public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: xdm doesn't restart on killed X
Date: Thu, 12 Nov 2009 18:32:00 +0200	[thread overview]
Message-ID: <200911121832.00625.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20091112162931.9087A538E9@doki-pen.org>

On Thursday 12 November 2009 18:29:31 doki_pen@doki-pen.org wrote:
> In gmane.linux.gentoo.user, you wrote:
> > On Thursday 12 November 2009 16:05:38 doki_pen@doki-pen.org wrote:
> >> In gmane.linux.gentoo.user, you wrote:
> >> > On Wednesday 11 November 2009 19:02:26 doki_pen@doki-pen.org wrote:
> >> >> In gmane.linux.gentoo.user, you wrote:
> >> >> > On Wednesday 11 November 2009 16:17:45 doki_pen@doki-pen.org wrote:
> >> >> >> In gmane.linux.gentoo.user, you wrote:
> >> >> >> > On Tuesday 10 November 2009 17:54:48 Doki Pen wrote:
> >> >> >> >> I've recently switched from gdm to xdm in an effort to reduce
> >> >> >> >> my distro size.  The only problem I've run into is that when I
> >> >> >> >> kill my X session, xdm doesn't restart automatically.  I have
> >> >> >> >> to switch to a vtty and type exec sudo /etc/init.d/xdm restart.
> >> >> >> >>  I've read the man pages and googled but can't come up with a
> >> >> >> >> solution.  Does anyone know if there is a way to fix this
> >> >> >> >> issue?
> >> >> >> >
> >> >> >> > When X exists, is xdm still running or has it died too?
> >> >> >> >
> >> >> >> > You can tell when restarting xdm if it gives errors about xdm
> >> >> >> > not running when the "stop" phase of "restart"" is run
> >> >> >>
> >> >> >> xdm is not running after I kill my xsession.  It is running after
> >> >> >> I log in.  I tested using ps -Af | grep -i xdm.
> >> >> >
> >> >> > Ok, so I reckon the init script dies because xdm dies when X
> >> >> > exists.
> >> >> >
> >> >> > is there anything relevant in your messages log file, Xorg.0.log,
> >> >> > ~/.xsession- errors and similar logs?
> >> >>
> >> >> From /var/log/Xorg.0.log.old:
> >> >>
> >> >> Backtrace:
> >> >> 0: /usr/bin/X(xorg_backtrace+0x38) [0x812a180]
> >> >>
> >> >> Fatal server error:
> >> >> Caught signal 11.  Server aborting
> >> >
> >> > That's a segfault so there's a serious bug. It's likely in X itself.
> >> >
> >> > Did you recently upgrade X and at the same time rebuild all it's app
> >> > and all drivers - without exception?
> >>
> >> This has happened since I have switched to xdm.  I've run revdep-rebuild
> >> and lafilefixer since my last X upgrade.  Is there any other way to
> >> check for broken libs?
> >
> > Checking for broken libs is not going to fix a segfault.....
> 
> So what should I do?  upgrade X?  upgrade xdm?

Downgrade xdm methinks 

-- 
alan dot mckinnon at gmail dot com



      reply	other threads:[~2009-11-12 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 15:54 [gentoo-user] xdm doesn't restart on killed X Doki Pen
2009-11-10 16:48 ` Alan McKinnon
2009-11-11 14:17   ` [gentoo-user] " doki_pen
2009-11-11 14:36     ` Alan McKinnon
2009-11-11 17:02       ` doki_pen
2009-11-12 10:08         ` Alan McKinnon
2009-11-12 14:05           ` doki_pen
2009-11-12 14:08             ` Alan McKinnon
2009-11-12 16:29               ` doki_pen
2009-11-12 16:32                 ` Alan McKinnon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200911121832.00625.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox