On Wed, 30 Sep 2009, ??????? ?????? wrote:
Sjoerd Hardeman wrote:??????? ?????? schreef:Matthew Moore wrote:On Saturday September 26 2009 9:39:43 am ??????? ?????? wrote:Does this happen to anybody else? Should I report it as a bug? I googled it and found several references of the problem, although old (around April 2009).Are you using an intel graphics chip? This was happening on my laptop about 6 months ago, and I finally tracked it down to the intel driver crashing on logout. I use kdm, so a workaround for me was to add the line TerminateServer=true to the [X-:*-Core] section of the file /etc/kde4/kdm/kdmrc.Thanks for the tip, that worked! I have indeed an intel chip and I wonder which package has the bug, in order to report it. (EE) intel(0): Failed to initialize kernel memory managerThat must be the xserver-xorg-video-intel. First install the xserver-xorg-video-intel-dbg, then reproduce. That will probably give a more helpful backtrace for the people who have to fix this problem. SjoerdI installed xserver-xorg-video-intel-dbg but I don't know what to do now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get exactly the same things that I posted earlier. With dbg, should I do something different? Where does it write its trace? Giorgos
Run ulimit -a and see if you have core files set to 0 or unlimited.You want to run gdb against the core and run bt full for a full backtrace and include that along with the logs for your report.
$ gdb application core.Xorg gdb> bt full Send this & logs in the bug report.