Slim freezes after entering login information

slamhound · 2012-07-16 10:30:00

I have a strange problem with Slim. I've used it for a while and everything has always worked fine (indeed, a different computer with similar setup is still fine), but two weeks ago I couldn't log in. The problem did not develop after an update of slim. I haven't found any similar symptoms described in the forums or wiki.

I start slim through the inittab method, and I usually boot into awesome, but sometimes into openbox, so I followed the instructions for setting up slim for multiple environments. Booting into either worked fine previously.

Now when booting, I can get to slim fine. If I immediately enter my user info and then hit "enter" to start the default WM (which is awesome), then slim just freezes. The user and password box disappear, but the background remains, and nothing else happens. I need to use ctl-alt-F1 to login again from tty and reboot. The strange thing is that if after booting, I enter my user info into slim and then hit "F1" then I can select awesome and boot normally. But just hitting enter after user and password (which should boot the default WM, which is awesome) without selecting awesome from F1 causes the freeze. Also, if I use F1 to select openbox, I get the same freeze.

I have tried modifying my .xinitrc just to open awesome rather than using the multiple-environment setup (see below), and with this .xinitrc, I still got the freezing problem, but obviously couldn't get around it by using F1.

Finally, if I get into awesome using the F1 method and then logout of awesome to go back to slim, then logging in to either awesome without hitting F1 or even logging in to openbox work fine. Very strange.

My slim.log has absolutely nothing useful in it. Here are the last lines from the last 7 boots (the ones where it says "Slim: unexpected signal 15" are the ones where I had to use tty to reboot, the others are where I've booted successfully).

slim: waiting for X server to begin accepting connections.
slim: unexpected signal 15


slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.
slim: unexpected signal 15


slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.
slim: unexpected signal 15


slim: waiting for X server to begin accepting connections.

Here's my .xinitrc. When testing whether the multiple-environment setup was the problem, I commented everything except the last line (which I uncommented) and still had the same problem.

#xset +fp /usr/share/fonts/local
#xset fp rehash

#exec ck-launch-session dbus-launch openbox-session

DEFAULT_SESSION=awesome

case $1 in
awesome)
#	exec dbus-launch awesome
	exec awesome
	;;
openbox)
#	exec dbus-launch openbox-session
	exec openbox-session
	;;
*)
	exec $DEFAULT_SESSION
	;;
esac

#exec awesome

Here's my slim.conf. Everything should be the default settings except for the login command (where I added "dbus-launch") and the sessions line where I specify options for awesome and openbox.

# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path        /bin:/usr/bin:/usr/local/bin
default_xserver     /usr/bin/X
xserver_arguments -nolisten tcp vt07

# Commands for halt, login, etc.
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend

# Full path to the xauth binary
xauth_path         /usr/bin/xauth 

# Xauth file for server
authfile           /var/run/slim.auth


# Activate numlock when slim starts. Valid values: on|off
# numlock             on

# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor          false

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd           exec /bin/sh - ~/.xinitrc %session
# login_cmd           exec /bin/bash -login ~/.xinitrc %session
login_cmd           exec dbus-launch /bin/bash -login ~/.xinitrc %session

# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd	some command
# sessionstop_cmd	some command

# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon	yes

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions            awesome,openbox

# Executed when pressing F11 (requires imagemagick)
screenshot_cmd      import -window root /slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         Welcome to %host

# Session message. Prepended to the session name when pressing F1
# session_msg         Session: 

# shutdown / reboot messages
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user        simone

# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password      no

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login          no


# current theme, use comma separated list to specify a set to 
# randomly choose from
current_theme       default

# Lock file
lockfile            /var/lock/slim.lock

# Log file
logfile             /var/log/slim.log

Anyway, I can get around this by using F1, but it is somewhat of a pain as sometimes I forget. Any ideas?

lachesis · 2012-07-17 04:27:35

The exact same thing happens to me. Using slim and awesome. My problem appeared after I installed pulseaudio, but I don't think that's the culprit. I've found that if I go to tty1, log in, and repeatedly issue "DISPLAY=:0 xterm" (ctrl-c'ing each one and running again), I eventually get dumped at my awesome desktop with a running xterm.

rasteenb · 2012-07-17 10:51:54

I'm having a very similar problem. My post is in the newbie corner forum. So far, I have not found a solution.
Rob

rasteenb wrote:

I solved my problem - slim was not the last daemon I started in rc.conf. By moving it to the end, I get password auto-focus and everything works.
Now my rc.conf looks like
# DAEMONS
# -------
#
DAEMONS=(syslog-ng dbus acpid @network @wicd @openntpd @cupsd @crond slim)
I found this recommendation in the Display Manager wiki page while researching the problem:
Ensure you start the display manager last in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by Getty (see /etc/inittab). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.
I'd just been lucky before that there wasn't a conflict.
There is a "flicker" during login where I'm shown the XFCE splash, then the SLIM splash again, then the XFCE desktop. Not sure what's going on there, but it's no big deal.
Cheers,
Rob

Last edited by rasteenb (2012-07-17 11:30:39)

zasdfgbnm · 2012-07-18 01:31:43

I'm having the same problem with you.

lachesis · 2012-07-18 06:38:55

So, it turns out that it was pulseaudio that caused the problem. When I removed pulseaudio and pulseaudio-alsa, awesome stopped freezing. I'm not sure why, and that's not really an acceptable solution for me, but now my machine boots again...

slamhound · 2012-07-18 08:38:57

