Summary: | Repainting problem in krunner | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | albert <alberthilbert> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | andresbajotierra, desintegr |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Snapshot showing the repainting problem |
Description
albert
2008-07-11 01:00:29 UTC
Created attachment 26029 [details]
Snapshot showing the repainting problem
this is a compositing problem, possibly in kwin (possibly in the video driver). Same problem here. I'm using 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703)) from Debian experimental. Video card: 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) Video driver: xserver-xorg-video-intel 2.3.2 My video card is: ATI Technologies Inc M9+ 5C61 [Radeon Mobility 9200 (AGP)] (rev 01) The driver is: X.org radeon 4.3.0 Confirmed here on nvidia proprietary. (KDE 4.0.99 (4.1RC1+) in ArchLinux) Intel Integrated Video Card: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) Driver: xf86-video-intel 2.3.2 KWin compositing disabled (doesn't work for me) My situation is a bit different: when I delete part of the search, the panel stays in the same height that when where matches, and after ~4/5 seconds it goes back to the normal height (search bar only height); but it doesn't display a weird shadow/black-rectangle below. Can anyone still reproduce this bug with a recent KDE version? (4.1.3 / 4.2beta1 / 4.2svn)? Thanks :) For me, krunner works perfectly now (kde 4.1.3). If you think this bug is fixed, you can close it as RESOLVED with resolution WORKSFORME. And if you later experience this bug again, you can re-open it. :) Ok, then I mark this bug as resolved. |