Summary: | glxgears kills xserver on window resize | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christoph Budziszewski <gentoobugs> |
Component: | [OLD] Server | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bensberg |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=7608 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge info
strace of the occurance Xorg.0.log with crash |
Description
Christoph Budziszewski
2006-07-18 16:00:36 UTC
Created attachment 92166 [details]
emerge info
my emerge --info
Created attachment 92167 [details]
strace of the occurance
did an strace. maybe it is helpfull.
Any particular reason you're using a hardened kernel but not a hardened profile? Also, please attach /var/log/Xorg.0.log. Created attachment 92346 [details]
Xorg.0.log with crash
No particular reason, just thought hardened-sources is a bit better than vanilla (and no need to download new sources every two weeks with gentoo-sources ;-). Is there a problem not using the hardend profile (i.e. put "hardened" in USE, I suppose)?
No, there shouldn't be. I don't often see the combination you have is all :) Give it a spin with gentoo-sources and see if the problem is still there. If it is, a bug should be filed at https://bugs.freedesktop.org. tried linux-2.6.16-gentoo-r13 but the problem still exists. As suggested: https://bugs.freedesktop.org/show_bug.cgi?id=7608 What happens if you don't maximize, but grab a corner of the window and drag it around, resizing it constantly? Does it crash then too? Yes. dragging around also triggers the crash. but only when the window becomes abount half of original width and height. The crash is not triggered when the window maximized and instantly restored before the "gears" inside the window are resized (got bigger). Seems to be the same as Bug #134395... Thanks mrsteven. Following upstream's lead and marking this as a duplicate. *** This bug has been marked as a duplicate of 134395 *** |