[Bug 34588] Screen corruption when running gtkperf on awesomewm

2019-09-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=34588 GitLab Migration User changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 34588] Screen corruption when running gtkperf on awesomewm

2014-07-07 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=34588 Andreas Boll changed: What|Removed |Added Component|Drivers/DRI/r300|Drivers/Gallium/r300 --- Comment #3 from

[Bug 34588] Screen corruption when running gtkperf on awesomewm

2011-03-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=34588 --- Comment #2 from Jeff Cook 2011-03-03 17:38:04 PST --- Yes, disabling tiling fixes it. I just tried this today and it is still occurring in new git builds. I guess it is probably a dupe of the linked bug. I haven't tested a git build of X ye

[Bug 34588] Screen corruption when running gtkperf on awesomewm

2011-03-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=34588 --- Comment #2 from Jeff Cook 2011-03-03 17:38:04 PST --- Yes, disabling tiling fixes it. I just tried this today and it is still occurring in new git builds. I guess it is probably a dupe of the linked bug. I haven't tested a git build of X ye

[Bug 34588] Screen corruption when running gtkperf on awesomewm

2011-02-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=34588 --- Comment #1 from Alex Deucher 2011-02-22 20:46:28 PST --- Does disabling tiling help? Option "ColorTiling" "false" in the device section of your xorg.conf? If so this bug is probably a duplicate of bug 33929. You might try the xserver patch

[Bug 34588] Screen corruption when running gtkperf on awesomewm

2011-02-22 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=34588 --- Comment #1 from Alex Deucher 2011-02-22 20:46:28 PST --- Does disabling tiling help? Option "ColorTiling" "false" in the device section of your xorg.conf? If so this bug is probably a duplicate of bug 33929. You might try the xserver patch