Hello
I have upgraded from 12 to 13, keeping my home directory.
I can log in as root, but not as a user - I always get the message"Failed to execute login command".
This is exactly the same problem that was reported in post cannot-login-for-user-t2332.html?hilit=failed%20to%20execute%20login%20command
I followed the instructions given then (copy .xinitrc and contents of Documents & Wallpaper from /etc/skel to /home/"myusername"), but no change.
Any ideas?
Thanks
Frank
-
Posts: 15
- Joined: 19 Feb 2013
#1
Last edited by frank4360 on 17 Jun 2013, 16:02, edited 1 time in total.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#2
Have a look at /etc/slim.conf and make sure user is correct
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#3
Also copy over the hidden antix-session files
-
Posts: 15
- Joined: 19 Feb 2013
#4
No change - still getting Failed to execute login command.
I set"default_user" to frank, and this shows at bootup; I could not see any other reference to"user" in slim.conf.anticapitalista wrote:Have a look at /etc/slim.conf and make sure user is correct
No change - still getting Failed to execute login command.
I have copied over the directory .antix-session and also the files in the directory to /home/frank - no change.Also copy over the hidden antix-session files
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#5
Post your .xinitrc file and /etc/slim.conf
-
Posts: 15
- Joined: 19 Feb 2013
#6
.xinitrc
slim.confanticapitalista wrote:Post your .xinitrc file and /etc/slim.conf
Code: Select all
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
default_xserver /usr/bin/X
xserver_arguments -dpi 96 -nolisten tcp
# Commands for halt, login, etc.
halt_cmd /usr/local/bin/persist-config --shutdown --command halt
reboot_cmd /usr/local/bin/persist-config --shutdown --command reboot
console_cmd /usr/bin/urxvt -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 off
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
hidecursor true
# 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/bash -login /etc/X11/Xsession %session
login_cmd exec /bin/bash -login ~/.xinitrc %session >~/.xsession-errors$DISPLAY 2>&1
# login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1
# 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 /usr/bin/sessreg -a -l $DISPLAY %user
sessionstop_cmd /usr/bin/sessreg -d -l $DISPLAY %user
# Start in daemon mode. Valid values: yes | no
# Note that this can overridden by the command line
# option"-d"
# 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 dwm,rox-fluxbox,space-fluxbox,fluxbox,rox-icewm,space-icewm,icewm,rox-jwm,space-jwm,jwm,wmii
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd scrot /tmp/slim.png
# welcome message. Available variables: %host, %domain
welcome_msg (Press F1 to toggle sessions)
# shutdown / reboot messages
shutdown_msg The system is shutting down...
reboot_msg The system is rebooting...
# 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
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme antiX
# Lock file
lockfile /var/run/slim.lock
# Log file
logfile /var/log/slim.log
#auto_login yes
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user frank
.xinitrc
Code: Select all
#----------------------------------------------------------------------
# .xinitrc
#
# Created by /usr/share/antiX/lib/make-xinitrc
# on 1 June 2013 @ 16:44:58 EDT
# Please add any modifications to .xinitrc-custom and not this file.
# This file will be re-written by update-default-desktop. The
# DEFAULT_DESKTOP line will be edited by antiX-init if you select
# a desktop via the bootloader menu or a"desktop=xxx" boot parameter.
#----------------------------------------------------------------------
[ -x ~/.xinitrc-custom ] && ~/.xinitrc-custom
[ -f ~/.Xmodmap ] && xmodmap ~/.Xmodmap
DEFAULT_DESKTOP="rox-jwm"
DESKTOP_CODE="$(echo"${1:-$DEFAULT_DESKTOP}" | tr"[A-Z]""[a-z]")"
sdir=$HOME/.antix-session
mkdir -p $sdir
display=${DISPLAY%.[0-9]}
echo"$DESKTOP_CODE" > $sdir/desktop-code$DISPLAY
echo $$ > $sdir/xinitrc-pid:$display
case"$DESKTOP_CODE" in
rox-fluxbox)
rox --pinboard=antiX-fluxbox
exec /usr/bin/startfluxbox
;;
space-fluxbox)
spacefm --desktop &
exec /usr/bin/startfluxbox
;;
fluxbox)
exec /usr/bin/startfluxbox
;;
rox-icewm)
rox --pinboard=antiX-icewm
exec /usr/bin/icewm-session
;;
space-icewm)
spacefm --desktop &
exec /usr/bin/icewm-session
;;
icewm)
exec /usr/bin/icewm-session
;;
rox-jwm)
rox --pinboard=antiX-jwm
exec /usr/bin/jwm
;;
space-jwm)
spacefm --desktop &
exec /usr/bin/jwm
;;
jwm)
exec /usr/bin/jwm
;;
wmii)
exec wmii
;;
*)
echo"Unknown DESKTOP_CODE: $DESKTOP_CODE" >&2
echo"Setting DESKTOP_CODE to rox-icewm" >&2
DESKTOP_CODE="rox-icewm"
echo"$DESKTOP_CODE" > $HOME/.antix-session/desktop-code$DISPLAY
rox --pinboard=antiX-icewm
exec /usr/bin/icewm-session
;;
esac
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#7
Do you have an .antix-session/desktop-code file?
Something like this desktop-code:0.0 with contents
rox-icewm
If not make one.
Something like this desktop-code:0.0 with contents
rox-icewm
If not make one.
-
Posts: 15
- Joined: 19 Feb 2013
#8
No change on reboot.
No such file in /home/frank - I copied one from /root/.antix-session directory and changed owner and group to frank. I added"rox-icewm".anticapitalista wrote:Do you have an .antix-session/desktop-code file?
Something like this desktop-code:0.0 with contents
rox-icewm
If not make one.
No change on reboot.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#9
Hmm.
Remove/purge slim
apt-get purge slim
reboot and login to the session with your name and password then type startx.
If that works, then slim is the problem.
If it doesn't work, then there is a problem with .xinitrc/antix-session
What desktop are you using? ice with rox?
Remove/purge slim
apt-get purge slim
reboot and login to the session with your name and password then type startx.
If that works, then slim is the problem.
If it doesn't work, then there is a problem with .xinitrc/antix-session
What desktop are you using? ice with rox?
-
Posts: 15
- Joined: 19 Feb 2013
#10
I removed slim (apt-get purge slim) and rebooted; et voila - login with my username worked!
There was no need to"startx".
I am using JWM.
At present the system is not finding any wireless networks - but I seem to recall that there was the same problem with the initial install of AntiX and I found that I needed special driver for the wireless card. I will cry for help later if I can't resolve that issue.
Thanks for your help - I know it is often not possible to identify the cause of such a problem, but do you know what may have been the fault?
thanks again.
Frank
There was no need to"startx".
I am using JWM.
At present the system is not finding any wireless networks - but I seem to recall that there was the same problem with the initial install of AntiX and I found that I needed special driver for the wireless card. I will cry for help later if I can't resolve that issue.
Thanks for your help - I know it is often not possible to identify the cause of such a problem, but do you know what may have been the fault?
thanks again.
Frank
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#11
Probably slim login manager.
If you want you could try installing it and see what happens.
Make sure the antiX repo is enabled.
If you want you could try installing it and see what happens.
Make sure the antiX repo is enabled.
-
Posts: 15
- Joined: 19 Feb 2013
#12
Resolved!
The problem seems to be that I was installing the full AntiX 13 - I am running it on an old AcerAspireOne with just 8GB of Solid State Disk - this leaves about 6.5GB for the installation.
After numerous problems with the full .iso I tried re-installing, and only then realised that I should try the base version.
I have installed the base version and all the problems relating to"Failed to execute login command" (as well as various others) have now disappeared.
The problem seems to be that I was installing the full AntiX 13 - I am running it on an old AcerAspireOne with just 8GB of Solid State Disk - this leaves about 6.5GB for the installation.
After numerous problems with the full .iso I tried re-installing, and only then realised that I should try the base version.
I have installed the base version and all the problems relating to"Failed to execute login command" (as well as various others) have now disappeared.
-
Posts: 1,308
- Joined: 31 Aug 2009
#13
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepisimo.com/antix/Released/antiX-13/FAQ/index.html#_system_requirements"
linktext was:"Minumum System Requirements"
====================================
.
OTOH, I can't imagine why antiX-full would require even close to 6 Gig of disk space. You can check the md5 of the antiX-full install media by selecting"check md5" in the"F4 Options" menu. If that's good then I wonder if there is something wrong with the ssd.
If this is really the problem then we need to bump up the disk spaces needed in thefrank4360 wrote:The problem seems to be that I was installing the full AntiX 13 - I am running it on an old AcerAspireOne with just 8GB of Solid State Disk - this leaves about 6.5GB for the installation.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepisimo.com/antix/Released/antiX-13/FAQ/index.html#_system_requirements"
linktext was:"Minumum System Requirements"
====================================
.
OTOH, I can't imagine why antiX-full would require even close to 6 Gig of disk space. You can check the md5 of the antiX-full install media by selecting"check md5" in the"F4 Options" menu. If that's good then I wonder if there is something wrong with the ssd.
-
Posts: 15
frank4360 - Joined: 19 Feb 2013
#14
Bear in mind that I preserved the /home directory during the installation of the base system.
The total disk usage shown with"du" is 5.4G, of which /home is only 1.1G.
/usr shows as 2.9G, of which /usr/lib is 1.3G and /usr/share is 1.2G.
/var is 1.2G, of which /var/cache is 772meg.
/home seems correct to me, but the others look excessive - only about 500 meg is available on the SSD!
The total disk usage shown with"du" is 5.4G, of which /home is only 1.1G.
/usr shows as 2.9G, of which /usr/lib is 1.3G and /usr/share is 1.2G.
/var is 1.2G, of which /var/cache is 772meg.
/home seems correct to me, but the others look excessive - only about 500 meg is available on the SSD!
-
Posts: 850
- Joined: 26 Jul 2012
#15
Those usage figures look too big to me, when I had '13 full beta3' installed, I'm sure it was less than 3gb, (2.7gb, I think), that was on a 64gb SSD.
That /var looks too big.
Edit: Using '13 base' takes around 1.6gb.
That /var looks too big.
Edit: Using '13 base' takes around 1.6gb.