From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Xorg segfaults, but GDM welcome screen loads
Date: Mon, 7 Feb 2011 23:05:06 +0000 [thread overview]
Message-ID: <201102072305.44529.michaelkintzios@gmail.com> (raw)
In-Reply-To: <201102052210.31445.alan.mckinnon@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1892 bytes --]
On Saturday 05 February 2011 20:10:31 Alan McKinnon wrote:
> Apparently, though unproven, at 02:54 on Saturday 05 February 2011, Grant
> did
>
> opine thusly:
> > >> Yesterday I caught up with portage and updated quite a few packages on
> > >> a remote workstation. The system hadn't been updated for about a
> > >> month. The updates included some xorg stuff and some xfce4 stuff.
> > >> Today when the workstation's user logged in via gdm, she clicked the
> > >> xfce4 "Migrate Config" option, something weird happened, and she ended
> > >> up back on the gdm welcome screen. Now whenever she logs is via gdm,
> > >> the screen immediately goes black and she is routed back to the gdm
> > >> welcome screen again. When I have grsecurity enabled I get this in
> > >> dmesg:
> > >>
> > >> Segmentation fault occurred at 000068e453633fdc in
> > >> /usr/bin/Xorg[X:4777] uid/euid:0/0 gid/egid:0/0, parent
> > >> /usr/sbin/gdm-binary[gdm:4775] uid/euid:0/0 gid/egid:1010/1002
> > >
> > > When you upgraded x.org, did you also rebuild it's drivers?
> >
> > I rebuilt nv but not evdev. Could that be responsible for this? I'm
> > not sure how since the gdm welcome screen comes up and the keyboard
> > works fine there for username/password input.
>
> I only mention it because in my experience I always have weird shit
> happening when I upgrade xorg-server over a big version number change.
>
> And rebuilding everything that underpins xorg always fixes it. Including
> drivers and mesa.
>
> In the old days when xorg was monolithic this never happened, as all the
> drivers always got rebuilt anyway. Nowadays with xorg sources being
> modular, we have to be a little more alert.
... and if you have just upgraded to xorg-server-1.9 you'll (probably) need an
xorg.conf file. The old .fdi files are no longer being used.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-07 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 22:26 [gentoo-user] Xorg segfaults, but GDM welcome screen loads Grant
2011-02-04 22:38 ` Alan McKinnon
2011-02-05 0:54 ` Grant
2011-02-05 20:10 ` Alan McKinnon
2011-02-07 23:05 ` Mick [this message]
2011-02-08 16:38 ` Grant
2011-02-08 22:02 ` Mick
2011-02-05 22:15 ` [gentoo-user] " walt
2011-02-06 0:14 ` Grant
2011-02-05 11:44 ` [gentoo-user] " Florian Philipp
2011-02-05 16:57 ` Grant
2011-02-05 16:59 ` Grant
2011-02-05 17:39 ` Florian Philipp
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=201102072305.44529.michaelkintzios@gmail.com \
--to=michaelkintzios@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