When I start xine and just close it, X Server crashes immediately.
Fedora 7, Gnome 2.18.0
X Window System Version 1.3.0
xine (X11 gui) v0.99.4 (default config)
Just start xine and close it by pressing "q" button, or clicking on Close button.
X Server crashes.
I using Driver "vesa" in xorg.conf, because fglrx (8.37.6) don't work with X 1.3.0
My videocard is ATI Radeon X1950 XTX [GDDR4, 512MB]
$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x7ff00000 (2047MB), size= 1MB: write-through, count=1
reg02: base=0xd0000000 (3328MB), size= 16MB: write-combining, count=1
Please attach the /var/log/Xorg.0.log from the crash. It should contain a
backtrace at the end; it may have been saved to /var/log/Xorg.0.log.old.
Created attachment 157333 [details]
"Xorg.0.log.old" after X Server crashes
"/var/log/Xorg.0.log.old" file after X Server crashes
and backtrace itself
$ tail -n20 /var/log/Xorg.0.log.old
(II) 3rd Button detected: disabling emulate3Button
0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80ceb41]
4: /usr/lib/xorg/modules/extensions//libGLcore.so [0xbd5f70]
5: /usr/lib/xorg/modules/extensions//libglx.so [0x32b3ba]
6: /usr/bin/Xorg(ReparentWindow+0x1ac) [0x80774dc]
7: /usr/bin/Xorg(ProcReparentWindow+0xd5) [0x8088d95]
8: /usr/bin/Xorg [0x814efd1]
9: /usr/bin/Xorg(Dispatch+0x1aa) [0x808936a]
10: /usr/bin/Xorg(main+0x495) [0x80710a5]
11: /lib/libc.so.6(__libc_start_main+0xe0) [0x4d440f70]
12: /usr/bin/Xorg(FontFileCompleteXLFD+0x1e1) [0x8070391]
Fatal server error:
Caught signal 11. Server aborting
I'm getting the same Xorg crash when mythtvfrontend exits on 2 different
machines. One has 64bit OS on intel core2 with an nvidia card and the nv
driver. The other is 32bit OS on intel P4 using the ivtv Xdriver with a
PVR350's TV-out. Both machines are fully updated F7.
Created attachment 206521 [details]
Xorg log with crash backtrace
Me too with a certain matlab plot and nv (xorg-x11-drv-nv-2.1.3-1.fc7) driver.
Created attachment 207531 [details]
X log with backtrace
This should be fixed already in the F8 X server, but I'll likely do an F7 update
for this once F8 is out.
Are there any workarounds we can do for now? Maybe something in xorg.conf to
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.