From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102103] after switch to xserver-xorg-video-intel-native-modesetting libreoffice sidebar corrupted
Date: Tue, 08 Aug 2017 08:11:04 +0000 [thread overview]
Message-ID: <bug-102103-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1311 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102103
Bug ID: 102103
Summary: after switch to
xserver-xorg-video-intel-native-modesetting
libreoffice sidebar corrupted
Product: Mesa
Version: 17.1
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/i915
Assignee: dri-devel@lists.freedesktop.org
Reporter: pieterkristensen@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 133375
--> https://bugs.freedesktop.org/attachment.cgi?id=133375&action=edit
ugly sidebar libreoffice caused by xserver-xorg-video-intel-native-modesetting
graphics dirver
My machine is a Dell Lattitude e5500. As far as I can see it has a Mobile 4
Series Chipset Integrated Graphics Controller.
I'm using kde Neon. After the introduction of the
xserver-xorg-video-intel-native-modesetting driver I had a few (minor but
irritating) issues.
Most notably the sidebar of LibreOffice is ugly.
I filed a bug at the document foundation and kde but they couldn't do anything
with them.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2963 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-08-08 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 8:11 bugzilla-daemon [this message]
2019-09-18 19:40 ` [Bug 102103] after switch to xserver-xorg-video-intel-native-modesetting libreoffice sidebar corrupted bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-102103-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.