You are not logged in.
Pages: 1
i have installed archlinux, openbox, slim, all up to date. followed all the wiki to configure X, slim, openbox......slim is started using inittab. everything is working except there is a very strange behavior with slim. when i log out, before slim login appear, i see a message saying "failed to execute login command"???!!!????? yes this happens at logout. another important detail: this happen since in my .xinit i change
exec openbox-session
by
exec ck-launch-session openbox-session
(yes i want a normal user be able to mount a dvd or whatever else using file manager like pcmanfm)
i have spend hours looking for information in google.......no solution for this small (but annoying) problem.
another problem that has been reported in arch forum is the impossibility to use correctly keyboard in vc/1 when just logged with slim.......https://lists.berlios.de/pipermail/slim … 00210.html
the only feel i have is that slim become less and less usable and no new maintener have been found (
we're currently looking for a new maintainer for the project. Please drop a message to the ML if you're interested!
). with the standardisation of using hal, dbus, *kit.......more and more problems appear......that's sad because slim is a nice DM, fast and minimal......
i even don't talk about pam support (ok we can patch and patch......but even if i like tweak and geek, sometime i would like someting more productive i you know what i mean).
ok that's not an "arch problem".
so if anyone has a solution for my little problem, i would appreciate a lot.
thanks
Offline
Not solving your problem but... pam support does not need patched in for slim and is enabled in the Arch package
Offline
happy to hear about pam support. i am sorry that i have not read enough.....i regret that this information is not mentioned in the slim wiki.
about my initial problem, (that appear using ck-launch-session), since i only use openbox instead of simply had this in my .xinitrc
exec ck-launch-session openbox-session
which cause the message appear at logout (failed to execute login command) , i have tested the script intended to manage multiple session:
DEFAULT_SESSION=openbox
case $1 in
openbox)
exec ck-launch-session openbox-session
;;
*)
exec ck-launch-session $DEFAULT_SESSION
;;
esac
that's crazy but the error message doesn't appear anymore.
i am happy for that but i would like to understand why......any idea?
thanks again
Offline
forget my previous message : it doesn't work even if i use the script intended for multiple session.
still have the problem at logout failed to execute login command
sad
Offline
Can you post the full ~/.xinitrc and /etc/slim.conf?
Also, are you using the testing repo for packages?
thayer williams ~ cinderwick.ca
Offline
hi again....
~/.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
export LC_ALL="fr_FR.UTF8"
xset -b
exec ck-launch-session openbox-session
and /etc/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 openbox,xfce4,icewm,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
another information : there are no backgrounds in my current conf and the message (failed to execute login command) appear in the middle of the main openbox display, just before logout.
i don't know if there is something to see with my ~/.config/.openbox/menu.xml
the problem occurs when i logout using SessionLogout (i repeat, this doesn't occurs if openbox is started directly using exec openbox-session. it happens only when using exec ck-launch-session openbox-session
<item label="Log Out">
<action name="SessionLogout">
<prompt>
yes
</prompt>
</action>
</item>
here is my /var/log/slim.log when i "SessionLogout" :
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
slim: waiting for X server to shut down
/usr/bin/xauth: creating new authority file /var/run/slim.auth
slim: waiting for X server to begin accepting connections
X.Org X Server 1.6.2
Release Date: 2009-7-7
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH i686
Current Operating System: Linux multhobox 2.6.30-ARCH #1 SMP PREEMPT Sat Jul 4 11:13:08 UTC 2009 i686
Build Date: 18 July 2009 08:27:13PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
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 Jul 21 09:55:09 2009
(==) Using default built-in configuration (30 lines)
(EE) Failed to load module "fbdev" (module does not exist, 0)
.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
hope those additional informations will be helpfull........
thanks
Offline
last note about the problem:
i have just made a new identicall install in vmware : same problem there...........
Offline
Try using GDM instead of slim I had loads of problems with LXDE which uses open box till I dumped slim then they disappeared like magic.
I'm dyslexic Please do not complain about puntuation or spelling and remember most dyslexic people have above average iq.
Offline
yes i think that actually this is something i really should to consider. i didn't wanna give up because i like the idea of using lightweight and tweakable piece of software but as i describe this thread, slim didn't follow the evolutions and the project will remain at dead point until a new motivated maintener take it back to life.
i am gonna dump slim right now, sad but have to be realistic......
thanks for your opinion and suggestion.
Offline
Qingy is a good login manager - a bit more trouble to install than slim, but the login screen is very configurable and a lot of fun to play with (translation: I've spent a ridiculous amount of time designing login themes which are, after all, only onscreen briefly). The Wiki has good info and the Qingy website is helpful.
Offline
thanks for the information. i will give a try.
as i know, it's not really a login manager (dm) but more a graphical login using directfb.......
cheers
Offline
Qingy is a good login manager - a bit more trouble to install than slim, but the login screen is very configurable and a lot of fun to play with (translation: I've spent a ridiculous amount of time designing login themes which are, after all, only onscreen briefly). The Wiki has good info and the Qingy website is helpful.
I had issues with qingy... every time I press a key, it echos twice (once on press, once on release). Anyone else had this problem/found a way to fix it?
Offline
I had issues with qingy... every time I press a key, it echos twice (once on press, once on release). Anyone else had this problem/found a way to fix it?
I did..... http://bbs.archlinux.org/viewtopic.php?id=76547
Hope it helps....
ILoveCandy
Offline
Ghost1227 wrote:I had issues with qingy... every time I press a key, it echos twice (once on press, once on release). Anyone else had this problem/found a way to fix it?
I did..... http://bbs.archlinux.org/viewtopic.php?id=76547
Hope it helps....
Good call! Don't know how I missed that...
Offline
It figures- the minute I recommend something it stops working.:rolleyes:
There are a couple other issues with the updated qingy & directfb, but this thread with Nnexxus' fix at the end was a huge help to me:
Offline
Offline
The easiest solution is to use no DM at all.
True, however at the bottom of that slippery slope lies ... pencil and paper?
Offline
thayer wrote:The easiest solution is to use no DM at all.
True, however at the bottom of that slippery slope lies ... pencil and paper?
Doing
x:5:respawn:/bin/su ataraxia -l -c "/usr/bin/xinit -- -nolisten tcp vt07"
in inittab works just fine for me. Of course, I don't recommend it if auto-login isn't appropriate for your security context.
Offline
thayer wrote:The easiest solution is to use no DM at all.
True, however at the bottom of that slippery slope lies ... pencil and paper?
Hardly...a DM is little more than vanity. A fancy wallpaper to glance at while you enter your username and password. Sure, some folks use the more advanced features of KDM/GDM such as directly logging into a remote host or choosing among several installed WM/DE setups, but most folks use it to log into the same ol' desktop.
I prefer the console login myself...the only real advantage I found to using a DM is that it started X before I logged in. However this too can be accomplished in other ways, such as ataraxia's example.
To each their own really, I just prefer simplicity.
thayer williams ~ cinderwick.ca
Offline
sonoran wrote:thayer wrote:The easiest solution is to use no DM at all.
True, however at the bottom of that slippery slope lies ... pencil and paper?
Hardly...a DM is little more than vanity. A fancy wallpaper to glance at while you enter your username and password. Sure, some folks use the more advanced features of KDM/GDM such as directly logging into a remote host or choosing among several installed WM/DE setups, but most folks use it to log into the same ol' desktop.
I prefer the console login myself...the only real advantage I found to using a DM is that it started X before I logged in. However this too can be accomplished in other ways, such as ataraxia's example.
To each their own really, I just prefer simplicity.
I prefer an uncluttered desktop also - plain background, no icons, no tray, no menu bar, just pypanel and a very restrained gkrellm.
So I indulge myself with fancy qingy login screens. We all have our vices.;)
Offline
There is an advantage with a small DM in that X starts way before the VC login prompt appears.
Last edited by Wintervenom (2009-08-03 13:27:33)
Offline
hi again....
~/.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 export LC_ALL="fr_FR.UTF8" xset -b exec ck-launch-session openbox-session
Just a sidenote, that should be LC_ALL="fr_FR.utf8"
You have to specify it exactly as locale -a shows it, so no uppercases or -'s
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Pages: 1