Can't log in after last update (lightDM-issue?)

Faehnchen · December 27, 2022, 3:34pm

Hello dear MaBox community, I hope you had happy hollydays!
After the last update I did the night before christmas I couldn’t log in again after reboot. The computer would boot up normally until the lightdm-greeter. After entering the password the screen turns black for a second and switches back to the greeter. No MaBox on Christmas for me because I was at my relatives with the laptop I couldn’t use .
I had a similar issue few month ago but more on that at the end.

So I logged into a tty and looked what ‘journalctl’ had to say (I attach the whole journal for the session at the end) and everything looked fine except the reports of lightdm (filtered them out with grep). Here they are:

Dez 27 14:35:51 Rechenapparat-V lightdm[503]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=971) by (uid=0)
Dez 27 14:35:58 Rechenapparat-V lightdm[558]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: gkr-pam: unable to locate daemon control file
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: gkr-pam: stashed password to try later in open session
Dez 27 14:37:08 Rechenapparat-V lightdm[503]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: pam_unix(lightdm:session): session opened for user stefan2(uid=1001) by (uid=0)
Dez 27 14:37:09 Rechenapparat-V lightdm[558]: gkr-pam: unlocked login keyring
Dez 27 14:37:10 Rechenapparat-V lightdm[558]: pam_unix(lightdm:session): session closed for user stefan2
Dez 27 14:37:11 Rechenapparat-V lightdm[599]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=971) by (uid=0)
Dez 27 14:37:12 Rechenapparat-V lightdm[617]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.

Here is some system info:

OS: Mabox Linux x86_64
Host: 81AH Lenovo V320-17IKB
Kernel: 5.15.85-1-MANJARO
CPU: Intel Pentium 4415U (4) @ 2.3000GHZ
GPU: Intel HD Graphics 610

So it seems to be an issue with ‘gkr-pam’ and the keyring file or lightdm itself (?). How can I resolve this issue? Are there other logs/journals I could look into? The machine also has network running so updating packages would also be no problem.

Few month ago I had a similar issue. Lightdm reported error messages and openbox would perform a coredump imediatly after I tried to log in. I thought it would be a problem with openbox autostart but now I think it has something to do with the lightdm session. Because I couldn’t find a simple solution at the time I just created a new user and copied the contents of my old home folder into my new. That worked fine until now. But I would be glad if there was a cleaner solution.

PS:
I couldn’t put in the whole journal because of character limit so please tell me if I should provide messages of other modules as well.

napcok · December 27, 2022, 9:43pm

Hello @Faehnchen
Have you changed anything in the configuration file /etc/lightdm/lightdm.conf

Can you paste its contents? (only uncommented lines)

grep -v "^#" /etc/lightdm/lightdm.conf

Does anybody have a similar problem with LightDM?

bootz · December 27, 2022, 10:32pm

If I have the time I’ll update my main rig and see if this happens. This will not be very soon I think.
This issue, I’m sure it was last year or somewhat earlier, was also happening with an update. Can’t seem to find any related issue notices however so maybe this is just purely a local issue on @Faehnchen machine…

napcok · December 27, 2022, 10:43pm

I re-read the post carefully… there doesn’t seem to be any problem with LightDM.
Since it works for a newly created user - the same config file is used.
Maybe something was broken in the Openbox configuration files?
autostart or rc.xml from ~/.config/openbox?

Either way, none of these files are ever changed during an update – neither is /etc/lightdm/lightdm.conf

Faehnchen · December 28, 2022, 1:37am

Thank you for the reply!
I didn’t alter these configs ever. Also the last time I did changes to my openbox rc was some weeks ago and I use the same rc (minus the program starters) on the Lubuntu install I’m currently in.

Here is the extract from lightdm.conf:

[LightDM]
run-directory=/run/lightdm

[Seat:*]
session-wrapper=/etc/lightdm/Xsession

[XDMCPServer]

[VNCServer]

That’s the openbox autostart file (/etc/skel/.config/openbox/autostart):

## Mabox Autostart File
##
##
##
## Note that global autostart .desktop files will also be in
## /etc/xdg/openbox/autostart. These will include applications
## such as the Network Manager and Parcellite
##
## Turn on/off system beep.
xset b off

## Resolution
#xrandr --output VGA-1 --primary --mode 1600x900 --pos 0x0 --rotate normal
#xrandr --output VGA-1 --primary --mode 1920x1080 --pos 0x0 --rotate normal

## Copy Language files for Mabox - only for first run
/usr/bin/mabox-langfiles &

## Set keyboard settings - 250 ms delay and 25 cps (characters per second) repeat rate.
## Adjust the values according to your preferances.
#xset r rate 250 25

# Alias Super key to Super+Space for single-key menu.
# See 'man xcape' for other possibilities.
xcape -e 'Super_L=Super_L|space'


/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 &


## Panel
(sleep 1s && mb-tint2-session) &

## Background
(sleep 2s && nitrogen --restore) &

## Optionally enable file manager in daemon mode for automounting
(sleep 1s && pcmanfm -d) &

## Optionally disable touchpad
#/usr/bin/synclient TouchpadOff=1 &


## Mabox scripts - DO NOT DISABLE 
(sleep 1s && mabox-obstart startopenbox) &

