Xorg crashes...

[Michel Dänzer]

On Thu, 2010-01-07 at 11:47 +1000, Peter Hutterer wrote: 
> On Wed, Jan 06, 2010 at 08:26:40PM -0500, Ryan Daly wrote:
> > On 01/06/2010 08:04 PM, Peter Hutterer wrote:
> > >> The backtrace is pretty consistent with the following few lines:
> > >>
> > >> Program received signal SIGTERM, Terminated.
> > >> 0x00007f146bab8110 in __close_nocancel () from /lib/libpthread.so.0
> > >> (gdb) backtrace r full
> > >> #0  0x00007f146bab8110 in __close_nocancel () from /lib/libpthread.so.0
> > >> No symbol table info available.
> > >> #1  0x00007f1466f61516 in ?? () from 
> > >> /usr/lib/xorg/modules/input//evdev_drv.so
> > >> No symbol table info available.
> > >> #2  0x0000000000447723 in DisableDevice (dev=0x18a33a0) at 
> > >> ../../dix/devices.c:407
> > >>
> > >> Are those lines pointing to a device or to the card possibly?
> > >>
> > >> I'm running the same version of Ubuntu on three different machines, and 
> > >> I'm only experiencing the Xorg restarts on one system.  I'm at a loss...
> > > 
> > > 
> > > uhm. SIGTERM is the termination signal. Something's shutting down your
> > > server.
> > 
> > Right, but it's nothing I'm doing.  That's the problem.  I'm not 
> > initiating an exit, nor am I hitting ctrl-backspace (I don't think 
> > that's enabled by default any longer anyway).
> > 
> > I'm looking for suggestions as to WHAT may be causing the SIGTERM.
> 
> either your session is terminating for some reason or another or you might
> be getting an unresolved symbol error. that terminates the server as well.
> try starting the server from a TTY instead of through gdm, once it exits you
> can see if it complains about a symbol error.

That would be SIGKILL though, or some other signal that can't be caught.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer