Possible bug in kwin or ??

Duncan 1i5t5.duncan at cox.net
Mon Apr 25 09:10:14 BST 2011

gene heskett posted on Sun, 24 Apr 2011 08:10:46 -0400 as excerpted:

> Please see this bug report:
>  <https://bugs.freedesktop.org/show_bug.cgi?id=35452>
> It turns out that the radeon driver is not the only victim, the nvidia
> driver suffers also, and there may be others.
> Symptoms with the nvidia blob are that black areas of the screen are
> contaminated from playing a news story.  

> Black areas [...] such as the html status bar of kmail, or the black
> patterns of the card faces in kpatience are also rendered rather yucky.
> We can fix it with:
> Section Device
> 	Option "NoFlip"  "True"
> in the xorg.conf file.
> There is a patch linked to in this bug-report, which also fixes it, but
> its an unruly hack according to the X folks.
> Can this be investigated please?  It seems to have become a problem of a
> far greater frequency of occurrence somewhere around 4.6.2, and has
> forced me to reboot to clean it up several times over the recent week.

FWIW, the kwin devs aren't likely to see it here, and many devs prefer a 
filed bug even if they do read a list, as it's designed for tracking such 
things thru final release of the fixed code, while a list isn't.

Meanwhile, does turning off kwin compositing/effects get rid of the 
problem?  If not, it's very unlikely to be kwin related at all.  If that 
does workaround the problem, it's still unlikely to be a kwin bug, but may 
be kwin related in that kwin is sometimes the first widely used Linux 
software to make use of some OpenGL functionality.  Tho even then, kwin 
won't use the functionality unless the driver CLAIMS to support it.

I could write more on that topic but won't, here, as it's unclear whether 
suspending kwin's OpenGL functions (suspend compositing/effects) 
eliminates the effects of the bug, or not.  And if it doesn't, as sounds 
likely, there's little point in discussing it further as it's quite 
unlikely to be a kwin bug, at least one related to OpenGL.

Never-the-less, you could try a different window-manager, compiz for 3D 
perhaps, or a 2D-only manager, and see if the problem persists.  If it 
does, it's quite clearly not a kwin issue.  (After installation, the 
window manager docs and/or commandline help output should say how to run 
it to replace an existing window manager.  With kwin, for instance,
kwin --help, run in konsole to see the output, says kwin --replace can be 
used to replace the existing window manager.)

Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

More information about the kde mailing list