Xorg crashed with SIGQUIT

Bug #801014 reported by IC Raibow
This bug report is a duplicate of:  Bug #802271: Characters sent to tty1. Edit Remove
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu: 11.10 Oneiric
xorg-server: 1:7.6+7ubuntu1

Caught a crash when hit "enter" key at some time after launch. Dropped to console showing login prompt and looks like some garbage were entered for username. That VTY was inoperable, had to switch to another one and restart lightdm.

Found this in /var/log/Xorg.0.log:

[ 2711.822] Backtrace:
[ 2711.836] 0: /usr/bin/X (xorg_backtrace+0x26) [0x4a2bd6]
[ 2711.836] 1: /usr/bin/X (0x400000+0x638ba) [0x4638ba]
[ 2711.836] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f1ab8811000+0xfc60) [0x7f1ab8820c60]
[ 2711.836] 3: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f1ab77ff293]
[ 2711.836] 4: /usr/bin/X (WaitForSomething+0x19b) [0x45ceab]
[ 2711.836] 5: /usr/bin/X (0x400000+0x2f6e2) [0x42f6e2]
[ 2711.836] 6: /usr/bin/X (0x400000+0x2325e) [0x42325e]
[ 2711.836] 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xff) [0x7f1ab773fe1f]
[ 2711.836] 8: /usr/bin/X (0x400000+0x2354d) [0x42354d]
[ 2711.836] Caught signal 3 (Quit). Server aborting

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu1
ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
Uname: Linux 3.0-1-generic x86_64
Architecture: amd64
Date: Thu Jun 23 10:09:58 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110619)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
IC Raibow (icrbow) wrote :
tags: removed: unity-2d
bugbot (bugbot)
affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Revision history for this message
IC Raibow (icrbow) wrote :
Revision history for this message
IC Raibow (icrbow) wrote :

There's also corrupted readline buffer which executed a lightdm restart. Looks like something have to do with vty/xserver memory issues.

Revision history for this message
h (sairia-b) wrote :

My Thoshiba Satellite R830 (Sandy Bridge) is affected, too. I'm using 32-Bit userland.

The following things did not help:
- stock kernel 2.6.39.1 32bit
- stock kernel 2.6.39.1 64bit (with 32bit userland)
- unity 2d session
- unity 3d session
- lxde session
- lubuntu session

It seems to crash after the same sequence of key strokes, but the sequence changes after reboot.

Revision history for this message
h (sairia-b) wrote :

using lxdm instead of lightdm did not help either

tags: added: i386 i686
Revision history for this message
Bryce Harrington (bryce) wrote :

Sounds like a dupe of lp #787821.

X isn't crashing; something is listening to the enter key and forcing X to quit.

You should elaborate a bit more on your setup and steps to reproduce it. See if any of the details in the comments to bug 787821 match up with your experience.

affects: xorg-server (Ubuntu) → plymouth (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 801014] Re: Xorg crashed with SIGQUIT

On Wed, Jul 06, 2011 at 02:47:42AM -0000, Bryce Harrington wrote:
> Sounds like a dupe of lp #787821.

No, it's a dupe of 802271.

> X isn't crashing; something is listening to the enter key and forcing X
> to quit.

I think this has more to do with the keyboard being in the wrong mode than
there being something else listening at the time - the wrong mode being a
sign that more than one process is trying to use the VT and they have
different opinions about what mode the keyboard should be in. So this is a
VT allocation bug - in this case one in lightdm.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

affects: plymouth (Ubuntu) → lightdm (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.