Faehnchen · December 28, 2022, 2:51am

Additionally here are some reports from ‘systemctl status’ that might be relevant:

● lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
     Active: active (running) since Tue 2022-12-27 14:35:45 CET; 12h ago
       Docs: man:lightdm(1)
   Main PID: 447 (lightdm)
      Tasks: 7 (limit: 4420)
     Memory: 93.4M
        CPU: 3.385s
     CGroup: /system.slice/lightdm.service
             ├─447 /usr/bin/lightdm
             ├─593 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
             └─617 lightdm --session-child 12 20

Dez 27 14:35:45 Rechenapparat-V systemd[1]: Starting Light Display Manager...
Dez 27 14:35:45 Rechenapparat-V systemd[1]: Started Light Display Manager.
Dez 27 14:35:51 Rechenapparat-V lightdm[503]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=971) by (uid=0)
Dez 27 14:35:58 Rechenapparat-V lightdm[558]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: gkr-pam: unable to locate daemon control file
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: gkr-pam: stashed password to try later in open session
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: pam_unix(lightdm:session): session opened for user stefan2(uid=1001) by (uid=0)
Dez 27 14:37:11 Rechenapparat-V lightdm[599]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=971) by (uid=0)
Dez 27 14:37:12 Rechenapparat-V lightdm[617]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.

● polkit.service - Authorization Manager
     Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
     Active: active (running) since Tue 2022-12-27 14:35:46 CET; 12h ago
       Docs: man:polkit(8)
   Main PID: 467 (polkitd)
      Tasks: 3 (limit: 4420)
     Memory: 4.1M
        CPU: 353ms
     CGroup: /system.slice/polkit.service
             └─467 /usr/lib/polkit-1/polkitd --no-debug

Dez 27 14:35:46 Rechenapparat-V systemd[1]: Starting Authorization Manager...
Dez 27 14:35:46 Rechenapparat-V polkitd[467]: Started polkitd version 122
Dez 27 14:35:46 Rechenapparat-V polkitd[467]: Loading rules from directory /etc/polkit-1/rules.d
Dez 27 14:35:46 Rechenapparat-V polkitd[467]: Loading rules from directory /usr/share/polkit-1/rules.d
Dez 27 14:35:46 Rechenapparat-V polkitd[467]: Finished loading, compiling and executing 5 rules
Dez 27 14:35:46 Rechenapparat-V systemd[1]: Started Authorization Manager.
Dez 27 14:35:46 Rechenapparat-V polkitd[467]: Acquired the name org.freedesktop.PolicyKit1 on the system bus

That’s interesting because after login it seems like it loged me out again imediatly:

● systemd-logind.service - User Login Management
     Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
     Active: active (running) since Tue 2022-12-27 14:35:43 CET; 12h ago
       Docs: man:sd-login(3)
             man:systemd-logind.service(8)
             man:logind.conf(5)
             man:org.freedesktop.login1(5)
   Main PID: 409 (systemd-logind)
     Status: "Processing requests..."
      Tasks: 1 (limit: 4420)
     Memory: 2.2M
        CPU: 351ms
     CGroup: /system.slice/systemd-logind.service
             └─409 /usr/lib/systemd/systemd-logind

Dez 27 14:35:43 Rechenapparat-V systemd-logind[409]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard)
Dez 27 14:35:43 Rechenapparat-V systemd[1]: Started User Login Management.
Dez 27 14:35:51 Rechenapparat-V systemd-logind[409]: New session c1 of user lightdm.
Dez 27 14:37:08 Rechenapparat-V systemd-logind[409]: Removed session c1.
Dez 27 14:37:08 Rechenapparat-V systemd-logind[409]: New session 2 of user stefan2.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Session 2 logged out. Waiting for processes to exit.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Removed session 2.
Dez 27 14:37:11 Rechenapparat-V systemd-logind[409]: New session c2 of user lightdm.
Dez 27 14:38:23 Rechenapparat-V systemd-logind[409]: New session 4 of user stefan2.
Dez 27 14:48:55 Rechenapparat-V systemd-logind[409]: New session 6 of user stefan2.

● systemd-logind.service - User Login Management
     Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
     Active: active (running) since Tue 2022-12-27 14:35:43 CET; 12h ago
       Docs: man:sd-login(3)
             man:systemd-logind.service(8)
             man:logind.conf(5)
             man:org.freedesktop.login1(5)
   Main PID: 409 (systemd-logind)
     Status: "Processing requests..."
      Tasks: 1 (limit: 4420)
     Memory: 2.2M
        CPU: 351ms
     CGroup: /system.slice/systemd-logind.service
             └─409 /usr/lib/systemd/systemd-logind

Dez 27 14:35:43 Rechenapparat-V systemd-logind[409]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard)
Dez 27 14:35:43 Rechenapparat-V systemd[1]: Started User Login Management.
Dez 27 14:35:51 Rechenapparat-V systemd-logind[409]: New session c1 of user lightdm.
Dez 27 14:37:08 Rechenapparat-V systemd-logind[409]: Removed session c1.
Dez 27 14:37:08 Rechenapparat-V systemd-logind[409]: New session 2 of user stefan2.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Session 2 logged out. Waiting for processes to exit.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Removed session 2.
Dez 27 14:37:11 Rechenapparat-V systemd-logind[409]: New session c2 of user lightdm.
Dez 27 14:38:23 Rechenapparat-V systemd-logind[409]: New session 4 of user stefan2.
Dez 27 14:48:55 Rechenapparat-V systemd-logind[409]: New session 6 of user stefan2.

