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