You are not logged in.
I recently installed SLiM (Simple Login Manager) and it's quite nice. My only problem with it is that if I do a ctrl-alt-backspace at the log-in prompt it will drop me into text-mode log-in without restarting X or SLiM.
Can it be configured to respawn if X is killed?
i have the following in my inittab:
#
# /etc/inittab
#
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty 38400 vc/6 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
x:5:respawn:/usr/bin/slim >& /dev/null
# End of file
Offline
try just x:5:respawn:/usr/bin/slim
Offline
I just want to second the OP's findings. SLiM used to restart with no difficulties after a C+A+Backspace. Now it switches to vc/1 and hangs indefinitely until its killed by hand. This isn't normal behaviour and wooptoo's /etc/inittab is configured correctly.
Last edited by thayer.w (2007-09-28 23:48:50)
thayer williams ~ cinderwick.ca
Offline
I just rebuilt SLiM with the previous PKGBUILD and it's still hanging, so it must be due to some other package that was recently updated.
thayer williams ~ cinderwick.ca
Offline
I have tried today after I've seen this thread and it works fine on my computer. I have slim set up using the inittab method and like daf666 described it above (no /dev/null stuff).
Offline
I just want to second the OP's findings. SLiM used to restart with no difficulties after a C+A+Backspace. Now it switches to vc/1 and hangs indefinitely until its killed by hand. This isn't normal behaviour and wooptoo's /etc/inittab is configured correctly.
I agree, I've been experiencing the same with 1.3.0. I thought it was just me... 'Good' to see it's not. I haven't tried without the >& /dev/null though.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I tried it without the >& /dev/null config after a reboot and it still isn't working. wooptoo and B, by chance have you guys installed the libx11 from the [testing] repo? I'm wondering if this has anything to do with it... it's the only non-stable package I have installed.
thayer williams ~ cinderwick.ca
Offline
thayer - I don't know it it helps but I have the testing repo fully enabled, so I don't think it's the libx11...
Offline
Thanks, I guess it's not that then. I wonder what it could be...
thayer williams ~ cinderwick.ca
Offline
This might be a bit unrelated, but when SLiM respawns for me, it takes around ~20 seconds before SLiM to start (X starts fast, but then it's just a black screen and a cursor until SLiM starts). This problem doesn't occur for me when I'm trying the setup on another computer, so it seems like a hardware specific problem.
Which leads me to wounder: have anyone of you with the "drop to text mode" problem tried running your setup on another computer?
Offline
I tried it without the >& /dev/null config after a reboot and it still isn't working. wooptoo and B, by chance have you guys installed the libx11 from the [testing] repo? I'm wondering if this has anything to do with it... it's the only non-stable package I have installed.
This is what I have:
[stijn@hephaistos ~]$ pacman -Qi libx11 | grep -i version
Version : 1.1.3-4
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I tried without >& /dev/null and SLiM restarts, but after about 10-20 seconds...
Offline
It should work with or without ">& /dev/null", and yes, sometimes it can take a while. I would suggest putting ">& /dev/null" back in, I know I did - I'm not sure what it does but this is what the authors of slim suggest using.
Offline
It just redirects output, nothing more. Makes for cleaner consoles .
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Same Problem here....
There is one thing even more vital to science than intelligent methods; and that is, the sincere desire to find out the truth, whatever it may be.
Charles S. Peirce
Offline
I hope no one takes this the wrong way, but I'm glad that there are more than just me that got the slow restarting problem...
Offline
I'd like to add - for what it's worth - that SLiM seems to max out my CPU too after Ctrl+Alt+Backspace. It will only respawn if you kill its process.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I have filed a bug report and Phrakture is looking into it as time permits.
Last edited by thayer.w (2007-10-31 18:39:57)
thayer williams ~ cinderwick.ca
Offline
yeah i got this problem too
Check me out on twitter!!! twitter.com/The_Ringmaster
Offline
Same problem here.
I have this problem since 2007-10-14 and can't find a solution.
There was a huge update amongst others "xkeyboard-config (0.9-2 -> 1.0-1)", and I think there is the problem.
I use slim too, but I don't believe slim is the problem.
EDIT:
After a try ctrl-alt-backspace, my slim.log says this:
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux arch 2.6.23-ARCH #1 SMP PREEMPT Sat Oct 27 09:04:14 UTC 2007 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 30 21:44:55 2007
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
/usr/bin/xauth: creating new authority file /home/jean/.Xauthority
Warning: Only changing the first 14 of 20 buttons.
** Message: This build doesn't include support for XF86Misc extension
** Message: Querying Xkb extension
** Message: Xkb extension found
** Message: Querying Xkb extension
** Message: Xkb extension found
Conky: desktop window (1000003) is subwindow of root window (1a5)
Conky: window type - override
Conky: drawing to created window (1800001)
Conky: drawing to double buffer
(xfwm4:8279): libxfcegui4-WARNING **: ICE I/O Error
(xfwm4:8279): libxfcegui4-WARNING **: Disconnected from session manager.
xfce-mcs-manager: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
xfwm4: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
xfdesktop: Fatal IO error 104 (Die Verbindung wurde vom Kommunikationspartner zurückgesetzt) on X server :0.0.
xfce4-panel: Fatal IO error 4 (Unterbrechung während des Betriebssystemaufrufs) on X server :0.0.
terminal: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 3, should be 1; fixing.
/usr/bin/xauth: creating new authority file /var/run/slim.auth
Jean-Paul
Last edited by jean-paul (2007-10-31 22:17:14)
I'm root. if you see me smile, you'd better have a backup!!
Offline
I'm also dealing with this issue and my story isn't any different than for the rest here in this thread, besides one more issue I haven't been able to track down.
The other issue might not be related but started to show at the exact same time. If I logout I'm first met by a screen, which is for a second full of messages about two programs running with the same PID. I've looked through the logs, but I can't find any of these messages, so I don't know what processes causing this.
It's annoying that X is running fine (...sometimes I get the message after ctrl+alt+backspace or logout that X is responding too fast, what does that mean?) so looking at the cursor while SLiM is taking its time can be annoying.
Offline
Have anybody found solution for this problem?
Offline
I have really found nothing, but I didn't delve into the code too much. I have a feeling it's a simple upstream bug.
Offline
My solution was to stop using a login manager period. Obviously, that's not good enough for others, but in case anyone is interested I just added this to ~/.bashrc:
# Start X if logging in at VC/1 and save debug info to ~/.myXLog
if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/vc/1 ]]; then
startx >& .myXLog
logout
fi
This will startx automatically when you into the first console and then log errors to ~/.myXLog. Restarting X will automatically bring you back to the login prompt.
thayer williams ~ cinderwick.ca
Offline
thayer, I read this on a thread about display managers / how to start X:
Me, I just use startx from console - I manually run it. I also have startx aliased to 'exec startx' so that if I have the computer locked, someone can't just change to VC1, ctrl-C, and use my PC. If they kill the startx process, it kicks them back to login.
Saves you from adding that second 'logout' line, and it's safer (if ever that's useful to you).
Offline