● user@1001.service - User Manager for UID 1001
     Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
    Drop-In: /usr/lib/systemd/system/user@.service.d
             └─10-login-barrier.conf
     Active: active (running) since Tue 2022-12-27 14:38:23 CET; 12h ago
       Docs: man:user@.service(5)
   Main PID: 625 (systemd)
     Status: "Ready."
      Tasks: 2
     Memory: 2.8M
        CPU: 383ms
     CGroup: /user.slice/user-1001.slice/user@1001.service
             └─init.scope
               ├─625 /usr/lib/systemd/systemd --user
               └─626 "(sd-pam)"

Dez 27 14:38:23 Rechenapparat-V systemd[625]: Listening on PipeWire Multimedia System Socket.
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Listening on Sound System.
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Listening on D-Bus User Message Bus Socket.
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Reached target Sockets.
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Reached target Basic System.
Dez 27 14:38:23 Rechenapparat-V systemd[1]: Started User Manager for UID 1001.
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Starting Update XDG user dir configuration...
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Finished Update XDG user dir configuration.
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Reached target Main User Target.
Dez 27 14:38:23 Rechenapparat-V systemd[625]: Startup finished in 173ms.

Faehnchen · December 28, 2022, 3:20am

Through some online research I found out that most of the ‘pam’ warnings seem to be noise because systemd may check conditions befor the services that provide them started. At least I couldn’t find a case regarding these warnings that were related to my problem. A few lines I found curious like this one after:

Dez 27 14:37:08 Rechenapparat-V systemd[1]: Starting User Manager for UID 1001...
Dez 27 14:37:08 Rechenapparat-V dbus-daemon[407]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.24' (uid=0 pid=569 comm="(systemd)")
Dez 27 14:37:08 Rechenapparat-V dbus-daemon[407]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:08 Rechenapparat-V audit[569]: USER_ACCT pid=569 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="stefan2" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:08 Rechenapparat-V audit[569]: CRED_ACQ pid=569 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stefan2" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1101 audit(1672148228.521:74): pid=569 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="stefan2" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

audit[569]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffd29eea590 a2=40 a3=1 items=0 ppid=1 pid=569 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=3 comm=“systemd” exe=“/usr/lib/systemd/systemd” key=(null)

Is the key-variable empty or is it normal?

Here is the whole journalctl log from startup of graphical interface until I logged in on tty4. I’m too tired so I try to research more online tomorrow. As said so far I found nothing related to my problem.

