#41 Today 17:02:13

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 3,110

Re: (Wayland forky/sid) HowTo: deb packages for niri-wm + Noctalia shell

^Well, I would have loved to just delete everything after spending so many hours searching. What’s stopping me is that after the system suspends, the correct login window appears—with the password field and all the other expected system states.

When you search for “gkr-pam,” you keep coming across references to GNOME and its nonsense.
e.g.

A blinking cursor in the upper-left corner after a reboot indicates that the graphical session may not be starting. The provided context describes the setup but does not offer specific troubleshooting steps for this symptom.

    Check whether greetd is enabled and whether the configuration file at /etc/greetd/config.toml correctly points to tuigreet and /usr/share/wayland-sessions.
    Ensure that a Niri session file exists at /usr/share/wayland-sessions/niri.desktop and uses Exec=niri-session.
    Check whether Niri and its dependencies are installed and whether the session can be started with `niri-session`. The guide also recommends `xwayland-satellite` for X11 applications; however, it is not listed as a prerequisite for starting the session.

Information is missing regarding a specific cause of the blinking cursor and how to diagnose the issue using system logs or error messages.

or

This message indicates that PAM was unable to unlock the “login” keychain during login. This may be because the keychain password does not match the login password, or because the daemon did not start or was terminated prematurely. A successful system login does not prove that the keychain was unlocked.

In the Arch Linux case described, the cause was determined to be a signaling issue during daemon startup: `gnome-keyring-daemon` received a SIGHUP signal and was terminated. A patch that used `setsid()` to detach the daemon from the previous session and its TTY before starting it in the background resolved this specific issue. However, this is an older, system-specific investigation and not a confirmed solution for current GNOME versions.

First, check whether the keyring password matches the login password and whether the PAM configuration for the login method being used includes the pam_gnome_keyring.so module. According to the context, current GNOME versions may also have errors in PAM or an error in GNOME. Deleting and recreating the keyring does not help in every case; the context lacks sufficient information for a universal solution for current systems.

In my opinion, the permissions are set correctly:

~$ ./show_uid_gid.sh
Benutzer: unklar
uid=1000(unklar) gid=1000(unklar) Gruppen=1000(unklar),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),999(lpadmin),101(netdev)

Benutzer: _greetd
uid=977(_greetd) gid=977(_greetd) Gruppen=977(_greetd)

Troubleshooting in "Startup and display" say: ... ist mode 0750 (?)
@hhh, do you have any idea? 

Last edited by unklar (Today 17:15:07)

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 3,110

Re: (Wayland forky/sid) HowTo: deb packages for niri-wm + Noctalia shell

^I've tried everything – all to no avail!

sudo ls -l /var/lib/noctalia-greeter
[sudo] Passwort für unklar: 
insgesamt 3900
-rw-r--r-- 1 _greetd _greetd    1218  4. Okt 16:28 sync.toml
-rw-r--r-- 1 _greetd _greetd 1992511  4. Okt 16:28 wallpaper-HDMI-A-1.jpg
-rw-r--r-- 1 _greetd _greetd 1992511  4. Okt 16:28 wallpaper.jpg

sudo ls -l /etc/greetd/
insgesamt 8
-rw-r--r-- 1 root root 627  4. Okt 16:23 config.toml
-rw-r--r-- 1 root root 149  4. Okt 16:23 noctalia-greeter.toml

sudo apt install --reinstall --install-recommends greetd noctalia-greeter