tux login failed

michaelbischof · 2013-10-16 19:11:53

Hopefully it is not too boring for experienced users. I use Slitaz 4. I logged in as tux, but found the lower task panel missing. Then, out of a sudden, login as tux failed. Login as root works, though.

Any ideas what to do?

emgi · 2013-10-16 20:18:13

The missing panel question returns here regularly. Its a known issue. Please search the forum for something like "missing panel". You will find the resolution quickly.

When the login for tux does not work, I assume the password is lost?

Login as root and type:

# passwd tux

Enter the password you want to use and try again.

/emgi

Trixar_za · 2013-10-16 20:46:54

Kill Lxpanel and restart it with lxpanel --profile slitaz preferably from a virtual terminal (Ctrl+Alt+F1) and then exit it with Ctrl+Alt+F7

michaelbischof · 2013-10-17 06:42:37

Thanks to both of you for your remarkably quick answers!

No, apparently it was not a password problem. I confirmed the password for tux but no help. Then I added a new user and this worked. With a new user the panel problem does not occur again. But thanks,Trixar_za, to have remembered me that the issue is with lxpanel and not with openbox-session.

The only issue: sakura did not work. I removed it and tried to re-install it then. But it does not appear any longer in the package list. Was it removed later from Slitaz 4 stable?

totoetsasoeur · 2013-10-18 11:06:10

sakura is in slitaz4 stable:

http://pkgs.slitaz.org/search.sh?package=sakura&version=s

michaelbischof · 2013-10-18 12:49:23

@totoetsasoeur

Thanks! I did not find it, do not know why, but I could just reinstall it.

michaelbischof · 2013-10-18 18:57:20

Hmmh, strange: I reinstalled sakura and it worked. After a reboot I see the following behaviour:

I start it and a konsole opens but there is no „input“ like

user@slitaz:~$

- the Sakura konsole is just empty.

ls -ll /usr/bin/sakura

-rwxr-xr-x 1 root root 52052 Mar 13 2012 /usr/bin/sakura

The first time I encounter such a thing. A mysterium? ;-)

Unpleasant, but I have xterm.

lexeii · 2013-10-18 20:22:35

Michael,

Check the free space on your SliTaz partition. When accidently I can’t log in as tux, and can only as root, I check my free space and see that it gone, equal to zero. Maybe it is a result of great cached data in the browser, or big sources decompression, or so...

Next. Do you run Sakura directly? I mean: from Application menu item. OR as Favorite Terminal. Sometimes I encounter a problem with black Sakura screen, but this problem solved with help of Enter key pressing. Here something wrong with Favorite Terminal script, but this bug is strange and volatile.

If this not helps you, try run Sakura from your working xterm. Just open xterm, type [c]sakura[/c] and press Enter. New terminal window will be opened, and maybe you can see something strange/interest in your first window (in the xterm).

michaelbischof · 2013-10-18 21:05:06

@Aleksej

First: free spaced is no problem. It appears in both ways of starting it. Pressing enter does not help. Starting sakura from xterm gives the same result.

Thanks for your help - but I have not yet seen such a strange thing. If I create a new user sakura works normal. But you see, as cited above: the permissions are set correct.

lexeii · 2013-10-18 22:45:57

1. Any messages/errors in the xterm when you run sakura?

2. Next, interesting that you have no problem with new user. I think, something wrong with your tux user settings. Maybe, with /home/tux/.profile...

2a. Please, put here output of command:

[c]echo $PATH[/c]

2b. Please, check for yourself the difference between output of command:

[c]env[/c]

for your problematic tux user and for your problem-less new user.

mojo · 2013-10-19 03:03:00

Sakura displays no command prompt if user is not in tty group.

michaelbischof · 2013-10-19 07:05:21

Thanks to both of you! No, the problem was not PATH or env - the culprit is line 6 in /etc/groups:

„tty:x:5:tux“

There is no mention of „user“. How can I put the user „user“ into this tty-group?

As root: addgroup user tty

- I tried this and it works after logging out and login in as „user“ again.

Now line 6 reads like:

„tty:x:5:tux,user“

And, as I must admit, once again you hit the nail, @mojo. Astonishing! ;-)

lexeii · 2013-10-19 09:38:36

mojo,

my congratulations! You hit the bull-eye with single shot :-)

But I can’t understand Michael.

tux already was part in tty group, and sakura not work???

user named user not belongs to tty group and sakura worked for he???

and now Michael added user named user for tty group, for what?

Anyway, thank you, mojo. Now I’ll remember about groups, not only about depends and its paths.

michaelbischof · 2013-10-19 10:14:25

@Aleksej,

it is convention not to publish private user names here, as far as I know. So I substituted the real user name with „user“. I had a trouble with orignal tux. So I established by your recommendation the new user „user“. It worked then. But when I had reinstalled sakura I run into the mentioned problem. So I deleted old user „tux“ and created him anew. And this => new user „tux“ was in this tty-group, but „user“ was not. So I had to use „addgroup user tty“.

As an occassional user, not being a professional, I would never ever have discovered what to do with this issue. It is, as I repeat, a minor thing as my slitaz had xterm as well.

lexeii · 2013-10-19 10:29:12

Oh, thank you Michael.

Now I understand. I was confused a bit with user user, I think better to hide his real name in manner: my_user or so similar. Its not a problem.

And seems like xterm not checked tty group. Btw, now I use lilyterm as my everyday terminal emulator, and its based on the vte libs like sakura. And I really don’t like xterm, can’t understand why :-)

michaelbischof · 2013-10-31 11:17:47

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?

emgi · 2013-10-31 19:13:31

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

michaelbischof · 2013-10-31 22:06:46

@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! ;-)

emgi · 2013-10-31 22:21:29

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

michaelbischof · 2013-11-01 11:16:57

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'