You are not logged in.
Pages: 1
Slim authentification doesn't work for me. After entering the password,
it goes back and prompts me for the username again. This happens for
the right username/password combination, as well as for wrong passwords
and/or users.
I start slim in deamon mode. X itself works, when i start it with startx.
Another issue: when i try to preview the slim themes as suggested in the
wiki with
$ slim -p /usr/share/slim/themes/<theme name>
i get the following error:
slim: could not open display ':0.0'
No X server is running at this point.
Offline
Although this is probably a user/setting - error, I must warn you that slim has been unmaintained for a while now, so using it is 'deprecated': as long as it works for you, good for you - if/when it breaks, bad for you
I use lxdm as an alternative for slim.
/EDIT: and as for Xserver-errors:
<SNIP - it's early> If no Xserver is running, that preview won't work. Just open up a terminal in X and type that command
as for slim error: try setting it up in inittab and disabling the daemon and see if that works.
Last edited by zenlord (2010-08-16 07:50:51)
Offline
I have no special preference for slim, i just installed it because
it was recommended in the wiki.
I may try your suggestions, but if it's deprecated anyway, why bother?
Maybe i'm just going to kick it and use lxdm, if that's in style now...
edit:
From http://wiki.archlinux.org/index.php/DM:
Note: It is best practice, but not required, to choose the display manager that corresponds to your desktop environment. Typically SLiM is preferred if there is not a corresponding desktop environment.
And i just realised, there is no wiki entry for lxdm. Is it that trivial to
configure that one doesn't need one?
Last edited by MickeyKnox (2010-08-16 11:04:21)
Offline
What DE or WM do you use?
I don't know why SLiM should be labelled "deprecated" as long as it works and does what it's supposed to do. I would guess your problem has to do with an inconsistency between .xinitrc and slim.conf. Could you post both here, please?
No need to jump from one solution to another. Better to figure out why something works or doesn't work.
Offline
What DE or WM do you use?
awesome
I don't know why SLiM should be labelled "deprecated" as long as it works and does what it's supposed to do. I would guess your problem has to do with an inconsistency between .xinitrc and slim.conf. Could you post both here, please?
Unfortunately, i'm not sitting in front of my machine right now.
But i think i know pretty much what i did.
.xinitrc just states 'exec awesome'.
In /etc/slim.conf i configured somewhere to use awesome.
There was a line with some sample wm's. I deleted those and put
awesome in. Besides that i just changed the theme, i think.
Sorry for this, i'll post slim.conf as soon as i get back...
Offline
There we go.
.xinitrc:
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
exec awesome
and slim.conf:
# 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 awesome
# 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 archlinux-simplyblack
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
Offline
A fast glance doesn't reveal anything odd in my eyes.
Does a simple startx without any argument start up awesome?
Offline
Does a simple startx without any argument start up awesome?
yes. That's how i use it.
edit:
For me it looks like slim doesn't get the authentification right.
Just a couriousity to other slim users: What is the behaviour of
slim when you mistype your password?
Last edited by MickeyKnox (2010-08-16 18:45:08)
Offline
I use SLiM on several computers. If you mistype it "hesitates" for a couple of seconds and then send you back to the beginning, username.
Offline
I use SLiM on several computers. If you mistype it "hesitates" for a couple of seconds and then send you back to the beginning, username.
That is exactly the behaviour i observe. So i guess there is something
wrong with the authentification.
Last edited by MickeyKnox (2010-08-16 19:38:00)
Offline
I apologize if this sounds like a stupid question: it's not just a keyboard layout problem, when you think you're typing the password right while the hidden output is something else?
Offline
Actually, that wasn't a stupid question. That was just my problem.
Thank you for your help.
Offline
I don't know why SLiM should be labelled "deprecated" as long as it works and does what it's supposed to do.
It is not officially deprecated, but development has stopped almost two years ago, and the package still has unresolved bugs. That oughtta be enough to stop using it if it doesn't work for you.
OK - just as I went checking the SLiM-dev pages to backup my story, I noticed that development has been picked up: after 2 years there is a minor update, released on 7/7/2010...
So, nevermind - although I kinda like lxdm. It has no wiki, admittedly, but it is as simple as adding lxdm to your inittab en configuring it in /etc/ ...
Offline
slim: could not open display ':0.0'
Try this when window manager is launched (in xterm or smth else)
Last edited by Palme (2010-11-20 05:55:28)
Offline
Pages: 1