X crash in ProcXkbGetKbdByName()

[hilary]

Laptop randomly logouts while I am using it for very basic things (mozilla, amarok, openoffice, deluge, pidgin usually). I can't determine any trigger, appears to be very random- doesn't happen while making a program work a lot, nor when launching a program. Last time I was just moving the mouse on the touchpad to minimize or close a window and it suddenly logged me out.

I do have compiz running, and I know that can cause problems sometimes. I have my screensaver disabled in case that might pose a problem, but I don't think that could be related since my computer isn't idle when this happens.

I can't pinpoint exactly when these random logouts began, certainly after I upgraded to hardy, but I don't think it occurred right away, maybe after receiving some updates for hardy. (I should note that I don't regularly install updates, only once every few months.) Its been occurring for at least two months, probably three. I was ignoring it because it only seemed to happen a few times a month. This week however, its already happened multiple times and I'm getting to the point where I need to do something about it because I can't afford to lose my work.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
     Subsystem: Dell XPS M1210 [1028:01d7]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Dell Unknown device [1028:01d7]

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a logout and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please run the command "/var/log/syslog > syslog.log after a logout and attach the resulting file "syslog.log" to this bug report.
 Thanks in advance!

[JMO Mandia (jmomandia)]

Same goes for Intrepid. Will send additional info later.

[JMO Mandia (jmomandia)]

Output of command "uname -a":
Linux jmom-laptop 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux

[JMO Mandia (jmomandia)]

Thanks in advance!

[Ian Weisser (ian-weisser)]

Thanks for the information.
The syslog shows an X-server crash, so assigning to package 'xorg'

Please take a look at the page https://wiki.ubuntu.com/DebuggingXorg
If it becomes neccesary, are you able (and willing) to use the described dbg and ssh (from a second system) to assist the debug process?

[hilary (hardysmiles)]

Here's the additional info...

hilary@lilbit:~$ uname -a
Linux lilbit 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux

hilary@lilbit:~$ /var/log/syslog > syslog.log
bash: /var/log/syslog: Permission denied
hilary@lilbit:~$ sudo /var/log/syslog > syslog.log

i don't know why it wouldn't let me do the system log... if you know how to make it let me do the system log, I'll add it the next time it logs out on me. in the meantime here is the dmesg and lspci logs

thank you!

-hilary.

[hilary (hardysmiles)]

oops, sorry, i didn't paste everything i meant to in the terminal... anyways when i do sudo /var/log/syslog > syslog.log it replies command not found...

[Ian Weisser (ian-weisser)]

The correct command is: 'sudo cat /var/log/syslog > syslog.log'

[Nico_argentina (ferrettinico)]

I can confirm the same happens in my laptop. Dell XPS M1530.

When this happen the Xorg log says something like:

AUDIT: Mon Dec 1 11:50:29 2008: 16167 X: client 4 rejected from local host ( uid=0 gid=0 pid=16201 )
AUDIT: Mon Dec 1 11:50:33 2008: 16167 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=16209 )
AUDIT: Mon Dec 1 11:50:33 2008: 16167 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=16210 )
AUDIT: Mon Dec 1 11:50:33 2008: 16167 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=16211 )

