From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Xorg segfaults, but GDM welcome screen loads
Date: Sat, 05 Feb 2011 14:15:00 -0800 [thread overview]
Message-ID: <iiki5a$7ro$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=rVSOwxsRfskLx5sQzK9a_ybqcMn3kKCCRaa50@mail.gmail.com>
On 02/04/2011 04:54 PM, Grant wrote:
>>> 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 can't answer that specifically, but you should definitely re-emerge
it anyway.
What happens when you run /usr/bin/Xorg directly instead of with startx?
If Xorg still segfaults it may give you better error messages.
next prev parent reply other threads:[~2011-02-05 22:16 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
2011-02-08 16:38 ` Grant
2011-02-08 22:02 ` Mick
2011-02-05 22:15 ` walt [this message]
2011-02-06 0:14 ` [gentoo-user] " 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='iiki5a$7ro$1@dough.gmane.org' \
--to=w41ter@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