Hmm . . . I've always had pulse installed, so it would seem strange if that were my problem. I am also reluctant to remove it, as it took a while to get all sound working with all programs, and I don't want to screw up my delicate balance. The symptom that has always seemed most strange to me is that awesome boots fine if I just F1 through the options to get to awesome (which is what I'm doing now to work around this issue).

@rasteenb: I think this might be a different issue, as I don't use the daemon method for starting slim, I use inittab.

bjschuma · 2012-07-18 13:05:59

I was having this problem too (without pulse installed). I needed to set up slim to log me in automatically for it to work.

derhamster · 2012-07-18 22:12:02

Having the same problem on a fresh arch installation. Slim is started through systemd. Pulse is not installed.
It always happens on my first login attempt. After I kill and restart slim from another console, it seems completely random if the problem persists.
When I just restart slim through systemd and leave the first one in its frozen state, login works always. But then the session does not get registered with consolekit correctly.
I'll look into this more deeply tomorrow.

zasdfgbnm · 2012-07-19 00:58:47

My slim is started by initscripts, not systemd. But the same problem happened.

jakobcreutzfeldt · 2012-07-26 14:54:04

I'm having this exact same problem (already posted it in a different thread because I didn't find this one; https://bbs.archlinux.org/viewtopic.php … #p1136088).

I'm starting with Systemd. The only thing that stuck out to me was that slim.conf was still putting things in /var/run, while the rest of Arch has moved files to /run. I modified my slim.conf accordingly (auth file at /run/slim.auth and lock file at /run/lock/slim.lock) but that didn't fix the problem. I'll work on it again this evening.

jakobcreutzfeldt · 2012-07-26 17:56:26

Ok, digging into my systemd log, I saw this as the last entry from slim before I killed the process:

slim[317]: *** glibc detected *** /usr/bin/slim: malloc(): memory corruption: 0x0000000001a2fa90 ***

That doesn't bode well...
I'll keep digging.

Edit: I've just double checked and verified that this indeed happens only after the login attempt. As soon as Slim freezes, this shows up in the log.

Last edited by jakobcreutzfeldt (2012-07-26 17:59:53)

jakobcreutzfeldt · 2012-07-26 18:11:40

Ok, for me the problem was resolved by installing slim-nock (Slim without Consolekit support) from the AUR.

jakobcreutzfeldt · 2012-07-26 18:22:30

Bug reported:
https://bugs.archlinux.org/task/30864

DuncanvR · 2012-09-05 12:13:43

After getting several similar errors and doing some searching, I found this (quite unrelated) thread: http://forum.soft32.com/linux/glibc-det … 52898.html
Applying this approach, i.e. executing the following, works for me!

root > LD_ASSUME_KERNEL=`uname -r | sed 's:\([0-9\.]*\).*:\1:'`
root > export LD_ASSUME_KERNEL
root > systemctl restart slim.service

Nevermind, upon restart this had no effect.

Last edited by DuncanvR (2012-09-05 13:13:58)

eocampos · 2012-09-12 12:24:08

jakobcreutzfeldt wrote:

Ok, for me the problem was resolved by installing slim-nock (Slim without Consolekit support) from the AUR.

I have this problem too and I solved it by installing slim-nock as you said, though I don't know what is the difference between slim and slim-nock. The freezing problem appeared after a power outage at my office.

71GA · 2012-09-27 03:16:56

Same problem here.

r0b0t · 2012-10-31 20:28:50

I have the same problem, even after installing slim-svn (no slim-nock on AUR) however from the last version slim is supposed to not suppot CK so with the SVN of today we can be sure that isn't supporting however the same problem, after the system starts up, I have to wait allot, and sometimes even I'm forced to restart, the last time worked normally however this is one in 5..
Didn't notice here anyway any malloc() errors.

$ cat /var/log/slim.log 


slim: waiting for X server to begin accepting connections.
slim: unexpected signal 15
slim: connection to X server lost.

slim: waiting for X server to shut down



slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.
slim: unexpected signal 15
slim: connection to X server lost.

slim: waiting for X server to shut down


slim: unexpected signal 15

slim: unexpected signal 15


slim: waiting for X server to begin accepting connections.slim: unexpected signal 15

slim: unexpected signal 15


slim: waiting for X server to begin accepting connections.

Any suggestion would be much appriciated.

r0b0t · 2012-11-01 12:11:03

I just removed it and now I'm not using any login manager, guess, ,,, works fine

Arch Linux

#1 2012-07-16 10:30:00

Slim freezes after entering login information

#2 2012-07-17 04:27:35

Re: Slim freezes after entering login information

#3 2012-07-17 10:51:54

Re: Slim freezes after entering login information

#4 2012-07-18 01:31:43

Re: Slim freezes after entering login information

#5 2012-07-18 06:38:55

Re: Slim freezes after entering login information

#6 2012-07-18 08:38:57

Re: Slim freezes after entering login information

#7 2012-07-18 13:05:59

Re: Slim freezes after entering login information

#8 2012-07-18 22:12:02

Re: Slim freezes after entering login information

#9 2012-07-19 00:58:47

Re: Slim freezes after entering login information

#10 2012-07-26 14:54:04

Re: Slim freezes after entering login information

#11 2012-07-26 17:56:26

Re: Slim freezes after entering login information

#12 2012-07-26 18:11:40

Re: Slim freezes after entering login information

#13 2012-07-26 18:22:30

Re: Slim freezes after entering login information

#14 2012-09-05 12:13:43

Re: Slim freezes after entering login information

#15 2012-09-12 12:24:08

Re: Slim freezes after entering login information

#16 2012-09-27 03:16:56

Re: Slim freezes after entering login information

#17 2012-10-31 20:28:50

Re: Slim freezes after entering login information

#18 2012-11-01 12:11:03

Re: Slim freezes after entering login information

Board footer