not resolved
Slizzard
offlineMember
For any other inexperienced Linux users who are reading this thread, the following page may be helpful to understand Filou's suggestion regarding Ctrl-Alt-F1. Especially useful is knowing how to get out of the virtual terminal once you are in it...
https://askubuntu.com/questions/157617/reverting-from-ctrl-alt-f1
Slizzard
Slizzard
offlineMember
Greetings Filou;
I tried your suggestions.
I could login to tty1 as root and killed slim.
I tried to log in to tty2 as 2 other different valid users, but same issue as with slim: would not accept valid users & passwords (they show up OK in TazPanel).
SO I could not write a login record from another user, but I did so from root back at tty1.
Started X as root. looked at file.
There were no EE errors flagged in the login.log, but there were some other errors...
(process:1721): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
error: Broken zip file structure
error: Broken zip file structure
** (lxpanel:1706): WARNING **: Battery 0 not found
error: Broken zip file structure
error: Broken zip file structure
** (lxpanel:1706): WARNING **: Battery 0 not found
Obt-Message: Failed to open an Input Method
** (lxpanel:1706): WARNING **: lxpanel : X error: BadWindow (invalid Window parameter)
** (lxpanel:1706): WARNING **: lxpanel : X error: BadWindow (invalid Window parameter)
(pcmanfm:1700): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(process:1784): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Are these irrelevant?
Slizzard
Slizzard
offlineMember
Greetings Ceel;
Thanks for your continuing attention.
MD5 in files named installed.md5, packages.md5, and tazpkg.log all match.
Here they are:
64efc014876ba3f4b55470dc50d85f03 busybox-pam-1.31.1.tazpkg
f87ec2e9ca01fa2af63f20759e1e9441 dropbear-pam-2022.83.tazpkg
20a221c891fabcba647ab4cf5630240c libcap-pam-2.63.tazpkg
6db691904871a8e5c7f3fa3d2067d13a partimage-pam-0.6.9.tazpkg
e1c9c42eb0e38c6df34de550bcb16b06 ppp-pam-2.4.7.tazpkg
9ca25168d210001379baed42f5c9b32d slim-pam-1.3.6.tazpkg
0605e35bb6f19436da91e0c49677a095 systemd-195.tazpkg
(edit) Oh, I forgot to say - All file permissions were checked and were correctly owned by root with change by owner only.
Slizzard
Slizzard
offlineMember
Greetings gibor;
I tried your suggestions...
From the CLI as root, I removed the tux home directory.
Then I ran bootopts.sh to recreate it, and closed the terminal.
I tried to log out of the desktop, but could not do so normally with the GUI options. The panel and the icons went away, but the desktop would not.
So I got out with Ctrl-Alt-Bkspc.
I typed "reboot" and it asked for a password - but refused to accept the root password.
So I rebooted with Ctrl-Alt-Del, and then tried to log in as tux. No joy. Still can only log in as root.
Does anyone have any more ideas I can try?
Slizzard
Slizzard
offlineMember
Greetings again Filou;
I glad you are persisting in this!
All expected users are present in /etc/passwd and /etc/shadow.
Users nobody, www, partimag, & mysql, are also present. I assume these are system requirements?
However, one test user that I had deleted a long time ago, which no longer has a home directory on disk, nor any presence in the Tazpanel users manager, is also present. What would happen if I deleted that line from the passwd and shadow files?
Here's the line in shadow:
Test+User::19372:0:99999:7:::
and in passwd:
Test+User:x:1002:100:testuser:/home/Test+User:/bin/sh
This invalid user listing comes just before the two users which can never log in (which includes tux). Is it possible that the invalid entry is aborting processing of the two lines that follow, so that the subsequent users do not exist as far as the system is concerned??
Slizzard
Ceel
offlineAdministrator
You didn't tell us you were using pam... Wouldn't be your login issue appears since you installed it?
Here is your update "problem":
busybox-pam: PROVIDE="busybox:pam"
dropbear-pam: PROVIDE="dropbear:pam ssh:pam"
libcap-pam: PROVIDE="libcap:pam"
partimage-pam: PROVIDE="partimage:pam"
ppp-pam: PROVIDE="ppp:pam"
slim-pam: PROVIDE="slim:pam"
systemd: PROVIDE="udev"
You should be able to solve it like this:
/mnt)busybox-pam, dropbear-pam, libcap-pam, partimage-pam, ppp-pam, slim-pam, pam and systemd:tazpkg -r <package_name> --root=/mntbusybox, dropbear, libcap, partimage, ppp, slim and udev in the same waysystemd, pam and the *-pam packages:tazpkg -gi <package_name> --root=/mntumount /mnt and reboot.Is your login issue still here? at least tazpkg up shouldn't ask to you to update the 7 packages.
Slizzard
offlineMember
Ceel;
Thanks for the revelation!
The only "pam" I know about is for spraying on frying pans so food doesn't stick.
Tazpkg.log says pam was first installed (or first upgraded) in june 2022 as part of an update of about 40 pkgs, so this was a tazpkg choice, not a user choice, Interestingly, pam did not cause any problems until the most recent blomf of 200+ updates - when it was upgraded to v.1.2.0. So this suggests that upgrade is what triggered the current pam issues.
Tazpanel's description of the pam package says its a "pluggable authentication module", which tells me nothing at all useful, and I can't find any useful information by searching the forum. I'm not a dev.
If pam is an optional & unnecessary program, why don't I just uninstall it using tazpanel? Won't tazpanel then remove all the dependent *-pam other files as well?
I'd like to remind you that this problem has occurred multiple times, and is always a pain in the ass to fix. This time I'd like to understand it, and hopefully find a way to fix it quickly and easily when it next occurs. Even better would be if the devs recognised it as their issue, and fixed it in the distro.
Slizzard
Ceel
offlineAdministrator
@ Slizzard,
Tazpkg will never install something you didn't ask for but pam and systemd could have been installed as depends of another package.
Did you install drbl or clonezilla? Can you post your tazpkg.log?
At the update that followed the pam installation, the *-pam packages are automatically installed for the equivallent "normal" packages that are installed. I've seen this behaviour with cups: epdfview was installed on my system; during the update that followed the cups installation, epdfview-cups has been installed.
So, check if pam is required by another package:
tazpkg rdepends pam
If not, you should be able to remove the packages in this order (with tazpanel or from a terminal): systemd, pam and then the *-pam.
Slizzard
offlineMember
Ceel;
Thanks for your continued interest.
You wrote...
Did you install drbl or clonezilla?
*** Both are installed. I only remember installing clonezilla. I think drbl is another tag-along.
Can you post your tazpkg.log?
*** Yes, it is included at the end of this post.
So, check if pam is required by another package:
tazpkg rdepends pam
*** output of that command below:
busybox-pam (712K)
dropbear-pam (356K)
libcap-pam (40K)
openssh-pam (5.6M)
partimage-pam (428K)
ppp-pam (748K)
slim-pam (356K)
systemd (6.4M)
drbl (7.1M)
clonezilla (3M)
*** PAM appears to be required by systemd, drbl, and clonezilla. I think I can do without drbl and clonezilla, but I thought systemd was an essential system file.
At the update that followed the pam installation, the *-pam packages are automatically installed for the equivalent "normal" packages that are installed. I've seen this behaviour with cups: epdfview was installed on my system; during the update that followed the cups installation, epdfview-cups has been installed.
** So if I understand correctly, by "normal" package you mean eg: dropbear instead of dropbear-pam.
*** tazpkg.log is attached. The April 2022 start date of the log is the day I re-installed Slitaz because of the previous occurrence of the login issue.
Slizzard
tazpkg.log (82.3 KB, 80 downloads) 1 year old
Ceel
offlineAdministrator
Hello Slizzard,
Your tazpkg.log short story (numbers are the line number in the log):
busybox (70), dropbear (88), libcap (73), ppp (264) and slim (208) are installed during Slitaz installation (1-322)clonezilla installation (484-532)Tazpkg installopenssh (502), partimage (505), libcap (515), pam (518), systemd (523), drbl (525), openssh-pam (527) because openssh is a dep of sshfs-fuse (528), but pam is now installed.zoneminder installation (536-571), Tazpkg installbusybox-pam (536) because busybox is a dep of mysql (539) but because of pam...libcap-pam (603+672), partimage-pam (605+761), dropbear-pam (615), ppp-pam (803), slim-pam (816) because there are new builds for libcap, partimage, dropbear, ppp, slim available on the mirror, but pam...Then each time you try to update your system, Tazpkg sees that busybox, dropbear, libcap, partimage, ppp and slim are not uptodate but can only install the corresponding -pam packages :(
So, I see 3 ways to solve this "issue":
clonezilla and all its dependences; this will be a little long...-pam packages (that the solution I suggested at Ravenslock and it seems working); remove systemd and udev and re-install systemdbusybox, dropbear, libcap, partimage, ppp, slim, systemd and udev; this must be done from a host as described in a previous post because you'll remove busybox-pam and busybox (by the way, I edited the post because I forgot to mention to remove pam); reinstall pam, systemd and the -pam.
*** PAM appears to be required by systemd, drbl, and clonezilla. I think I can do without drbl and clonezilla, but I thought systemd was an essential system file.
SliTaz comes without systemd by default; systemd was installed as a dependence during clonezilla installation.
** So if I understand correctly, by "normal" package you mean eg: dropbear instead of dropbear-pam.
Yes, I could also write " a non-pam package" ;-)
You must log in to post.