Dez 27 14:35:57 Rechenapparat-V systemd[1]: Startup finished in 4.196s (firmware) + 8.991s (loader) + 7.010s (kernel) + 42.805s (userspace) = 1min 3.003s.
Dez 27 14:35:57 Rechenapparat-V dbus-daemon[407]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.18' (uid=0 pid=549 comm="/usr/bin/smbd --foreground --no-process-group")
Dez 27 14:35:57 Rechenapparat-V kernel: audit: type=1130 audit(1672148157.840:62): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=smb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:35:57 Rechenapparat-V dbus-daemon[407]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Dez 27 14:35:58 Rechenapparat-V at-spi-bus-launcher[528]: dbus-daemon[528]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=971 pid=515 comm="/usr/bin/lightdm-gtk-greeter")
Dez 27 14:35:58 Rechenapparat-V at-spi-bus-launcher[528]: dbus-daemon[528]: Successfully activated service 'org.a11y.atspi.Registry'
Dez 27 14:35:58 Rechenapparat-V at-spi-bus-launcher[560]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dez 27 14:35:58 Rechenapparat-V dbus-daemon[407]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.20' (uid=0 pid=558 comm="lightdm --session-child 13 20")
Dez 27 14:35:58 Rechenapparat-V dbus-daemon[407]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:35:58 Rechenapparat-V lightdm[558]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:36:14 Rechenapparat-V systemd-timesyncd[403]: Contacted time server [2003:a:87f:c37c::3]:123 (2.manjaro.pool.ntp.org).
Dez 27 14:36:14 Rechenapparat-V systemd-timesyncd[403]: Initial clock synchronization to Tue 2022-12-27 14:36:14.021501 CET.
Dez 27 14:36:16 Rechenapparat-V systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Dez 27 14:36:16 Rechenapparat-V audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:36:16 Rechenapparat-V kernel: audit: type=1131 audit(1672148176.011:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:36:16 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:36:16 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:36:16 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:36:16 Rechenapparat-V kernel: audit: type=1334 audit(1672148176.114:64): prog-id=0 op=UNLOAD
Dez 27 14:36:16 Rechenapparat-V kernel: audit: type=1334 audit(1672148176.114:65): prog-id=0 op=UNLOAD
Dez 27 14:36:16 Rechenapparat-V kernel: audit: type=1334 audit(1672148176.114:66): prog-id=0 op=UNLOAD
Dez 27 14:36:20 Rechenapparat-V nmbd[532]: [2022/12/27 14:36:20.584214,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Dez 27 14:36:20 Rechenapparat-V nmbd[532]:   *****
Dez 27 14:36:20 Rechenapparat-V nmbd[532]:
Dez 27 14:36:20 Rechenapparat-V nmbd[532]:   Samba name server RECHENAPPARAT-V is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.154
Dez 27 14:36:20 Rechenapparat-V nmbd[532]:
Dez 27 14:36:20 Rechenapparat-V nmbd[532]:   *****
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: gkr-pam: unable to locate daemon control file
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1100 audit(1672148228.028:67): pid=558 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1101 audit(1672148228.028:68): pid=558 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V audit[558]: USER_AUTH pid=558 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V audit[558]: USER_ACCT pid=558 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: gkr-pam: stashed password to try later in open session
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Stopping Session c1 of User lightdm...
Dez 27 14:37:08 Rechenapparat-V lightdm[503]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dez 27 14:37:08 Rechenapparat-V audit[503]: USER_END pid=503 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V audit[503]: CRED_DISP pid=503 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1106 audit(1672148228.445:69): pid=503 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1104 audit(1672148228.445:70): pid=503 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V systemd[1]: session-c1.scope: Deactivated successfully.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Stopped Session c1 of User lightdm.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: session-c1.scope: Consumed 1.246s CPU time.
Dez 27 14:37:08 Rechenapparat-V systemd-logind[409]: Removed session c1.
Dez 27 14:37:08 Rechenapparat-V audit[558]: CRED_ACQ pid=558 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V audit[558]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7fff0830a520 a2=4 a3=7fff0830a234 items=0 ppid=447 pid=558 auid=1001 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="lightdm" exe="/usr/bin/lightdm" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle=6C69676874646D002D2D73657373696F6E2D6368696C64003133003230
Dez 27 14:37:08 Rechenapparat-V lightdm[558]: pam_unix(lightdm:session): session opened for user stefan2(uid=1001) by (uid=0)
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1103 audit(1672148228.478:71): pid=558 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1006 audit(1672148228.478:72): pid=558 uid=0 old-auid=4294967295 auid=1001 tty=(none) old-ses=4294967295 ses=2 res=1
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1300 audit(1672148228.478:72): arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7fff0830a520 a2=4 a3=7fff0830a234 items=0 ppid=447 pid=558 auid=1001 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="lightdm" exe="/usr/bin/lightdm" key=(null)
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1327 audit(1672148228.478:72): proctitle=6C69676874646D002D2D73657373696F6E2D6368696C64003133003230
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Created slice User Slice of UID 1001.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Starting User Runtime Directory /run/user/1001...
Dez 27 14:37:08 Rechenapparat-V systemd-logind[409]: New session 2 of user stefan2.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Finished User Runtime Directory /run/user/1001.
Dez 27 14:37:08 Rechenapparat-V audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1130 audit(1672148228.515:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Starting User Manager for UID 1001...
Dez 27 14:37:08 Rechenapparat-V dbus-daemon[407]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.24' (uid=0 pid=569 comm="(systemd)")
Dez 27 14:37:08 Rechenapparat-V dbus-daemon[407]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:08 Rechenapparat-V audit[569]: USER_ACCT pid=569 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="stefan2" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:08 Rechenapparat-V audit[569]: CRED_ACQ pid=569 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stefan2" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Dez 27 14:37:08 Rechenapparat-V kernel: audit: type=1101 audit(1672148228.521:74): pid=569 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="stefan2" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:08 Rechenapparat-V audit[569]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7fff7c62dfd0 a2=4 a3=7fff7c62dce4 items=0 ppid=1 pid=569 auid=1001 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=3 comm="(systemd)" exe="/usr/lib/systemd/systemd" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle="(systemd)"
Dez 27 14:37:08 Rechenapparat-V systemd[569]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[stefan2] ruser=[<unknown>] rhost=[<unknown>]
Dez 27 14:37:08 Rechenapparat-V systemd[569]: pam_unix(systemd-user:session): session opened for user stefan2(uid=1001) by (uid=0)
Dez 27 14:37:08 Rechenapparat-V audit[569]: USER_START pid=569 uid=0 auid=1001 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stefan2" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=36 op=LOAD
Dez 27 14:37:08 Rechenapparat-V audit[569]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffd29eea900 a2=90 a3=0 items=0 ppid=1 pid=569 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=3 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle="(systemd)"
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=37 op=LOAD
Dez 27 14:37:08 Rechenapparat-V audit[569]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffd29ee9770 a2=74 a3=2 items=0 ppid=1 pid=569 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=3 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle="(systemd)"
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=38 op=LOAD
Dez 27 14:37:08 Rechenapparat-V audit[569]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffd29ee98c0 a2=80 a3=0 items=0 ppid=1 pid=569 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=3 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle="(systemd)"
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=39 op=LOAD
Dez 27 14:37:08 Rechenapparat-V audit[569]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffd29eea6d0 a2=80 a3=2 items=0 ppid=1 pid=569 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=3 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle="(systemd)"
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=40 op=LOAD
Dez 27 14:37:08 Rechenapparat-V audit[569]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffd29eea590 a2=40 a3=1 items=0 ppid=1 pid=569 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=3 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle="(systemd)"
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=41 op=LOAD
Dez 27 14:37:08 Rechenapparat-V audit[569]: SYSCALL arch=c000003e syscall=321 success=yes exit=10 a0=5 a1=7ffd29eea450 a2=80 a3=5 items=0 ppid=1 pid=569 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=3 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)
Dez 27 14:37:08 Rechenapparat-V audit: PROCTITLE proctitle="(systemd)"
Dez 27 14:37:08 Rechenapparat-V audit: BPF prog-id=0 op=UNLOAD
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Queued start job for default target Main User Target.
Dez 27 14:37:08 Rechenapparat-V audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Created slice User Application Slice.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Reached target Paths.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Reached target Timers.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Starting D-Bus User Message Bus Socket...
Dez 27 14:37:09 Rechenapparat-V gnome-keyring-daemon[578]: GNOME_KEYRING_CONTROL=/run/user/1001/keyring
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on GnuPG network certificate management daemon.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on GCR ssh-agent wrapper.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on GNOME Keyring daemon.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on GnuPG cryptographic agent and passphrase cache.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on p11-kit server.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on PipeWire Multimedia System Socket.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on Sound System.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Listening on D-Bus User Message Bus Socket.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Reached target Sockets.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Reached target Basic System.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Started User Manager for UID 1001.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Started Session 2 of User stefan2.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Starting Update XDG user dir configuration...
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Started GNOME Keyring daemon.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Finished Update XDG user dir configuration.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Reached target Main User Target.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Startup finished in 336ms.
Dez 27 14:37:09 Rechenapparat-V systemd[569]: Created slice User Core Session Slice.
Dez 27 14:37:09 Rechenapparat-V systemd[569]: Starting D-Bus User Message Bus...
Dez 27 14:37:09 Rechenapparat-V systemd[569]: Started D-Bus User Message Bus.
Dez 27 14:37:09 Rechenapparat-V lightdm[558]: gkr-pam: unlocked login keyring
Dez 27 14:37:09 Rechenapparat-V audit[558]: USER_START pid=558 uid=0 auid=1001 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:09 Rechenapparat-V audit[558]: USER_LOGIN pid=558 uid=0 auid=1001 ses=2 msg='op=login id=1001 exe="/usr/bin/lightdm" hostname=Rechenapparat-V addr=? terminal=/dev/tty7 res=success'
Dez 27 14:37:10 Rechenapparat-V audit[558]: USER_LOGOUT pid=558 uid=0 auid=1001 ses=2 msg='op=logout id=1001 exe="/usr/bin/lightdm" hostname=Rechenapparat-V addr=? terminal=/dev/tty7 res=success'
Dez 27 14:37:10 Rechenapparat-V lightdm[558]: pam_unix(lightdm:session): session closed for user stefan2
Dez 27 14:37:10 Rechenapparat-V audit[558]: USER_END pid=558 uid=0 auid=1001 ses=2 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:10 Rechenapparat-V audit[558]: CRED_DISP pid=558 uid=0 auid=1001 ses=2 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:10 Rechenapparat-V systemd[1]: session-2.scope: Deactivated successfully.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Session 2 logged out. Waiting for processes to exit.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Removed session 2.
Dez 27 14:37:11 Rechenapparat-V audit[599]: CRED_ACQ pid=599 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:11 Rechenapparat-V lightdm[599]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=971) by (uid=0)
Dez 27 14:37:11 Rechenapparat-V systemd-logind[409]: New session c2 of user lightdm.
Dez 27 14:37:11 Rechenapparat-V systemd[1]: Started Session c2 of User lightdm.
Dez 27 14:37:11 Rechenapparat-V audit[599]: USER_START pid=599 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:12 Rechenapparat-V dbus-daemon[407]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.32' (uid=0 pid=617 comm="lightdm --session-child 12 20")
Dez 27 14:37:12 Rechenapparat-V dbus-daemon[407]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:12 Rechenapparat-V lightdm[617]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopping User Manager for UID 1001...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Activating special unit Exit the Session...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Main User Target.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopping D-Bus User Message Bus...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopping GNOME Keyring daemon...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped GNOME Keyring daemon.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped D-Bus User Message Bus.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Removed slice User Core Session Slice.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Basic System.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Paths.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Sockets.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Timers.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed D-Bus User Message Bus Socket.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG network certificate management daemon.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GCR ssh-agent wrapper.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GNOME Keyring daemon.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Dez 27 14:37:20 Rechenapparat-V kernel: kauditd_printk_skb: 37 callbacks suppressed
Dez 27 14:37:20 Rechenapparat-V kernel: audit: type=1131 audit(1672148240.875:98): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V kernel: audit: type=1131 audit(1672148240.918:99): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V systemd[570]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[stefan2] ruser=[<unknown>] rhost=[<unknown>]
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent and passphrase cache.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed p11-kit server.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed PipeWire Multimedia System Socket.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed Sound System.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Removed slice User Application Slice.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Reached target Shutdown.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Finished Exit the Session.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Reached target Exit the Session.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: user@1001.service: Deactivated successfully.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopped User Manager for UID 1001.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopping User Runtime Directory /run/user/1001...
Dez 27 14:37:20 Rechenapparat-V systemd[1]: run-user-1001.mount: Deactivated successfully.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: user-runtime-dir@1001.service: Deactivated successfully.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopped User Runtime Directory /run/user/1001.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Removed slice User Slice of UID 1001.
Dez 27 14:38:06 Rechenapparat-V systemd[1]: Started Getty on tty4.
Dez 27 14:38:06 Rechenapparat-V audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty4 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Faehnchen · December 28, 2022, 3:55am

I found the lightdm log (/var/log/lightdm/lightdm.log):

[+0.04s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.04s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=447
[+0.04s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.04s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.04s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.04s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.04s] DEBUG: Registered seat module local
[+0.04s] DEBUG: Registered seat module xremote
[+0.04s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.04s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.04s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.05s] DEBUG: Monitoring logind for seats
[+0.05s] DEBUG: New seat added from logind: seat0
[+0.05s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.05s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.05s] DEBUG: Seat seat0: Starting
[+0.05s] DEBUG: Seat seat0: Creating greeter session
[+0.07s] DEBUG: Seat seat0: Creating display server of type x
[+0.07s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.07s] DEBUG: Using VT 7
[+0.07s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.07s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.10s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.10s] DEBUG: XServer 0: Launching X Server
[+0.10s] DEBUG: Launching process 458: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.10s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.10s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.10s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+1.00s] DEBUG: Loading users from org.freedesktop.Accounts
[+1.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+1.60s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+5.73s] DEBUG: Got signal 10 from process 458
[+5.73s] DEBUG: XServer 0: Got signal from X server :0
[+5.73s] DEBUG: XServer 0: Connecting to XServer :0
[+5.92s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+5.92s] DEBUG: Session pid=503: Started with service 'lightdm-greeter', username 'lightdm'
[+6.06s] DEBUG: Session pid=503: Authentication complete with return value 0: Success
[+6.06s] DEBUG: Seat seat0: Session authenticated, running command
[+6.06s] DEBUG: Session pid=503: Running command /usr/bin/lightdm-gtk-greeter
[+6.06s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+6.06s] DEBUG: Session pid=503: Logging to /var/log/lightdm/seat0-greeter.log
[+6.89s] DEBUG: Activating VT 7
[+6.89s] DEBUG: Activating login1 session c1
[+6.89s] DEBUG: Seat seat0 changes active session to c1
[+6.89s] DEBUG: Session c1 is already active
[+10.11s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+12.46s] DEBUG: Greeter start authentication for stefan2
[+12.46s] DEBUG: Session pid=558: Started with service 'lightdm', username 'stefan2'
[+12.55s] DEBUG: Session pid=558: Got 1 message(s) from PAM
[+12.55s] DEBUG: Prompt greeter with 1 message(s)
[+81.85s] DEBUG: Continue authentication
[+81.87s] DEBUG: Session pid=558: Authentication complete with return value 0: Success
[+81.87s] DEBUG: Authenticate result for user stefan2: Success
[+81.87s] DEBUG: User stefan2 authorized
[+81.94s] DEBUG: Greeter requests session openbox
[+81.95s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+81.95s] DEBUG: Terminating login1 session c1
[+81.95s] DEBUG: Session pid=503: Sending SIGTERM
[+82.28s] DEBUG: Greeter closed communication channel
[+82.28s] DEBUG: Session pid=503: Exited with return value 0
[+82.28s] DEBUG: Seat seat0: Session stopped
[+82.28s] DEBUG: Seat seat0: Greeter stopped, running session
[+82.28s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+82.29s] DEBUG: Session pid=558: Running command /etc/lightdm/Xsession /usr/bin/openbox-session
[+82.29s] DEBUG: Creating shared data directory /var/lib/lightdm-data/stefan2
[+82.30s] DEBUG: Session pid=558: Logging to .xsession-errors
[+83.07s] DEBUG: Activating VT 7
[+83.07s] DEBUG: Activating login1 session 2
[+83.07s] DEBUG: Seat seat0 changes active session to 
[+83.07s] DEBUG: Seat seat0 changes active session to 2
[+83.07s] DEBUG: Session 2 is already active
[+84.42s] DEBUG: Session pid=558: Exited with return value 127
[+84.42s] DEBUG: Seat seat0: Session stopped
[+84.42s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+84.42s] DEBUG: Sending signal 15 to process 458
[+84.43s] DEBUG: Seat seat0 changes active session to 
[+84.78s] DEBUG: Process 458 exited with return value 0
[+84.78s] DEBUG: XServer 0: X server stopped
[+84.78s] DEBUG: Releasing VT 7
[+84.78s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+84.78s] DEBUG: Seat seat0: Display server stopped
[+84.78s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+84.78s] DEBUG: Seat seat0: Creating greeter session
[+84.78s] DEBUG: Seat seat0: Creating display server of type x
[+84.78s] DEBUG: Using VT 7
[+84.78s] DEBUG: Seat seat0: Starting local X display on VT 7
[+84.78s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+84.78s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+84.78s] DEBUG: XServer 0: Launching X Server
[+84.79s] DEBUG: Launching process 593: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+84.79s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+85.40s] DEBUG: Got signal 10 from process 593
[+85.40s] DEBUG: XServer 0: Got signal from X server :0
[+85.40s] DEBUG: XServer 0: Connecting to XServer :0
[+85.40s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+85.40s] DEBUG: Session pid=599: Started with service 'lightdm-greeter', username 'lightdm'
[+85.43s] DEBUG: Session pid=599: Authentication complete with return value 0: Success
[+85.43s] DEBUG: Seat seat0: Session authenticated, running command
[+85.43s] DEBUG: Session pid=599: Running command /usr/bin/lightdm-gtk-greeter
[+85.43s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+85.43s] DEBUG: Session pid=599: Logging to /var/log/lightdm/seat0-greeter.log
[+85.45s] DEBUG: Activating VT 7
[+85.45s] DEBUG: Activating login1 session c2
[+85.45s] DEBUG: Seat seat0 changes active session to c2
[+85.45s] DEBUG: Session c2 is already active
[+85.65s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+85.95s] DEBUG: Greeter start authentication for stefan2
[+85.96s] DEBUG: Session pid=617: Started with service 'lightdm', username 'stefan2'
[+85.97s] DEBUG: Session pid=617: Got 1 message(s) from PAM
[+85.97s] DEBUG: Prompt greeter with 1 message(s)
[+140.59s] DEBUG: Seat seat0 changes active session to 
[+157.38s] DEBUG: Seat seat0 changes active session to 4
[+776.93s] DEBUG: Seat seat0 changes active session to 
[+789.28s] DEBUG: Seat seat0 changes active session to 6
[+1479.11s] DEBUG: Seat seat0 changes active session to 4
[+1786.42s] DEBUG: Seat seat0 changes active session to 6
[+3530.36s] DEBUG: Seat seat0 changes active session to 4
[+3626.73s] DEBUG: Seat seat0 changes active session to 6

