From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Xorg segfaults, but GDM welcome screen loads
Date: Fri, 4 Feb 2011 14:26:12 -0800 [thread overview]
Message-ID: <AANLkTinLv1t0oLCeHPhKTp4UwoeoKoJVdoriYXN0+tc9@mail.gmail.com> (raw)
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
She also tried skipping gdm and issuing startxfce4 manually but it
fails in a similar way and displays "disconnected from session
manager". I get this in Xorg.0.log:
Backtrace:
[ 74.799] 0: /usr/bin/X (xorg_backtrace+0x28) [0x49eeb8]
[ 74.799] 1: /usr/bin/X (0x400000+0x62849) [0x462849]
[ 74.799] 2: /lib/libpthread.so.0 (0x64727eac2000+0xf3f0) [0x64727ead13f0]
[ 74.800] 3: /usr/lib64/xorg/modules/drivers/nv_drv.so
(0x64727bed7000+0x112d0) [0x64727bee82d0]
[ 74.800] 4: /usr/lib64/xorg/modules/libshadowfb.so
(0x64727a682000+0x3db2) [0x64727a685db2]
[ 74.800] 5: /usr/bin/X (0x400000+0x2da29) [0x42da29]
[ 74.800] 6: /usr/bin/X (0x400000+0x2eda9) [0x42eda9]
[ 74.800] 7: /usr/bin/X (0x400000+0x2475a) [0x42475a]
[ 74.800] 8: /lib/libc.so.6 (__libc_start_main+0xe6) [0x64727dcb2ba6]
[ 74.800] 9: /usr/bin/X (0x400000+0x242f9) [0x4242f9]
[ 74.800] Segmentation fault at address 0x64727462bfdc
[ 74.800]
Fatal server error:
[ 74.800] Caught signal 11 (Segmentation fault). Server aborting
and when grsecurity is enabled I get this in dmesg:
Segmentation fault occurred at 000064727462bfdc in
/usr/bin/Xorg[X:4647] uid/euid:1003/0 gid/egid:1010/1010, parent
/usr/bin/xinit[xinit:4646] uid/euid:1003/1003 gid/egid:1010/1010
I have tried disabling all security options in the kernel but I get
the same results with the exception of the dmesg info. I tried
re-emerging xorg-server, xf86-video-nv, xinit, and gdm. Strangely,
after re-emerging xorg-server and xinit there were files to change in
etc-update. I don't see how that's possible since I'm caught up with
emerge -DuN world. revdep-rebuild comes up with nothing. I'm running
an emerge -e world now. It's weird that the gdm welcome screen will
load (which implies xorg) but nothing afterward. Any ideas?
- Grant
next reply other threads:[~2011-02-04 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 22:26 Grant [this message]
2011-02-04 22:38 ` [gentoo-user] Xorg segfaults, but GDM welcome screen loads 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 ` [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=AANLkTinLv1t0oLCeHPhKTp4UwoeoKoJVdoriYXN0+tc9@mail.gmail.com \
--to=emailgrant@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