| 1 |
Apparently, though unproven, at 00:26 on Saturday 05 February 2011, Grant did |
| 2 |
opine thusly: |
| 3 |
|
| 4 |
> Yesterday I caught up with portage and updated quite a few packages on |
| 5 |
> a remote workstation. The system hadn't been updated for about a |
| 6 |
> month. The updates included some xorg stuff and some xfce4 stuff. |
| 7 |
> Today when the workstation's user logged in via gdm, she clicked the |
| 8 |
> xfce4 "Migrate Config" option, something weird happened, and she ended |
| 9 |
> up back on the gdm welcome screen. Now whenever she logs is via gdm, |
| 10 |
> the screen immediately goes black and she is routed back to the gdm |
| 11 |
> welcome screen again. When I have grsecurity enabled I get this in |
| 12 |
> dmesg: |
| 13 |
> |
| 14 |
> Segmentation fault occurred at 000068e453633fdc in |
| 15 |
> /usr/bin/Xorg[X:4777] uid/euid:0/0 gid/egid:0/0, parent |
| 16 |
> /usr/sbin/gdm-binary[gdm:4775] uid/euid:0/0 gid/egid:1010/1002 |
| 17 |
|
| 18 |
|
| 19 |
When you upgraded x.org, did you also rebuild it's drivers? |
| 20 |
|
| 21 |
There should have been an elog about it, it's not something that protage can |
| 22 |
tarck easily as the driver's version numbers did not change. |
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
> |
| 29 |
> She also tried skipping gdm and issuing startxfce4 manually but it |
| 30 |
> fails in a similar way and displays "disconnected from session |
| 31 |
> manager". I get this in Xorg.0.log: |
| 32 |
> |
| 33 |
> Backtrace: |
| 34 |
> [ 74.799] 0: /usr/bin/X (xorg_backtrace+0x28) [0x49eeb8] |
| 35 |
> [ 74.799] 1: /usr/bin/X (0x400000+0x62849) [0x462849] |
| 36 |
> [ 74.799] 2: /lib/libpthread.so.0 (0x64727eac2000+0xf3f0) |
| 37 |
> [0x64727ead13f0] [ 74.800] 3: /usr/lib64/xorg/modules/drivers/nv_drv.so |
| 38 |
> (0x64727bed7000+0x112d0) [0x64727bee82d0] |
| 39 |
> [ 74.800] 4: /usr/lib64/xorg/modules/libshadowfb.so |
| 40 |
> (0x64727a682000+0x3db2) [0x64727a685db2] |
| 41 |
> [ 74.800] 5: /usr/bin/X (0x400000+0x2da29) [0x42da29] |
| 42 |
> [ 74.800] 6: /usr/bin/X (0x400000+0x2eda9) [0x42eda9] |
| 43 |
> [ 74.800] 7: /usr/bin/X (0x400000+0x2475a) [0x42475a] |
| 44 |
> [ 74.800] 8: /lib/libc.so.6 (__libc_start_main+0xe6) [0x64727dcb2ba6] |
| 45 |
> [ 74.800] 9: /usr/bin/X (0x400000+0x242f9) [0x4242f9] |
| 46 |
> [ 74.800] Segmentation fault at address 0x64727462bfdc |
| 47 |
> [ 74.800] |
| 48 |
> Fatal server error: |
| 49 |
> [ 74.800] Caught signal 11 (Segmentation fault). Server aborting |
| 50 |
> |
| 51 |
> and when grsecurity is enabled I get this in dmesg: |
| 52 |
> |
| 53 |
> Segmentation fault occurred at 000064727462bfdc in |
| 54 |
> /usr/bin/Xorg[X:4647] uid/euid:1003/0 gid/egid:1010/1010, parent |
| 55 |
> /usr/bin/xinit[xinit:4646] uid/euid:1003/1003 gid/egid:1010/1010 |
| 56 |
> |
| 57 |
> I have tried disabling all security options in the kernel but I get |
| 58 |
> the same results with the exception of the dmesg info. I tried |
| 59 |
> re-emerging xorg-server, xf86-video-nv, xinit, and gdm. Strangely, |
| 60 |
> after re-emerging xorg-server and xinit there were files to change in |
| 61 |
> etc-update. I don't see how that's possible since I'm caught up with |
| 62 |
> emerge -DuN world. revdep-rebuild comes up with nothing. I'm running |
| 63 |
> an emerge -e world now. It's weird that the gdm welcome screen will |
| 64 |
> load (which implies xorg) but nothing afterward. Any ideas? |
| 65 |
> |
| 66 |
> - Grant |
| 67 |
|
| 68 |
-- |
| 69 |
alan dot mckinnon at gmail dot com |
Archives