SLiM crashes X on switch to console, prevents resume

Question

i'm facing something of a mystery, here.
when i switch to a virtual console ( <ctrl>+<alt>+f{1-9} ) after logging into a desktop session via slim, the x session crashes and i'm presented with a new slim login screen.
i first noticed this while (finally!) trying to setup suspend-to-ram.  when i resumed, instead of getting my x session back, i got a new login.  i thought it was a problem with resuming from S3, but it happens when manually switching as well, and disappears when i disable slim.  if i understand correctly, resuming from S3 involves a switch-to-console at some point.
i don't see much to go on in my log files (and i read them all, dammit), but here's the following from /var/log/slim.log.  most of the messages are generated by the applications that are started by startfluxbox, and predictably, they start failing after the x server has crashed:
/usr/bin/xauth: creating new authority file /home/user/.Xauthority
xmodmap: unable to open file '/home/user/.Xmodmap' for reading
xmodmap: 1 error encountered, aborting.
Logging to: /home/user/.fluxbox/log
amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration
amidi-plug(i_backend.c:i_backend_load:107): loading backend '/usr/lib/audacious/Input/amidi-plug/ap-alsa.so'
amidi-plug(i_backend.c:i_backend_load:145): backend /usr/lib/audacious/Input/amidi-plug/ap-alsa.so (name alsa') successfully loaded
[01-14 06:23:04] Torbutton NOTE: Skipping no location: chrome://global/content/commonDialog.xul
[01-14 06:23:08] Torbutton NOTE: Skipping no location: chrome://browser/content/browser.xul
[01-14 06:23:13] Torbutton NOTE: Crash detected, attempting recovery
[01-14 06:23:13] Torbutton NOTE: Restoring cookie status
[01-14 06:23:13] Torbutton NOTE: Loading non-tor jar after crash
[01-14 06:23:13] Torbutton NOTE: Restoring tor state
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x812d2ab]
1: /usr/bin/X(xf86SigHandler+0x51) [0x80c13e1]
2: [0xb7ff8400]
3: /usr/lib/xorg/modules//libxaa.so [0xb71afd99]
4: /usr/lib/xorg/modules//libxaa.so [0xb71f618a]
5: /usr/bin/X [0x8173824]
6: /usr/bin/X(ProcPolyFillRectangle+0x100) [0x80880f0]
7: /usr/bin/X(Dispatch+0x34f) [0x808b19f]
8: /usr/bin/X(main+0x47d) [0x8070c1d]
9: /lib/libc.so.6(__libc_start_main+0xe5) [0xb7c496c5]
10: /usr/bin/X [0x8070001]
Fatal server error:
Caught signal 11. Server aborting
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"
audacious: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 30967 requests (30967 known processed) with 0 events remaining.
clues?
Last edited by kludge (2009-01-14 19:47:34)

Answer 1

You could try this as it's similar to what "madeye" said but append a plain "s" to the kernel line. Puts you in "single-user mode" my password seems to work then. Actually I think what you guys are discussing is the same thing affecting me at the moment. I need to investigate this more. Hope this helps!!
Update: This was not my issue after all. My issue was that I switched to using sha512 passwords via the Wiki page. I was also using fgetty which doesn't support sha512 passwords. Fixed now!
Last edited by harryNID (2010-11-06 09:44:13)