Tumbleweed opensuse ver.16: cannot login after changed /home disc, LUKS problem?

My newly istalled OoenSuSE ver.16 tumbleweed cannot login into KDE, gnome, Plasma/ X11 or Wayland. This is simmilar to the situation in Sddm wont load desktop after migrate /home to a new ext4 partition . Error messages say the system cannot locate daemon control file (see sshd: gkr-pam: unable to locate daemonn control file) but I unistalled gkr-pam, error disappeared, but I still cannot log in. Somehow the system seems to cannot identify the proper home directory of a user in /home. I can log in into root, which in in /root i.e. on another partition.

In the current situation:

blkid | grep home

/dev/mapper/cr_home2: LABEL=“home” UUID=“2469a880-cb66-453c-acc6-f29f32e061af” BLOCK_SIZE=“4096” TYPE=“ext4”
/dev/nvme0n1p3: UUID=“1316a6c2-18c8-4201-80cb-fbd4e2238c3e” LABEL=“home” TYPE=“crypto_LUKS” PARTUUID=“38ff738f-dcf6-48a4-ac2a-79021540ec43”
/dev/mapper/cr-auto-1: LABEL=“home_old” UUID=“05d2231d-9773-410a-b1d0-d070815daa25” BLOCK_SIZE=“4096” TYPE=“ext4”

I do not undestand the third line with /dev/nvme0n1p3. What I see in partitioner shoud suffice:

/dev/mapper/cr-auto-1: LABEL=“home_old” /dev/nvme0n1p3 → /home_old
/dev/mapper/cr-home2: LABEL=“home” /dev/nvme1n1 → /home

This third line has also the wrong LABEL ! It should be “home_old”, not “home”. I did succed to log in after manipulating LABELS, but in /home_old, not into /home as it is written in /etc/passwd . This is weird.

I’d love to see what system calls have been made with strace, as is was suggested in the thrread above, but it is not agetty, which breaks down and I don’t know which process to observe.

Any ideas what to do now ?

There’s nothing I’m aware of about “16” in Tumbleweed, whose latest version is 20251106, while Leap’s latest version is 16.0. It makes me wonder what is is wrong besides in your description. Were you logged out of normal user and in as root to do this disk and label manipulation?

You should show us the entire /etc/fstab, and output from lsblk -f, as additional information.

When you paste command output, be sure to enclose between a pair of lines containing only ```, to preserve the formatting of the command output; and, include the command that produced the output on the first line after the first ```; and, also include the following command prompt, so we can assume we are seeing the entire command output, rather than some unknown size subset of it. The </> (pre) icon above the input window is there to facilitate doing so.

1 Like

Hi Mrmazda, thank U for the answere. I tried several days and I cannot say I found the solution, but the problem does not appear any more. I suggest this can be connected with the fact, that I uninstalled gnome-keyring and gnome-keyring-pam. Thank U for your attension. The case can be closed.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.