Faehnchen · December 28, 2022, 3:02pm

So far I did what I found on the internet related to lightdm-loops

Checking the configs for missing lines → everything is fine
Deleting ~/.Xauthority → no change in behaviour

Although it is notable that the .Xauthority I deleted was empty and so was the new one when I restarted the system. So I had the Idea to check ~/.xsession-errors. It only says following:

/etc/lightdm/Xsession: Zeile 64: exec: PATH: Nicht gefunden.

That means that the wrapper skript ‘Xsession’ located in /etc/lightdm that sources everything to create a new session couldn’t receive a path, see:

 ·
 ·
 ·
echo "X session wrapper complete, running session $@"

exec $@

So lightdm worked just fine and did it’s thing. Te error must lie somewhere else…

I guessed this has something to do with the module ‘user@.service’ (see systemctl status above). That’s also what

man user@.service

indicates.

Looking for the event in journalctl it pointed me right to the end before I successfully logged in to tty4 (so it also can’t be a problem with the keyring)

Dez 27 14:37:08 Rechenapparat-V systemd[569]: Reached target Basic System.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Started User Manager for UID 1001.
Dez 27 14:37:08 Rechenapparat-V systemd[1]: Started Session 2 of User stefan2.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Starting Update XDG user dir configuration...
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Started GNOME Keyring daemon.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Finished Update XDG user dir configuration.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Reached target Main User Target.
Dez 27 14:37:08 Rechenapparat-V systemd[569]: Startup finished in 336ms.
Dez 27 14:37:09 Rechenapparat-V systemd[569]: Created slice User Core Session Slice.
Dez 27 14:37:09 Rechenapparat-V systemd[569]: Starting D-Bus User Message Bus...
Dez 27 14:37:09 Rechenapparat-V systemd[569]: Started D-Bus User Message Bus.
Dez 27 14:37:09 Rechenapparat-V lightdm[558]: gkr-pam: unlocked login keyring
Dez 27 14:37:09 Rechenapparat-V audit[558]: USER_START pid=558 uid=0 auid=1001 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:09 Rechenapparat-V audit[558]: USER_LOGIN pid=558 uid=0 auid=1001 ses=2 msg='op=login id=1001 exe="/usr/bin/lightdm" hostname=Rechenapparat-V addr=? terminal=/dev/tty7 res=success'
Dez 27 14:37:10 Rechenapparat-V audit[558]: USER_LOGOUT pid=558 uid=0 auid=1001 ses=2 msg='op=logout id=1001 exe="/usr/bin/lightdm" hostname=Rechenapparat-V addr=? terminal=/dev/tty7 res=success'
Dez 27 14:37:10 Rechenapparat-V lightdm[558]: pam_unix(lightdm:session): session closed for user stefan2
Dez 27 14:37:10 Rechenapparat-V audit[558]: USER_END pid=558 uid=0 auid=1001 ses=2 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:10 Rechenapparat-V audit[558]: CRED_DISP pid=558 uid=0 auid=1001 ses=2 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="stefan2" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:10 Rechenapparat-V systemd[1]: session-2.scope: Deactivated successfully.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Session 2 logged out. Waiting for processes to exit.
Dez 27 14:37:10 Rechenapparat-V systemd-logind[409]: Removed session 2.
Dez 27 14:37:11 Rechenapparat-V audit[599]: CRED_ACQ pid=599 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:11 Rechenapparat-V lightdm[599]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=971) by (uid=0)
Dez 27 14:37:11 Rechenapparat-V systemd-logind[409]: New session c2 of user lightdm.
Dez 27 14:37:11 Rechenapparat-V systemd[1]: Started Session c2 of User lightdm.
Dez 27 14:37:11 Rechenapparat-V audit[599]: USER_START pid=599 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success'
Dez 27 14:37:12 Rechenapparat-V dbus-daemon[407]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.32' (uid=0 pid=617 comm="lightdm --session-child 12 20")
Dez 27 14:37:12 Rechenapparat-V dbus-daemon[407]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:12 Rechenapparat-V lightdm[617]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopping User Manager for UID 1001...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Activating special unit Exit the Session...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Main User Target.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopping D-Bus User Message Bus...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopping GNOME Keyring daemon...
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped GNOME Keyring daemon.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped D-Bus User Message Bus.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Removed slice User Core Session Slice.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Basic System.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Paths.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Sockets.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Stopped target Timers.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed D-Bus User Message Bus Socket.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG network certificate management daemon.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GCR ssh-agent wrapper.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GNOME Keyring daemon.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Dez 27 14:37:20 Rechenapparat-V kernel: kauditd_printk_skb: 37 callbacks suppressed
Dez 27 14:37:20 Rechenapparat-V kernel: audit: type=1131 audit(1672148240.875:98): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V kernel: audit: type=1131 audit(1672148240.918:99): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 27 14:37:20 Rechenapparat-V systemd[570]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[stefan2] ruser=[<unknown>] rhost=[<unknown>]
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed GnuPG cryptographic agent and passphrase cache.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed p11-kit server.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed PipeWire Multimedia System Socket.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Closed Sound System.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Removed slice User Application Slice.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Reached target Shutdown.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Finished Exit the Session.
Dez 27 14:37:20 Rechenapparat-V systemd[569]: Reached target Exit the Session.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: user@1001.service: Deactivated successfully.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopped User Manager for UID 1001.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopping User Runtime Directory /run/user/1001...
Dez 27 14:37:20 Rechenapparat-V systemd[1]: run-user-1001.mount: Deactivated successfully.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: user-runtime-dir@1001.service: Deactivated successfully.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Stopped User Runtime Directory /run/user/1001.
Dez 27 14:37:20 Rechenapparat-V systemd[1]: Removed slice User Slice of UID 1001.
Dez 27 14:38:06 Rechenapparat-V systemd[1]: Started Getty on tty4.

