SliTaz Forum

tux login failed

(22 posts) (7 voices)

• Started 11 years ago by michaelbischof
• Latest reply from michaelbischof
• This topic is not a support question

Tags:

No tags yet.

1. 

   michaelbischof
   

   offline

   Member

   Uff, I now have this login problem again and again. More than a week ago it helped to create a new user and login as this new user. Now on Slitaz 4 even this does not help. To copy the content of /etc/skel to /home/user and a "chown -R user:user /home/user/*" does not hope as well. The advice of @emgi (Password) does not help as well. Where might I find the culprit?

   Posted 11 years ago #
2. 

   emgi
   

   offline

   Member

   Hi Michael,

   Can you plerase elaborate a bit more on what exactly is going wrong?
   When I try this on my box I get this:
   tux@slitaz01's password:
   Access denied
   tux@slitaz01's password:
   Access denied

   But that is as expected because I never created user tux in the first place. ;-)
   Instead, I created user 'myname' and all has been working fine with this account ever since.

   Is 'tux' in your etc/passwd? It should be if you created it. Please check.
   Perhaps you used chown/chmod with incorrect parameters which accidentally modified file rigths in /etc? (Sorry for asking, I don't mean to offend, just considering all options)

   Creating user accounts is a basic feature of any linux distri and I've never heard or experienced issues with such a trivial matter. That does not mean you cannot have a problem but I cannot easily guess what it might be.
   One more tip: Did you check the documentation about this topic on the slitaz website?

   /emgi

   Posted 11 years ago #
3. 

   michaelbischof
   

   offline

   Member

   @emgi
   What happens is this: I start slitaz and then I see the login screen. It does not matter whether I use user „tux“ or user „michael“. I type either „tux“ and then the password for „tux“ or the same with user „michael“. In each case login fails with the comment: login execution failed.
   That is all. Login as „root“ with the root password works. With „passwd tux“ I had confirmed the right password, same with „michael“. It does not help. If I establish a new user, e.g. „mick“, with „adduser mick“ as root I am immediately prompted to set a password. I logout from root then, type „mick“ on the slim screen and then this password: again login execution fails. If I delete the content of „mick“ completely, all not visible files like .Xauthority as well, and copy the whole content of /etc/skel into /home/mick, including all those files and set the permissions „chown -R mick:mick /etc/home/mick/*“ it fails as well.
   No, of course you do not offend. It is trivial that sometimes one may do a trivial mistake! ;-)

   Posted 11 years ago #
4. 

   emgi
   

   offline

   Member

   Hi Michael,

   At least you have stated the error message: Login execution failed
   This should certainly evoke some useful hints about where to start looking.
   A forum search brought up this ancient post:
   http://forum.slitaz.org/topic/failed-to-execute-login-command-1#post-3030

   Personally I'm not using the GUI much, mostly CLI and that always works for me.
   I'm also adding users via the cli (is there another way ;-) and afterwards I've always been able to start a graphical session with these accounts.

   /emgi

   Posted 11 years ago #
5. 

   michaelbischof
   

   offline

   Member

   With F1 I checked. It showed „openboxB.
   The last lines of /var/log/messages are:
   Nov 1 12:03:36 (none) daemon.info init: starting pid 1467, tty '/dev/tty4': '/sbin/getty 38400 tty4'
   Nov 1 12:03:36 (none) user.notice error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1468]: error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1469]: bind failed: Address already in use
   Nov 1 12:03:36 (none) user.notice error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1469]: error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1471]: bind failed: Address already in use
   Nov 1 12:03:36 (none) daemon.info init: starting pid 1470, tty '/dev/tty5': '/sbin/getty 38400 tty5'
   Nov 1 12:03:36 (none) daemon.err udevd[1472]: bind failed: Address already in use
   Nov 1 12:03:36 (none) user.notice error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1471]: error binding udev control socket
   Nov 1 12:03:36 (none) user.notice error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1472]: error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1474]: bind failed: Address already in use
   Nov 1 12:03:36 (none) daemon.info init: starting pid 1473, tty '/dev/tty6': '/sbin/getty 38400 tty6'
   Nov 1 12:03:36 (none) daemon.err udevd[1475]: bind failed: Address already in use
   Nov 1 12:03:36 (none) user.notice error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1474]: error binding udev control socket
   Nov 1 12:03:36 (none) user.notice error binding udev control socket
   Nov 1 12:03:36 (none) daemon.err udevd[1475]: error binding udev control socket

   Any useful information for the advanced people here?

   Posted 11 years ago #
6. 

   christophe
   

   offline

   Member

   i've hit that a couple of time
   It is likely that one of the configuration files is missing in your home configuration.

   start checking if .xinitrc is there, slim will not login without it

   otherwise I would start booting from a 4.0 boot cd or ram key, check the files there, and compare with what is in your 'on disk' home directory.

   I just booted a 4.0 disk and adduser test did create a test user who can login.

   Hope this helps.

   Posted 11 years ago #
7. 

   michaelbischof
   

   offline

   Member

   @christophe
   I tried it from a new installation now and it works, with a new user as well.
   Thanks!

   Posted 11 years ago #

RSS feed for this topic

Reply

You must log in to post.