Summary: | x11-libs/gtk+-2.18: leaves ghosts on scroll | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexandre Hannud Abdo <solstag> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | tetromino |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 288249 |
Description
Alexandre Hannud Abdo
2009-11-11 18:24:09 UTC
Just to clarify... I should have said "Reproducible: Always" since if you try enough times it does happen on every scrollable window. It's easier to reproduce with larger scrollbars. Apparently it affects every gtk+ application: scrollable pages on firefox, email lsts on evolution, contact lists and conversations on empathy, file folders on nautilus, etc. You will have a better chance at getting this fixed by reporting on upstream bugzilla (https://bugzilla.gnome.org). This is most likely a problem with new "client side window" code but I'm 100% unable to reproduce this problem since I first upgrade to gtk+-2.18 branch weeks ago I have also seen this, but only in compiz (in metacity without compositing, everything works fine). To resolve the issue in compiz, you need to enable "force synchronization between X and GLX" in the workarounds plugin in ccsm. Ok, after Alexandre Rostovtsev's comment I tried disabling DRI and everything works fine now. So this might be my fault for using the raedeonhd driver from git, although I've been using it for ages without a glitch. However, I'm not running compiz (the ebuild isn't installed). Is there a way for me to set this "force synchronization between X and GLX" without compiz? ~~ If you're using xserver-1.7.x, you might be running in to an EXA corruption issue https://bugs.freedesktop.org/show_bug.cgi?id=24300 how is it with gtk+-2.18.5 ? After today's updates (gtk, mesa, xserver, radeonhd) everything works fine :] I guess the issue was solved upstream. Thanks! ~~ |