Summary: | Xorg 7.2.0 segfault in miSetShape. | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Eric <eric.sirianni> | ||||
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||
Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | critical | ||||||
Priority: | medium | ||||||
Version: | 7.2 (2007.02) | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Eric
2007-09-10 08:52:46 UTC
Created attachment 11491 [details]
Xorg.log
I hit this again with the same backtrace. Is anyone looking at this? Is there any information that I can provide? You could tell us what you were doing that prompted this. The only common thing across occurrences of this was that I was doing window management operations when this happened (maximizing windows, etc.). Could this be related to this bug? https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/71913 I am using an nvidia card with the nvidia driver. Just hit this again today. Problem seems to occur when maximizing an editor from within the eclipse IDE. Backtrace: 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1] 1: [0xffffe420] 2: /usr/bin/X(miSetShape+0x2fe) [0x813e7ee] 3: /usr/bin/X [0x8149ab7] 4: /usr/bin/X [0x8149cd9] 5: /usr/bin/X [0x815765e] 6: /usr/bin/X(Dispatch+0x1aa) [0x808f47a] 7: /usr/bin/X(main+0x495) [0x8076f05] 8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d3c050] 9: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241] The only other reference to "miSetShape" I find in a bug report is this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407007 Please try with a recent server and an opensource driver (nv or nouveau). If it is still a problem in that configuration, please reopen with a full backtrace. Closing assuming that it is an nVidia bug. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.