You are not logged in.
Pages: 1
hi
I just did a full system upgrade (was not very much). Slim was updated, too.
Now I cannot login. I just get dropped to the login without an error message. Where might I find a log-file?
(Logging in using the TTY still works fine)
regards,
Keen
Last edited by keen90 (2012-05-10 17:22:07)
Offline
Ok i found the file - but I'm not sure what to do now.
(it is in /var/log/slim.log)
/usr/bin/xauth: file /var/run/slim.auth does not exist
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Server terminated with error (1). Closing log file.
/var/run/slim.auth does exist, I just checked
Xorg.0.log stores the same text as this message.
Last edited by keen90 (2012-05-10 06:44:10)
Offline
May I should describe better:
slim does start fine and when I enter my login I get a can see that x tries to start, since the screen turns black for maybe half a second. But usualy I then end up with my xfce-desktop and since the last update I only get the slim login again.
Offline
Please post your slim.conf
Offline
# 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
# 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 xfce4,icewm-session,wmaker,blackbox
# 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
Offline
Post your .xinitrc as well. Also check the permissions on it.
meh
Offline
xinitrc:
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
exec startxfce4
#exec xmonad
# ...or the Window Manager of your choice
permissions:
-rw-r--r-- 1 maex users 323 Apr 23 12:10 /home/maex/.xinitrc
Offline
run
chmod +x ~/.xinitrc
It looks like it is not executable.
meh
Offline
nope, that did not help :-(
Offline
what are the permissions on the file now?
meh
Offline
I have the same symptoms (which is why I posted https://bbs.archlinux.org/viewtopic.php?id=141277). In my case I know that the problem is because consolekit cannot run (because dbus is not running).
Can you try
ck-list-sessions
If that works (and reports only one session) then you probably have CK working.
If it fails (as in my case) then you probably also have no dbus.
If it works and reports more than one session (unlikely in your case) then check the numerous other posts detailing how to get CK working with slim.
Hope that helps, R.
Offline
permissions now are:
-rwxr-xr-x 1 maex users 323 Apr 23 12:10 .xinitrc
so it is executable for anyone
but I also got the dbus symptoms:
maex@cobalt:~ $ ck-list-sessions
** Message: Failed to connect to the D-Bus daemon: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Offline
That explains it.
The recent change to slim which is breaking things is that it now uses something called 'consolekit' (and in turn consolekit requires dbus). Almost everyone else has consolekit already installed and it encountering a different problem (multiple nested CK sessions). You and I seem to be the only ones who do not yet have consolekit and dbus enabled and so are seeing the symptoms above.
I posted a similar thread and was given some helpful advice a short while ago. There seems to be only two solutions:
- enable dbus (it's all listed in the wiki - but basically you just add it to rc.conf daemons)
or
- don't use slim
Hope that helps, R.
Offline
...
Last edited by keen90 (2012-05-10 13:13:43)
Offline
'...' is not a very helpful reply. Was there something else?
Offline
There is another way for you:
Compile slim using ABS and remove the consolekit dependency and change
-DUSE_CONSOLEKIT=yes
to
-DUSE_CONSOLEKIT=no
Removing that should work too, but I haven't tested that.
EDIT: replaced AUR with ABS
Last edited by leper (2012-05-10 17:47:18)
Offline
There was, but when I submited you had already answered that question ;-)
(so I removed the post)
Thanks for all the help - I guess I'll just use the previous version of slim.
Offline
I had this problem this morning also - running Slim with Awesome WM, after login I would just get a black screen.
Adding dbus to the startup daemons in rc.conf did the trick.
Offline
The same happened to me. I can confirm that dbus was the issue...
Offline
Pages: 1