reassign 449039 xserver-xorg-core found 449039 2:1.4-3 thank you
[EMAIL PROTECTED] wrote: > I'm keeping sid updated on an almost daily basis, but this is the first time > the problem occurs. It's reproducible, in the sense that I can experience it > as soon as heavy X11 networking activity is taking place with Mathematica as > the remote client; five sessions are enough, if they happen to send what > apparently is the critical event concurrently. On the other hand this was not > my usage pattern until a few days ago or so, therefore I cannot be sure the > bug wasn't already there. > > The problem is not a freeze, but a complete Xserver crash: kde and all the > open applications fail, and I'm dropped back to a textual console. Then kdm > respawns, and I have to login again. Of course loosing all the unsaved > documents and open sessions elsewhere in the process. > > I don't have a backtrace available at the moment, and apparently not much is > shown in the Xorg.log file (I might have to increase the verbosity there). If it is the crash like you're reporting, there should be a backtrace. > But here follows the final part of my ~/.xsession-errors, saved immediately > after the crash. > Do you know if these 'X Error' appeared right before the crash? or which of them? > Thanks a lot again, and please let me know if anything more could help (I'll > have to see how to do the gdb backtrace you suggested, I've never tried). > Yes we really need a backtrace. If you have another machine, use it to log on the first one through ssh, run 'gdb -p $(pidof X)', reproduce the crash, enter 'bt full' in gdb, and send us the whole output. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