Everything cries “success” until

lightdm[558]: pam_unix(lightdm:session): session closed for user stefan2

comes around and seems to shut down everything. It’s hilarious: no error messages why this could be the case whatsoever! I’m pretty lost from here on. I would appreciate help very much. I work in a bike shop and have no clue about OS-init systems and much of the stuff I find about systemd in the web is criticizing it for this and that but not helping me really.

I wished there was a clean solution other to make just a new user, because I found many forum entries of people having the same problem with lightdm/sddm/gdm after updates/version-upgrades on several other Distros (even on Ubuntu). So for a new user that could be a deal-breaker to further try MaBox or any other user friendly distro and they will probably go back where they came from.

napcok · December 28, 2022, 3:14pm

So far you are the only user reporting this type of issue.
I have never encountered such a problem, even though I have been using Mabox on several computers for many years. And many virtual machines.
No one has ever reported such a problem.

Maybe it’s a problem related to a very specific hardware…
I can’t fix a problem that cannot be reproduced in any way.

Faehnchen · December 28, 2022, 3:38pm

That’s fair. However I seem to be not the only one having this problem ever. If you google “lightdm/sddm/gdm login loop” you’ll find hundreds of forum posts. Also there are plenty of Youtube tutorials with workarounds.

Notable to read:

And even lightdm in Arch wiki has an entry on it:
https://wiki.archlinux.org/title/LightDM#Infinite_login_loop