(I'm attaching the full log)

Thanks

[Ian Weisser (ian-weisser)]

Please attach a backtrace to this bug report. Instructions on how to create the backtrace are at https://wiki.ubuntu.com/DebuggingXorg .

(Please be aware that this bug report will deal with issues from hilary's backtrace. If your backtrace turns out to be different, then you might actually have a different bug and will need to open a separate bug report. If so, please unsubscribe from this bug, and make sure to add the backtrace to the new bug report!)

[Nico_argentina (ferrettinico)]

I am using nvidia restricted drivers, so i think i cannot use : xserver-xorg-video-<video>-dbg as it says in https://wiki.ubuntu.com/DebuggingXorg am i right? Is this package necessary for debugging?

One more thing, can i debug from another tty in the same machine or it must be by ssh?

Thanks

[Nico_argentina (ferrettinico)]

> One more thing, can i debug from another tty in the same machine or it must be by ssh?

No worries, i've started the debug session from another machine via SSH, i'll attach the backtrace after this incident happens again.

Thanks

[Nico_argentina (ferrettinico)]

Ok, this time while the debugging was running the system instead of logging out just freezes. I've tried CTRL ALT BKSP without success, and writing "cont" in the SSH Debug console, without succes, had to do a hard press...

I'm attaching the backtrace.

I'm running Intrepid up-to-date, with kernel 2.6.27-9-generic

Thanks

[Nico_argentina (ferrettinico)]

It happened again, and the backtrace seems to be slightly different, so i'm attaching it (this is the last one, i promise :) )

When it freezes the dbg tells me:

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7ac26b0 (LWP 6150)]
0xb7f61430 in __kernel_vsyscall ()

[Ian Weisser (ian-weisser)]

Thanks for the backtraces.
Marking 'New' in package 'xorg'

[Erektium (meizinteizi)]

I'm also affected by this bug.

Linux Kone 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

[Erektium (meizinteizi)]

This is a part of the syslog after the logout:

Dec 4 21:16:47 Kone kernel: [13117.125304] [drm] Num pipes: 3
Dec 4 21:16:48 Kone gdm[6158]: WARNING: gdm_slave_xioerror_handler: Fatal X error – :0 restarting
Dec 4 21:16:48 Kone bonobo-activation-server (jaro-13234): could not associate with desktop session: Failed to connect to socket /tmp/dbus-cdHjlM1Nds: connection blocked
Dec 4 21:16:49 Kone acpid: client connected from 13256[0:0]
Dec 4 21:16:49 Kone kernel: [13118.812541] [drm] Setting GART location based on new memory map
Dec 4 21:16:49 Kone kernel: [13118.813034] [drm] Loading R400 Microcode
Dec 4 21:16:49 Kone kernel: [13118.813055] [drm] Num pipes: 3
Dec 4 21:16:49 Kone kernel: [13118.813062] [drm] writeback test succeeded in 1 usecs

[Ian Weisser (ian-weisser)]

Erektium,

Next time your xserver crashes, please obtain a backtrace so we can see if your *really* have the same bug, instead of a different bug with similar symptoms. Instructions on how to create the backtrace are at https://wiki.ubuntu.com/DebuggingXorg .

Please be aware that this bug report will deal with issues from the original reporter's backtrace. If your backtrace turns out to be different, then you might actually have a different bug and will need to open a separate bug report. If so, please unsubscribe from this bug, and make sure to add the backtrace to the new bug report!

[Erektium (meizinteizi)]

I only have one computer

[JMO Mandia (jmomandia)]

Same here. But the problem seems to have disappearred. At least it has not
recurred in the past five days. Am observing.

2008/12/5 Erektium <email address hidden>

> I only have one computer
>
> --
> Random xserver crash in Hardy and Intrepid
> https://bugs.launchpad.net/bugs/290252
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[hilary (hardysmiles)]

Sorry to not have been posting more often. :S I have the same situation as Erektium: I only have one computer, so doing the backtrace doesn't seem to be an option for me...

Also, I haven't observed the problem in at least a full week, possibly two, though it has been very erratic in the months since I first noticed it. One thing I have noticed when it does happen: it seems to occur when i move my mouse to the bottom panel to open a minimized window (with several programs minimized). I don't know if that helps at all, or if others have noticed the same thing...

[Nico_argentina (ferrettinico)]

I haven't seen this problem in the last 2 weeks either. Don't know if it's solved or not

[Erektium (meizinteizi)]

I had these log outs few days ago, it seems that in my case this only happens when I have multiple programs running. The last time this happened I was running xchat, emesene, transmission, rhythmbox, firefox and compiz. If I use all those programs at the same time I think that the log out is almost certain to happen. Also I was browsing folders every time that the log out occurred. Last time I had these log outs it happened like five times in an hour.

[Tom Wolf (tjwolf)]

I'm affected by this problem too - happens every now and then (but this morning already 3 times). I'm running (uname -a):
Linux beowulf 2.6.27-12-generic #1 SMP Thu Feb 5 09:26:35 UTC 2009 i686 GNU/Linux

After the crash, I can see in Xorg.0.log.old the backtrace:

0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xb7f90400]
2: /usr/X11R6/bin/X(XkbWriteXKBGeometry+0x181) [0x81a9ed1]
3: /usr/X11R6/bin/X(XkbWriteXKBKeymapForNames+0x610) [0x81a9210]
4: /usr/X11R6/bin/X(XkbDDXLoadKeymapByNames+0x1d7) [0x81b41c7]
5: /usr/X11R6/bin/X(ProcXkbGetKbdByName+0x40e) [0x819041e]
6: /usr/X11R6/bin/X [0x8195668]
7: /usr/X11R6/bin/X(Dispatch+0x34f) [0x808c89f]
8: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b96685]
10: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.

I'm attaching my .xsession_errors as well.

Doing quick googles, I see at least a couple bugs that seem to deal with the same problem:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/297442
http://bugs.freedesktop.org/show_bug.cgi?id=20081

But I don't understand what the resolutions really mean as I'm not all that Linux savvy. All I really want to know is: is it fixed somewhere and where/how do I pick up the fix? Or do I have to wait for the next Ubuntu release?

[Tom Wolf (tjwolf)]

One additional datapoint: It has never happened to me at home - where I don't have the laptop connected to the laptop (and its second monitor and keyboard). In the bug I originally referred to (or maybe it was in the bug I found in the Fedora support site), the person had the same crash happening when he used a KVM switch - so perhaps that's the clue. If that's it, then this must be a regression bug as this never happened on 8.04.

[Bryce Harrington (bryce)]

Not obvious from the backtrace what is causing the crash. Next step is to forward the backtrace and logs upstream.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi hilary,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 290252

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 290252 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/290252

[hilary (hardysmiles)]

Sorry not to update for so long. This problem has ceased to occur on my system, however I can't remember when. I know I did a fresh install last summer, and I had no problems since. However this specific problem might have gone away prior to the install as well. Thanks for the help!