Red Hat Bugzilla – Bug 699026
KDE menu corruption with Sandy Bridge integrated graphics
Last modified: 2011-05-19 00:54:25 EDT
Description of problem: All pull-down menus in KDE 4.6 are distorted and unreadable. (the rest of the window treatments appear OK) This is only a problem with Intel Sandy Bridge integrated graphics.
The machine in question is a relatively new Dell Latitude E6420
Version-Release number of selected component (if applicable): 2.14.0-4
How reproducible: Always
Steps to Reproduce:
1. Boot into x86_64 KDE Live CD
2. Open Konsole or any other KDE program
3. Pull down the file or edit (or other) menu
Actual results: Menu items are unreadable and their backgrounds are completely distored.
Expected results: normal menus.
Additional info: This bug was also encountered by the Ubuntu team (see: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/750964 ) and there appears to be a patch contributed that reportedly fixes the issue.
Intel also released 2.15.0 last week, but I haven't had a chance to patch that into the SRPM to see if it fixes it also.
I haven't tried the 32 bit live CD image yet, so I'm not sure if this bug is architecture specific or not. If you want, I will do so.
Since this was a live image, I didn't even check yum update yet. There's an update to this driver. I'll test it shortly.
Output from lscpi -vnn
00:02.0 VGA compatible controller : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0493]
Flags: bus master, fast devsel, latency 0, IRQ 48
Memory at e1400000 (64-bit, non-prefetchable) [size=4M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 4000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel modules: i915
Relevant bits from dmidecode:
Handle 0x0001, DMI type 1, 27 bytes
Manufacturer: Dell Inc.
Product Name: Latitude E6420
Output from cat /proc/cpuinfo (multiply by 4)
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
stepping : 7
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat tpr_shadow vnmi flexpriority ept vpid
bogomips : 4989.27
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
Installed the x86_64 version of the F15 beta to disk, yum updated the relevant libdrm, mesa-* and xorg-* packages. Rebooted, and problem still exists.
Tried the work-around suggested in the Ubuntu bug in addition to installing 2.14.0-5 and that does mitigate the problem. Though you can see the extra repaint needed to keep the menu from corrupting.
Next step is for me to try 2.15.0
Updated to 2.15.0 and removed the xorg.conf, and the problem disappeared completely, with no obvious repaint or other performance issues.
Fixed SRPM: http://www.deepgroove.org/rpm/xorg-x11-drv-intel-2.15.0-1.fc15.src.rpm
p.s.: I didn't correctly update %changelog in the spec for that srpm, sorry!
xorg-x11-drv-intel-2.15.0-3.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-intel-2.15.0-3.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
New driver package looks good here. Feel free to close this out!
xorg-x11-drv-intel-2.15.0-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.