So far none of the presented solutions worked or gave me a clue of the core problem only that it doesn’t lie in the DE or the session manager. Wiping my disk or creating a new user might solve it for me (until the next major update).

I didn’t mean to waste your time and I appreciate your efforts in every regard. But since that happened to me the second time in a year and apparently in a similar fashion to many other people as well I thought that may be an issue worth to be addressed.

Anyway, you don’t loose me as a Mabox user all too soon .

Have a nice evening!

bootz · December 29, 2022, 11:12am

Indeed there were or maybe are multiple login loops recorded for lightdm. I also encountered it after an upgrade and wasn’t able to sort it out.

Instead of an upgrade on my main PC, I did a full new install on my laptop and had no issues there. But that of course is different than an upgrade.

Faehnchen · December 29, 2022, 8:30pm

I did just the same. I tested the harddrive with the diagnosis tool from the live environment and saw that some sektors were corrupted. So maybe it was an error in the filesystem after all. I just installed Mabox new on a freshly wiped HDD. Hope everything works fine from here on.

HTinEdin · March 2, 2024, 2:21pm

Just to help anyone else who hit this problem, there is actually a simple explanation which it took me a long time to find. In my case anyway. If you already have an X session running, lightdm detects this, aborts the creation of a new session and returns to the login screen. So if, for instance, you have launched a headless session via ssh before ever logging in from the console, you may hit this problem.

I’m guessing that that’s why people always report that rebooting fixes the problem, so your disk was probably just fine.

You can easily check if this is the problem, by using Ctrl-Alt-F2 to launch a non-X session, then pgrep X…