Red Hat Bugzilla – Bug 242896
SIGSEGV with xorg-x11-server 184.108.40.206-5.fc7 (intel 945GM)
Last modified: 2008-06-16 21:27:04 EDT
Description of problem:
Sometimes the X-server crashed with SIGSEGV
Version-Release number of selected component (if applicable):
Current Operating System: Linux oder 2.6.21-1.3194.fc7 #1 SMP
Build Date: 11 May 2007
Build ID: xorg-x11-server 220.127.116.11-5.fc7
Start a guest in VMwareWorkstation-6.0.0-45731 from PowerOff or Suspend
(SIGSEGV happens only sometimes, I coundn't detect the needed circumstances)
Steps to Reproduce:
1.run X11 with gnome
3.start a guest (fromPowerOff or Suspend)
X11 crashes (and restarts ... Login Screen show up)
no crash of X11
Additional info: -
Created attachment 156331 [details]
log file of the X-Server
Please attach the output of both:
$ xrandr -q
$ xdpyinfo -ext XFree86-VidModeExtension
Created attachment 156699 [details]
Created attachment 156700 [details]
xdpyinfo -ext XFree86-VidModeExtension
Created attachment 156853 [details]
2nd log file of X-Server with SIGSEGV
Created attachment 156854 [details]
3rd log file of X-Server with SIGSEGV
Created attachment 160732 [details]
procedure to recreate the bug
Now I'm able to recreate the bug on request.
If needed you could enable additional traces while the
* VMware runs under a screen with high resolution, e.g. 1600x1200 on
* suspend the guest
* switch the screen to a lower resolution, e.g. 1400x1050 on build in LCD
* resume the guest
-> the X-server will crash
(In reply to comment #2)
> Please attach the output of both:
> $ xrandr -q
> $ xdpyinfo -ext XFree86-VidModeExtension
I delivered the requested output.
If you could provide me a X-Server with symbols (not stripped) which will write
a core after the SIGSEGV crash, you should be able to to analyze the stack.
I'm up for it!
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 is no longer maintained, which means that it will not
receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version
of Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.