Bug 429668

Created attachment 292490 [details]
xorg.conf

Created attachment 292491 [details]
lspci -vvv

Created attachment 292492 [details]
~/.xsession-errors

Created attachment 292493 [details]
Xorg.0.log

Created attachment 292494 [details]
Xorg.0.log.old

No obvious crash in the X log, which makes me think it's a session problem. 
Shifting the blame to scim.

What's phenomenon of X crash? Could you start a new Xserver by self (not gdm),
and send the xinit's all output to me when X crashs again? Thanks.

Steps for Start a new X session by self:
KDE: # xinit /usr/bin/startkde -- :2 -auth "" 2>&1 | tee log
GNOME: # xinit /usr/bin/gnome-session -- :2 -auth "" 2>&1 | tee log

Are you using scim?

Hi, 

 - I'm not using scim
 - the crash is pretty random, though still happening (happened just a minute ago)

I'll try doing regular work in the new X session and try to make it crash. 

Seems X is not crashing?

So maybe you have a kernel oops or your desktop is hanging?
Any other log messages?  Are you able to ping the machine
from another when it hangs?

Can you describe exactly how it crashes?
Are you using GNOME?

Nothing interesting in the logs, nothing that would signal a kernel oops. The X
server just restarts. After re-login I can continue working. I'm using KDE. 

The crashes are less often now, but still do happen. Unfortunately on :0, not on
the new X session I have running on :2 :-/

Another random crash on :0, only thing interesting in the logs is /v/l/messages:
Apr 25 13:55:54 kovinek gdm-binary[2865]: WARNING: gdm_slave_xioerror_handler:
Fatal X error - Restarting :0
Apr 25 13:55:56 kovinek acpid: client connected from 18188[0:0]
Apr 25 13:56:13 kovinek gconfd (dkovalsk-31485): GConf server is not in use,
shutting down.
Apr 25 13:56:13 kovinek gconfd (dkovalsk-31485): Exiting
Apr 25 13:56:25 kovinek gconfd (dkovalsk-18371): starting (version 2.20.1), pid
18371 user 'dkovalsk'
Apr 25 13:56:25 kovinek gconfd (dkovalsk-18371): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration
source at position 0
Apr 25 13:56:25 kovinek gconfd (dkovalsk-18371): Resolved address
"xml:readwrite:/home/dkovalsk/.gconf" to a writable configuration source at
position 1
Apr 25 13:56:25 kovinek gconfd (dkovalsk-18371): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source
at position 2


and as I already mentioned thread safety warnings in ~/.xsession-errors
setParam(pad.cpp:304)    --- NOT YET THREAD SAFE!
intVerToStrVer(pad.cpp:96)       --- intVerToStrVer
intVerToStrVer(pad.cpp:96)       --- intVerToStrVer
intVerToStrVer(pad.cpp:96)       --- intVerToStrVer
intVerToStrVer(pad.cpp:96)       --- intVerToStrVer

If there's a way to force more verbose logging for my regular setup on :0 I'll
be happy to do it :-)

Moving back to Xorg team based on comment 9.

Reporter, have you had a chance to test with F9 pre-releases?

Not on this hardware (my laptop). I haven't been bitten by this issues on
machines running rawhide, but on the other hand I don't use them for day to day
work and since it takes a while to reproduce I can't say it's been fixed. 

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 to the applicable version.  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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.