Bug 230550

Summary: artefacts showing the background while not using compositing
Product: [Unmaintained] plasma4 Reporter: Jean-Christophe Baptiste <jc>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andresbajotierra, kwin-bugs-null, linuxhippy
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: artefact while mouse over on the task bar
artefact while mouse over on the clock
artefact while mouse over on the clock

Description Jean-Christophe Baptiste 2010-03-13 11:14:53 UTC
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

I have frequently a lot of artefacts in KDE 4.3.5 (I switched to it straight
from Gnome).

It happens most of time when I put the mouse cursor over the task bar to
display the info bubble, or over the clock.

The artefact displays the background inside a shape equal to the info bubble,
but misplaced.
Please look at the screenshots for better understanding.

I didn't notice any issues neither while using compositing (but I don't want to
use it because of the ressources drain) nor using the Gnome environment, so I
"guess" it is more a KDE issue than an Nvidia one (I am using the proprietary
driver from the nvidia repo).
Comment 1 Jean-Christophe Baptiste 2010-03-13 11:19:55 UTC
Created attachment 41581 [details]
artefact while mouse over on the task bar
Comment 2 Jean-Christophe Baptiste 2010-03-13 11:20:32 UTC
Created attachment 41582 [details]
artefact while mouse over on the clock
Comment 3 Jean-Christophe Baptiste 2010-03-13 11:21:50 UTC
Created attachment 41583 [details]
artefact while mouse over on the clock
Comment 4 Martin Flöser 2010-03-13 11:35:38 UTC
When compositing is deactivated kwin does not paint the windows. In that case painting the windows is done by X. So it is unlikely to be a KDE issue.

Btw: why do you think using compositing results in a "ressources drain"? This is in general not true.
Comment 5 Vojtěch Zeisek 2010-03-13 11:35:55 UTC
I can confirm this behaviour. It happens sometimes with integrated Intel graphic (especially when CPU load is higher, but it is not a rule) as well as with integrated Nvidia chip. In both cases it is same as images of Jean-Christophe Baptiste.
Comment 6 Vojtěch Zeisek 2010-03-13 11:37:29 UTC
Sorry, short note: I notice such artefacts regardless composition is turned on or off.
Comment 7 Jean-Christophe Baptiste 2010-03-13 15:46:49 UTC
(In reply to comment #4)
> When compositing is deactivated kwin does not paint the windows. In that case
> painting the windows is done by X. So it is unlikely to be a KDE issue.

But if it was an X issue, wouldn't I have the same problem with Gnome or anything else?
I have had Gnome on this computer for 2 years and never had such a problem.

> Btw: why do you think using compositing results in a "ressources drain"? This
> is in general not true.

I noticed Kwin and Xorg use more CPU with compositing (more interrupts) and that's not good for my battery life. I also have from time to time latency issues, as when scrolling with Firefox. So personally I prefer the responsiveness without compositing.
Comment 8 Thomas Lübking 2010-03-13 16:08:58 UTC
looks quite as if it's triggered by the plasma tooltips - did you use plasma on gnome?

... :-P

I've no idea whether it's still supported at all, but try to turn on the backing store, xorg.conf, Section Device
Option "BackingStore" "true"

and if you don't want to use compositing, turn it off.

Section "Extensions"
    Option "Composite" "Disable"
EndSection

and maybe even
Option "DamageEvents" "True"
in the device section as well.

by all means, this is however an Xorg, driver or plasma problem - w/o compositing kwin has no impact on those bubbles.

passed to the plasma guys, though they might mark this upstream
Comment 9 Jean-Christophe Baptiste 2010-03-13 16:48:58 UTC
Thanks ;)
I am trying these options and will report how it goes.
Comment 10 Dario Andres 2010-03-14 14:02:15 UTC
Those "holes" in applications are caused by X -> bug 177959 / bug 173686. 
Regards

*** This bug has been marked as a duplicate of bug 177959 ***
Comment 11 Clemens Eisserer 2011-01-26 16:12:23 UTC
This is clearly a Xorg bug, I was able to write a xlib-only testcas (as I was asked for), but then nothing happend.

If you want this bug fixed, please vote for it and make some polite noise at:
https://bugs.freedesktop.org/show_bug.cgi?id=22566