You are not logged in.

#1 2024-04-30 18:37:19

maximiliano
Member
Registered: 2013-04-16
Posts: 27

[SOLVED] DE froozen after SDDM

Hi all! yesterday I did a full OS update and now I can't access any of my DE's anymore, is someone facing this issue ? I found something interesting if I unplug my network wire everything work's so the issue is 100% related to the network service ( I use networkmanager )

Kernel version:

[root@Tesla /]# uname -ar
Linux Tesla 6.7.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:31:48 +0000 x86_64 GNU/Linux

Digging on the journalctl log I just found this kind of error

Apr 30 13:31:47 Tesla sddm[696]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Apr 30 13:31:47 Tesla sddm[696]: Auth: sddm-helper (--socket /tmp/sddm-auth-357b02b6-2f64-43c6-8237-50a79f9ccd9e --id 1 --start i3-with-shmlog --user maximiliano) crashed (exit code 1)
Apr 30 13:31:47 Tesla sddm[696]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Apr 30 13:31:47 Tesla sddm[696]: Auth: sddm-helper exited with 1
Apr 30 13:31:47 Tesla systemd[1]: Stopped Daily verification of password and group files.
Apr 30 13:31:47 Tesla systemd[1]: systemd-tmpfiles-clean.timer: Deactivated successfully.
Apr 30 13:31:47 Tesla systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Apr 30 13:31:47 Tesla kdeconnectd[1027]: 2024-04-30T13:31:47 default: The X11 connection broke (error 1). Did the X11 server die?
Apr 30 13:30:56 Tesla alsactl[617]: alsa-lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2

Journalctl of NetworkManager

Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8960] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8962] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8968] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8977] device (anbox0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8980] policy: auto-activating connection 'anbox-net' (22062f1c-eaa7-44de-92b6-5879d19fbae0)
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8981] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8983] device (anbox0): Activation: starting connection 'anbox-net' (22062f1c-eaa7-44de-92b6-5879d19fbae0)
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8983] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8986] device (lo): Activation: successful, device activated.
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8989] device (anbox0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8991] manager: NetworkManager state is now CONNECTING
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8994] device (anbox0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 30 13:30:56 Tesla NetworkManager[616]: <info>  [1714494656.8998] device (anbox0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 30 13:30:57 Tesla NetworkManager[616]: <info>  [1714494657.2822] dnsmasq-manager: starting dnsmasq...
Apr 30 13:30:57 Tesla dnsmasq[774]: started, version 2.90 cachesize 150
Apr 30 13:30:57 Tesla dnsmasq[774]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loo>
Apr 30 13:30:57 Tesla dnsmasq[774]: chown of PID file /var/run/nm-dnsmasq-anbox0.pid failed: Operation not permitted
Apr 30 13:30:57 Tesla dnsmasq-dhcp[774]: DHCP, IP range 192.168.250.10 -- 192.168.250.254, lease time 1h
Apr 30 13:30:57 Tesla dnsmasq[774]: reading /etc/resolv.conf
Apr 30 13:30:57 Tesla dnsmasq[774]: using nameserver 8.8.8.8#53
Apr 30 13:30:57 Tesla dnsmasq[774]: cleared cache
Apr 30 13:30:59 Tesla NetworkManager[616]: <info>  [1714494659.1487] device (anbox0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Apr 30 13:30:59 Tesla NetworkManager[616]: <info>  [1714494659.1523] device (anbox0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Apr 30 13:30:59 Tesla NetworkManager[616]: <info>  [1714494659.1528] device (anbox0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Apr 30 13:30:59 Tesla NetworkManager[616]: <info>  [1714494659.1536] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 30 13:30:59 Tesla NetworkManager[616]: <info>  [1714494659.1543] device (anbox0): Activation: successful, device activated.
Apr 30 13:31:02 Tesla NetworkManager[616]: <info>  [1714494662.8375] manager: startup complete
Apr 30 13:31:36 Tesla NetworkManager[616]: <info>  [1714494696.2933] agent-manager: agent[f568099c8e38e70e,:1.34/org.freedesktop.nm-applet/1000]: agent registered
Apr 30 13:31:47 Tesla systemd[1]: Stopping Network Manager...
Apr 30 13:31:47 Tesla NetworkManager[616]: <info>  [1714494707.6481] caught SIGTERM, shutting down normally.
Apr 30 13:31:47 Tesla NetworkManager[616]: <info>  [1714494707.6485] device (anbox0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'manag>
Apr 30 13:31:47 Tesla NetworkManager[616]: <info>  [1714494707.6486] manager: NetworkManager state is now DISCONNECTING
Apr 30 13:31:47 Tesla NetworkManager[616]: <warn>  [1714494707.6507] dispatcher: (7) failed (after 0.001 sec): Could not activate remote peer 'org.freedesktop.nm_dispatch>
Apr 30 13:31:47 Tesla NetworkManager[616]: <info>  [1714494707.6507] device (anbox0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed>
Apr 30 13:31:47 Tesla dnsmasq[774]: exiting on receipt of SIGTERM
Apr 30 13:31:47 Tesla NetworkManager[616]: <info>  [1714494707.7284] manager: NetworkManager state is now DISCONNECTED
Apr 30 13:31:47 Tesla NetworkManager[616]: <info>  [1714494707.7461] exiting (success)
Apr 30 13:31:47 Tesla systemd[1]: NetworkManager.service: Deactivated successfully.
Apr 30 13:31:47 Tesla systemd[1]: Stopped Network Manager.

Journalctl of SDDM

-- Boot 92d52458bccf4ec0ab5e01a9ac12947a --
Apr 30 09:46:00 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 09:46:00 Tesla sddm[719]: Initializing...
Apr 30 09:46:00 Tesla sddm[719]: Starting...
Apr 30 09:46:00 Tesla sddm[719]: Logind interface found
Apr 30 09:46:00 Tesla sddm[719]: Adding new display...
Apr 30 09:46:00 Tesla sddm[719]: Loaded empty theme configuration
Apr 30 09:46:00 Tesla sddm[719]: Xauthority path: "/run/sddm/xauth_DEuEhz"
Apr 30 09:46:00 Tesla sddm[719]: Using VT 2
Apr 30 09:46:00 Tesla sddm[719]: Display server starting...
Apr 30 09:46:00 Tesla sddm[719]: Writing cookie to "/run/sddm/xauth_DEuEhz"
Apr 30 09:46:00 Tesla sddm[719]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_DEuEhz -noreset -displayfd 16
Apr 30 09:46:00 Tesla sddm[719]: Setting default cursor
Apr 30 09:46:01 Tesla sddm[719]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 09:46:01 Tesla sddm[719]: Display server started.
Apr 30 09:46:01 Tesla sddm[719]: Socket server starting...
Apr 30 09:46:01 Tesla sddm[719]: Socket server started.
Apr 30 09:46:01 Tesla sddm[719]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 09:46:01 Tesla sddm[719]: Greeter starting...
Apr 30 09:46:01 Tesla sddm-helper[822]: [PAM] Starting...
Apr 30 09:46:01 Tesla sddm-helper[822]: [PAM] Authenticating...
Apr 30 09:46:01 Tesla sddm-helper[822]: [PAM] returning.
Apr 30 09:46:01 Tesla sddm-helper[822]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 09:46:01 Tesla sddm-helper[822]: Writing cookie to "/tmp/xauth_ZmztKQ"
Apr 30 09:46:01 Tesla sddm-helper[822]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-fWEnSG --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 09:46:01 Tesla sddm[719]: Greeter session started successfully
Apr 30 09:46:01 Tesla sddm[719]: Message received from greeter: Connect
Apr 30 09:46:10 Tesla sddm[719]: Message received from greeter: Login
Apr 30 09:46:10 Tesla sddm[719]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Apr 30 09:46:10 Tesla sddm[719]: Session "/usr/share/wayland-sessions/plasma.desktop" selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1
Apr 30 09:46:10 Tesla sddm-helper[867]: [PAM] Starting...
Apr 30 09:46:10 Tesla sddm-helper[867]: [PAM] Authenticating...
Apr 30 09:46:10 Tesla sddm-helper[867]: [PAM] Preparing to converse...
Apr 30 09:46:10 Tesla sddm-helper[867]: [PAM] Conversation with 1 messages
Apr 30 09:46:10 Tesla sddm-helper[867]: gkr-pam: unable to locate daemon control file
Apr 30 09:46:10 Tesla sddm-helper[867]: gkr-pam: stashed password to try later in open session
Apr 30 09:46:10 Tesla sddm-helper[867]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 09:46:10 Tesla sddm-helper[867]: [PAM] returning.
Apr 30 09:46:10 Tesla sddm[719]: Authentication for user  "maximiliano"  successful
Apr 30 09:46:10 Tesla sddm-helper[867]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 30 09:46:10 Tesla sddm-helper[867]: pam_unix(sddm:session): session opened for user maximiliano(uid=1000) by maximiliano(uid=0)
Apr 30 09:46:10 Tesla sddm[719]: Auth: sddm-helper exited successfully
Apr 30 09:46:10 Tesla sddm[719]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Apr 30 09:46:11 Tesla sddm-helper[867]: gkr-pam: unlocked login keyring
Apr 30 09:46:11 Tesla sddm-helper[867]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Apr 30 09:46:11 Tesla sddm-helper[867]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Apr 30 09:46:11 Tesla sddm[719]: Session started true
-- Boot 76542008b65042e69fdb003e94985fd1 --
Apr 30 10:00:24 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 10:00:24 Tesla sddm[724]: Initializing...
Apr 30 10:00:25 Tesla sddm[724]: Starting...
Apr 30 10:00:25 Tesla sddm[724]: Logind interface found
Apr 30 10:00:25 Tesla sddm[724]: Adding new display...
Apr 30 10:00:25 Tesla sddm[724]: Loaded empty theme configuration
Apr 30 10:00:25 Tesla sddm[724]: Xauthority path: "/run/sddm/xauth_OpfvMB"
Apr 30 10:00:25 Tesla sddm[724]: Using VT 2
Apr 30 10:00:25 Tesla sddm[724]: Display server starting...
Apr 30 10:00:25 Tesla sddm[724]: Writing cookie to "/run/sddm/xauth_OpfvMB"
Apr 30 10:00:25 Tesla sddm[724]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_OpfvMB -noreset -displayfd 16
Apr 30 10:00:26 Tesla sddm[724]: Setting default cursor
Apr 30 10:00:26 Tesla sddm[724]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 10:00:26 Tesla sddm[724]: Display server started.
Apr 30 10:00:26 Tesla sddm[724]: Socket server starting...
Apr 30 10:00:26 Tesla sddm[724]: Socket server started.
Apr 30 10:00:26 Tesla sddm[724]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 10:00:26 Tesla sddm[724]: Greeter starting...
Apr 30 10:00:26 Tesla sddm-helper[829]: [PAM] Starting...
Apr 30 10:00:26 Tesla sddm-helper[829]: [PAM] Authenticating...
Apr 30 10:00:26 Tesla sddm-helper[829]: [PAM] returning.
Apr 30 10:00:26 Tesla sddm-helper[829]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 10:00:26 Tesla sddm-helper[829]: Writing cookie to "/tmp/xauth_fjVbFB"
Apr 30 10:00:26 Tesla sddm-helper[829]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-idqcUK --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 10:00:26 Tesla sddm[724]: Greeter session started successfully
Apr 30 10:00:26 Tesla sddm[724]: Message received from greeter: Connect
Apr 30 10:00:32 Tesla sddm[724]: Message received from greeter: Login
Apr 30 10:00:32 Tesla sddm[724]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Apr 30 10:00:32 Tesla sddm[724]: Session "/usr/share/xsessions/plasmax11.desktop" selected, command: "/usr/bin/startplasma-x11" for VT 2
Apr 30 10:00:32 Tesla sddm-helper[873]: [PAM] Starting...
Apr 30 10:00:32 Tesla sddm-helper[873]: [PAM] Authenticating...
Apr 30 10:00:32 Tesla sddm-helper[873]: [PAM] Preparing to converse...
Apr 30 10:00:32 Tesla sddm-helper[873]: [PAM] Conversation with 1 messages
Apr 30 10:00:32 Tesla sddm-helper[873]: gkr-pam: unable to locate daemon control file
Apr 30 10:00:32 Tesla sddm-helper[873]: gkr-pam: stashed password to try later in open session
Apr 30 10:00:32 Tesla sddm-helper[873]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 10:00:32 Tesla sddm-helper[873]: [PAM] returning.
Apr 30 10:00:32 Tesla sddm[724]: Authentication for user  "maximiliano"  successful
Apr 30 10:00:32 Tesla sddm-helper[873]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 30 10:00:32 Tesla sddm-helper[873]: pam_unix(sddm:session): session opened for user maximiliano(uid=1000) by maximiliano(uid=0)
Apr 30 10:00:32 Tesla sddm[724]: Auth: sddm-helper exited successfully
Apr 30 10:00:32 Tesla sddm[724]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Apr 30 10:00:32 Tesla sddm-helper[873]: gkr-pam: unlocked login keyring
Apr 30 10:00:32 Tesla sddm-helper[873]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Apr 30 10:00:32 Tesla sddm-helper[873]: Writing cookie to "/tmp/xauth_hahhTo"
Apr 30 10:00:32 Tesla sddm-helper[873]: Starting X11 session: "" "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
Apr 30 10:00:32 Tesla sddm[724]: Session started true
-- Boot 8e5e88f30988493eaf4042b37840f01f --
Apr 30 10:03:03 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 10:03:03 Tesla sddm[742]: Initializing...
Apr 30 10:03:03 Tesla sddm[742]: Starting...
Apr 30 10:03:03 Tesla sddm[742]: Logind interface found
Apr 30 10:03:03 Tesla sddm[742]: Adding new display...
Apr 30 10:03:03 Tesla sddm[742]: Loaded empty theme configuration
Apr 30 10:03:03 Tesla sddm[742]: Xauthority path: "/run/sddm/xauth_BXJfFj"
Apr 30 10:03:03 Tesla sddm[742]: Using VT 2
Apr 30 10:03:03 Tesla sddm[742]: Display server starting...
Apr 30 10:03:03 Tesla sddm[742]: Writing cookie to "/run/sddm/xauth_BXJfFj"
Apr 30 10:03:03 Tesla sddm[742]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BXJfFj -noreset -displayfd 16
Apr 30 10:03:03 Tesla sddm[742]: Setting default cursor
Apr 30 10:03:04 Tesla sddm[742]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 10:03:04 Tesla sddm[742]: Display server started.
Apr 30 10:03:04 Tesla sddm[742]: Socket server starting...
Apr 30 10:03:04 Tesla sddm[742]: Socket server started.
Apr 30 10:03:04 Tesla sddm[742]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 10:03:04 Tesla sddm[742]: Greeter starting...
Apr 30 10:03:04 Tesla sddm-helper[844]: [PAM] Starting...
Apr 30 10:03:04 Tesla sddm-helper[844]: [PAM] Authenticating...
Apr 30 10:03:04 Tesla sddm-helper[844]: [PAM] returning.
Apr 30 10:03:04 Tesla sddm-helper[844]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 10:03:04 Tesla sddm-helper[844]: Writing cookie to "/tmp/xauth_nNeVwh"
Apr 30 10:03:04 Tesla sddm-helper[844]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-WmwdNW --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 10:03:04 Tesla sddm[742]: Greeter session started successfully
Apr 30 10:03:04 Tesla sddm[742]: Message received from greeter: Connect
Apr 30 10:03:15 Tesla sddm[742]: Message received from greeter: Login
Apr 30 10:03:15 Tesla sddm[742]: Reading from "/usr/share/xsessions/i3.desktop"
Apr 30 10:03:15 Tesla sddm[742]: Session "/usr/share/xsessions/i3.desktop" selected, command: "i3" for VT 2
Apr 30 10:03:15 Tesla sddm-helper[889]: [PAM] Starting...
Apr 30 10:03:15 Tesla sddm-helper[889]: [PAM] Authenticating...
Apr 30 10:03:15 Tesla sddm-helper[889]: [PAM] Preparing to converse...
Apr 30 10:03:15 Tesla sddm-helper[889]: [PAM] Conversation with 1 messages
Apr 30 10:03:15 Tesla sddm-helper[889]: gkr-pam: unable to locate daemon control file
Apr 30 10:03:15 Tesla sddm-helper[889]: gkr-pam: stashed password to try later in open session
Apr 30 10:03:15 Tesla sddm-helper[889]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 10:03:15 Tesla sddm-helper[889]: [PAM] returning.
Apr 30 10:03:15 Tesla sddm[742]: Authentication for user  "maximiliano"  successful
Apr 30 10:03:15 Tesla sddm-helper[889]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 30 10:03:15 Tesla sddm-helper[889]: pam_unix(sddm:session): session opened for user maximiliano(uid=1000) by maximiliano(uid=0)
Apr 30 10:03:15 Tesla sddm[742]: Auth: sddm-helper exited successfully
Apr 30 10:03:15 Tesla sddm[742]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
-- Boot 90617c9194834ccb9b6e1c1d1ba18a2f --
Apr 30 10:04:02 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 10:04:02 Tesla sddm[735]: Initializing...
Apr 30 10:04:02 Tesla sddm[735]: Starting...
Apr 30 10:04:02 Tesla sddm[735]: Logind interface found
Apr 30 10:04:02 Tesla sddm[735]: Adding new display...
Apr 30 10:04:02 Tesla sddm[735]: Loaded empty theme configuration
Apr 30 10:04:02 Tesla sddm[735]: Xauthority path: "/run/sddm/xauth_EyzcSv"
Apr 30 10:04:02 Tesla sddm[735]: Using VT 2
Apr 30 10:04:02 Tesla sddm[735]: Display server starting...
Apr 30 10:04:02 Tesla sddm[735]: Writing cookie to "/run/sddm/xauth_EyzcSv"
Apr 30 10:04:02 Tesla sddm[735]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_EyzcSv -noreset -displayfd 16
Apr 30 10:04:03 Tesla sddm[735]: Setting default cursor
Apr 30 10:04:03 Tesla sddm[735]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 10:04:03 Tesla sddm[735]: Display server started.
Apr 30 10:04:03 Tesla sddm[735]: Socket server starting...
Apr 30 10:04:03 Tesla sddm[735]: Socket server started.
Apr 30 10:04:03 Tesla sddm[735]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 10:04:04 Tesla sddm[735]: Greeter starting...
Apr 30 10:04:04 Tesla sddm-helper[840]: [PAM] Starting...
Apr 30 10:04:04 Tesla sddm-helper[840]: [PAM] Authenticating...
Apr 30 10:04:04 Tesla sddm-helper[840]: [PAM] returning.
Apr 30 10:04:04 Tesla sddm-helper[840]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 10:04:04 Tesla sddm-helper[840]: Writing cookie to "/tmp/xauth_znTMju"
Apr 30 10:04:04 Tesla sddm-helper[840]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-veXBXL --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 10:04:04 Tesla sddm[735]: Greeter session started successfully
Apr 30 10:04:04 Tesla sddm[735]: Message received from greeter: Connect
Apr 30 10:04:11 Tesla sddm[735]: Message received from greeter: Login
Apr 30 10:04:11 Tesla sddm[735]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Apr 30 10:04:11 Tesla sddm[735]: Session "/usr/share/wayland-sessions/plasma.desktop" selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1
Apr 30 10:04:11 Tesla sddm-helper[886]: [PAM] Starting...
Apr 30 10:04:11 Tesla sddm-helper[886]: [PAM] Authenticating...
Apr 30 10:04:11 Tesla sddm-helper[886]: [PAM] Preparing to converse...
Apr 30 10:04:11 Tesla sddm-helper[886]: [PAM] Conversation with 1 messages
Apr 30 10:04:11 Tesla sddm-helper[886]: gkr-pam: unable to locate daemon control file
Apr 30 10:04:11 Tesla sddm-helper[886]: gkr-pam: stashed password to try later in open session
Apr 30 10:04:11 Tesla sddm-helper[886]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 10:04:11 Tesla sddm-helper[886]: [PAM] returning.
Apr 30 10:04:11 Tesla sddm[735]: Authentication for user  "maximiliano"  successful
Apr 30 10:04:11 Tesla sddm-helper[886]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 30 10:04:11 Tesla sddm-helper[886]: pam_unix(sddm:session): session opened for user maximiliano(uid=1000) by maximiliano(uid=0)
Apr 30 10:04:11 Tesla sddm[735]: Auth: sddm-helper exited successfully
Apr 30 10:04:11 Tesla sddm[735]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
-- Boot c4827888f0184f8dba77593b3e7dc5d5 --
Apr 30 13:20:17 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 13:20:17 Tesla sddm[705]: Initializing...
Apr 30 13:20:17 Tesla sddm[705]: Starting...
Apr 30 13:20:17 Tesla sddm[705]: Logind interface found
Apr 30 13:20:17 Tesla sddm[705]: Adding new display...
Apr 30 13:20:17 Tesla sddm[705]: Loaded empty theme configuration
Apr 30 13:20:17 Tesla sddm[705]: Xauthority path: "/run/sddm/xauth_DdvXoQ"
Apr 30 13:20:17 Tesla sddm[705]: Using VT 2
Apr 30 13:20:17 Tesla sddm[705]: Display server starting...
Apr 30 13:20:17 Tesla sddm[705]: Writing cookie to "/run/sddm/xauth_DdvXoQ"
Apr 30 13:20:17 Tesla sddm[705]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_DdvXoQ -noreset -displayfd 16
Apr 30 13:20:18 Tesla sddm[705]: Setting default cursor
Apr 30 13:20:19 Tesla sddm[705]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 13:20:19 Tesla sddm[705]: Display server started.
Apr 30 13:20:19 Tesla sddm[705]: Socket server starting...
Apr 30 13:20:19 Tesla sddm[705]: Socket server started.
Apr 30 13:20:19 Tesla sddm[705]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 13:20:19 Tesla sddm[705]: Greeter starting...
Apr 30 13:20:19 Tesla sddm-helper[804]: [PAM] Starting...
Apr 30 13:20:19 Tesla sddm-helper[804]: [PAM] Authenticating...
Apr 30 13:20:19 Tesla sddm-helper[804]: [PAM] returning.
Apr 30 13:20:19 Tesla sddm-helper[804]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 13:20:19 Tesla sddm-helper[804]: Writing cookie to "/tmp/xauth_uvoLpj"
Apr 30 13:20:19 Tesla sddm-helper[804]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-oLnelS --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 13:20:19 Tesla sddm[705]: Greeter session started successfully
Apr 30 13:20:19 Tesla sddm[705]: Message received from greeter: Connect
Apr 30 13:21:08 Tesla sddm[705]: Message received from greeter: Login
Apr 30 13:21:08 Tesla sddm[705]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Apr 30 13:21:08 Tesla sddm[705]: Session "/usr/share/xsessions/plasmax11.desktop" selected, command: "/usr/bin/startplasma-x11" for VT 2
Apr 30 13:21:08 Tesla sddm-helper[1076]: [PAM] Starting...
Apr 30 13:21:08 Tesla sddm-helper[1076]: [PAM] Authenticating...
Apr 30 13:21:12 Tesla sddm[705]: Message received from greeter: Login
Apr 30 13:21:12 Tesla sddm[705]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Apr 30 13:21:12 Tesla sddm[705]: Existing authentication ongoing, aborting
Apr 30 13:21:25 Tesla sddm[705]: Message received from greeter: Login
Apr 30 13:21:25 Tesla sddm[705]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Apr 30 13:21:25 Tesla sddm[705]: Existing authentication ongoing, aborting
Apr 30 13:21:26 Tesla sddm[705]: Message received from greeter: Login
Apr 30 13:21:26 Tesla sddm[705]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Apr 30 13:21:26 Tesla sddm[705]: Existing authentication ongoing, aborting
Apr 30 13:21:27 Tesla sddm[705]: Message received from greeter: Login
Apr 30 13:21:27 Tesla sddm[705]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Apr 30 13:21:27 Tesla sddm[705]: Existing authentication ongoing, aborting
Apr 30 13:21:28 Tesla sddm[705]: Message received from greeter: Login
Apr 30 13:21:28 Tesla sddm[705]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Apr 30 13:21:28 Tesla sddm[705]: Existing authentication ongoing, aborting
Apr 30 13:21:33 Tesla sddm-helper[1076]: pam_systemd_home(sddm:auth): Failed to query user record: Connection timed out
Apr 30 13:21:33 Tesla sddm-helper[1076]: [PAM] Preparing to converse...
Apr 30 13:21:33 Tesla sddm-helper[1076]: [PAM] Conversation with 1 messages
Apr 30 13:21:33 Tesla sddm-helper[1076]: gkr-pam: unable to locate daemon control file
Apr 30 13:21:33 Tesla sddm-helper[1076]: gkr-pam: stashed password to try later in open session
Apr 30 13:21:33 Tesla sddm-helper[1076]: [PAM] returning.
Apr 30 13:21:33 Tesla sddm-helper[1076]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 13:21:33 Tesla sddm[705]: Authentication for user  "maximiliano"  successful
Apr 30 13:21:33 Tesla sddm-helper[1076]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
-- Boot eedb764a4c364fb6b2d607fd5529b83d --
Apr 30 13:23:14 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 13:23:14 Tesla sddm[694]: Initializing...
Apr 30 13:23:14 Tesla sddm[694]: Starting...
Apr 30 13:23:14 Tesla sddm[694]: Logind interface found
Apr 30 13:23:14 Tesla sddm[694]: Adding new display...
Apr 30 13:23:14 Tesla sddm[694]: Loaded empty theme configuration
Apr 30 13:23:14 Tesla sddm[694]: Xauthority path: "/run/sddm/xauth_iDgakN"
Apr 30 13:23:14 Tesla sddm[694]: Using VT 2
Apr 30 13:23:14 Tesla sddm[694]: Display server starting...
Apr 30 13:23:14 Tesla sddm[694]: Writing cookie to "/run/sddm/xauth_iDgakN"
Apr 30 13:23:14 Tesla sddm[694]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_iDgakN -noreset -displayfd 16
Apr 30 13:23:15 Tesla sddm[694]: Setting default cursor
Apr 30 13:23:15 Tesla sddm[694]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 13:23:15 Tesla sddm[694]: Display server started.
Apr 30 13:23:15 Tesla sddm[694]: Socket server starting...
Apr 30 13:23:15 Tesla sddm[694]: Socket server started.
Apr 30 13:23:15 Tesla sddm[694]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 13:23:15 Tesla sddm[694]: Greeter starting...
Apr 30 13:23:15 Tesla sddm-helper[789]: [PAM] Starting...
Apr 30 13:23:15 Tesla sddm-helper[789]: [PAM] Authenticating...
Apr 30 13:23:15 Tesla sddm-helper[789]: [PAM] returning.
Apr 30 13:23:15 Tesla sddm-helper[789]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 13:23:15 Tesla sddm-helper[789]: Writing cookie to "/tmp/xauth_rWeCve"
Apr 30 13:23:15 Tesla sddm-helper[789]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-gxJOlc --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 13:23:15 Tesla sddm[694]: Greeter session started successfully
Apr 30 13:23:15 Tesla sddm[694]: Message received from greeter: Connect
-- Boot 94a0768ff38f4bb39f3c475ea6dc00c9 --
Apr 30 13:25:05 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 13:25:05 Tesla sddm[701]: Initializing...
Apr 30 13:25:05 Tesla sddm[701]: Starting...
Apr 30 13:25:05 Tesla sddm[701]: Logind interface found
Apr 30 13:25:05 Tesla sddm[701]: Adding new display...
Apr 30 13:25:05 Tesla sddm[701]: Loaded empty theme configuration
Apr 30 13:25:05 Tesla sddm[701]: Xauthority path: "/run/sddm/xauth_FlnlyQ"
Apr 30 13:25:05 Tesla sddm[701]: Using VT 2
Apr 30 13:25:05 Tesla sddm[701]: Display server starting...
Apr 30 13:25:05 Tesla sddm[701]: Writing cookie to "/run/sddm/xauth_FlnlyQ"
Apr 30 13:25:05 Tesla sddm[701]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_FlnlyQ -noreset -displayfd 16
Apr 30 13:25:05 Tesla sddm[701]: Setting default cursor
Apr 30 13:25:06 Tesla sddm[701]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 13:25:06 Tesla sddm[701]: Display server started.
Apr 30 13:25:06 Tesla sddm[701]: Socket server starting...
Apr 30 13:25:06 Tesla sddm[701]: Socket server started.
Apr 30 13:25:06 Tesla sddm[701]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 13:25:06 Tesla sddm[701]: Greeter starting...
Apr 30 13:25:06 Tesla sddm-helper[799]: [PAM] Starting...
Apr 30 13:25:06 Tesla sddm-helper[799]: [PAM] Authenticating...
Apr 30 13:25:06 Tesla sddm-helper[799]: [PAM] returning.
Apr 30 13:25:06 Tesla sddm-helper[799]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 13:25:06 Tesla sddm-helper[799]: Writing cookie to "/tmp/xauth_ATgNkR"
Apr 30 13:25:06 Tesla sddm-helper[799]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-AhpVQO --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 13:25:06 Tesla sddm[701]: Greeter session started successfully
Apr 30 13:25:06 Tesla sddm[701]: Message received from greeter: Connect
Apr 30 13:25:14 Tesla sddm[701]: Message received from greeter: Login
Apr 30 13:25:14 Tesla sddm[701]: Reading from "/usr/share/xsessions/i3-with-shmlog.desktop"
Apr 30 13:25:14 Tesla sddm[701]: Session "/usr/share/xsessions/i3-with-shmlog.desktop" selected, command: "i3-with-shmlog" for VT 2
Apr 30 13:25:14 Tesla sddm-helper[845]: [PAM] Starting...
Apr 30 13:25:14 Tesla sddm-helper[845]: [PAM] Authenticating...
Apr 30 13:25:14 Tesla sddm-helper[845]: [PAM] Preparing to converse...
Apr 30 13:25:14 Tesla sddm-helper[845]: [PAM] Conversation with 1 messages
Apr 30 13:25:14 Tesla sddm-helper[845]: gkr-pam: unable to locate daemon control file
Apr 30 13:25:14 Tesla sddm-helper[845]: gkr-pam: stashed password to try later in open session
Apr 30 13:25:14 Tesla sddm-helper[845]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 13:25:14 Tesla sddm-helper[845]: [PAM] returning.
Apr 30 13:25:14 Tesla sddm[701]: Authentication for user  "maximiliano"  successful
Apr 30 13:25:14 Tesla sddm-helper[845]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 30 13:25:14 Tesla sddm-helper[845]: pam_unix(sddm:session): session opened for user maximiliano(uid=1000) by maximiliano(uid=0)
Apr 30 13:25:14 Tesla sddm[701]: Auth: sddm-helper exited successfully
Apr 30 13:25:14 Tesla sddm[701]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Apr 30 13:25:15 Tesla sddm-helper[845]: gkr-pam: unlocked login keyring
Apr 30 13:25:15 Tesla sddm-helper[845]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Apr 30 13:25:15 Tesla sddm-helper[845]: Writing cookie to "/tmp/xauth_EKJFff"
Apr 30 13:25:15 Tesla sddm-helper[845]: Starting X11 session: "" "/usr/share/sddm/scripts/Xsession \"i3-with-shmlog\""
Apr 30 13:25:15 Tesla sddm[701]: Session started true
-- Boot b234e79bc95f422381f90c61562ad154 --
Apr 30 13:29:36 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 13:29:36 Tesla sddm[685]: Initializing...
Apr 30 13:29:36 Tesla sddm[685]: Starting...
Apr 30 13:29:36 Tesla sddm[685]: Logind interface found
Apr 30 13:29:36 Tesla sddm[685]: Adding new display...
Apr 30 13:29:36 Tesla sddm[685]: Loaded empty theme configuration
Apr 30 13:29:36 Tesla sddm[685]: Xauthority path: "/run/sddm/xauth_BCDnAe"
Apr 30 13:29:36 Tesla sddm[685]: Using VT 2
Apr 30 13:29:36 Tesla sddm[685]: Display server starting...
Apr 30 13:29:36 Tesla sddm[685]: Writing cookie to "/run/sddm/xauth_BCDnAe"
Apr 30 13:29:36 Tesla sddm[685]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BCDnAe -noreset -displayfd 16
Apr 30 13:29:36 Tesla sddm[685]: Setting default cursor
Apr 30 13:29:37 Tesla sddm[685]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 13:29:37 Tesla sddm[685]: Display server started.
Apr 30 13:29:37 Tesla sddm[685]: Socket server starting...
Apr 30 13:29:37 Tesla sddm[685]: Socket server started.
Apr 30 13:29:37 Tesla sddm[685]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 13:29:37 Tesla sddm[685]: Greeter starting...
Apr 30 13:29:37 Tesla sddm-helper[782]: [PAM] Starting...
Apr 30 13:29:37 Tesla sddm-helper[782]: [PAM] Authenticating...
Apr 30 13:29:37 Tesla sddm-helper[782]: [PAM] returning.
Apr 30 13:29:37 Tesla sddm-helper[782]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 13:29:37 Tesla sddm-helper[782]: Writing cookie to "/tmp/xauth_OBxsGP"
Apr 30 13:29:37 Tesla sddm-helper[782]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-OPyEDc --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 13:29:37 Tesla sddm[685]: Greeter session started successfully
Apr 30 13:29:37 Tesla sddm[685]: Message received from greeter: Connect
Apr 30 13:29:49 Tesla sddm[685]: Message received from greeter: Login
Apr 30 13:29:49 Tesla sddm[685]: Reading from "/usr/share/xsessions/i3-with-shmlog.desktop"
Apr 30 13:29:49 Tesla sddm[685]: Session "/usr/share/xsessions/i3-with-shmlog.desktop" selected, command: "i3-with-shmlog" for VT 2
Apr 30 13:29:49 Tesla sddm-helper[828]: [PAM] Starting...
Apr 30 13:29:49 Tesla sddm-helper[828]: [PAM] Authenticating...
Apr 30 13:29:49 Tesla sddm-helper[828]: [PAM] Preparing to converse...
Apr 30 13:29:49 Tesla sddm-helper[828]: [PAM] Conversation with 1 messages
Apr 30 13:29:49 Tesla sddm-helper[828]: gkr-pam: unable to locate daemon control file
Apr 30 13:29:49 Tesla sddm-helper[828]: gkr-pam: stashed password to try later in open session
Apr 30 13:29:49 Tesla sddm-helper[828]: [PAM] returning.
Apr 30 13:29:49 Tesla sddm-helper[828]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 13:29:49 Tesla sddm[685]: Authentication for user  "maximiliano"  successful
Apr 30 13:29:49 Tesla sddm-helper[828]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 30 13:29:49 Tesla sddm-helper[828]: pam_unix(sddm:session): session opened for user maximiliano(uid=1000) by maximiliano(uid=0)
Apr 30 13:29:49 Tesla sddm[685]: Auth: sddm-helper exited successfully
Apr 30 13:29:49 Tesla sddm[685]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
-- Boot 3b5c87b67aea4ec4a15f80a7127d831d --
Apr 30 13:30:56 Tesla systemd[1]: Started Simple Desktop Display Manager.
Apr 30 13:30:56 Tesla sddm[696]: Initializing...
Apr 30 13:30:56 Tesla sddm[696]: Starting...
Apr 30 13:30:56 Tesla sddm[696]: Logind interface found
Apr 30 13:30:56 Tesla sddm[696]: Adding new display...
Apr 30 13:30:56 Tesla sddm[696]: Loaded empty theme configuration
Apr 30 13:30:56 Tesla sddm[696]: Xauthority path: "/run/sddm/xauth_lcsLlT"
Apr 30 13:30:56 Tesla sddm[696]: Using VT 2
Apr 30 13:30:56 Tesla sddm[696]: Display server starting...
Apr 30 13:30:56 Tesla sddm[696]: Writing cookie to "/run/sddm/xauth_lcsLlT"
Apr 30 13:30:56 Tesla sddm[696]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_lcsLlT -noreset -displayfd 16
Apr 30 13:30:57 Tesla sddm[696]: Setting default cursor
Apr 30 13:30:58 Tesla sddm[696]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 30 13:30:58 Tesla sddm[696]: Display server started.
Apr 30 13:30:58 Tesla sddm[696]: Socket server starting...
Apr 30 13:30:58 Tesla sddm[696]: Socket server started.
Apr 30 13:30:58 Tesla sddm[696]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Apr 30 13:30:58 Tesla sddm[696]: Greeter starting...
Apr 30 13:30:58 Tesla sddm-helper[793]: [PAM] Starting...
Apr 30 13:30:58 Tesla sddm-helper[793]: [PAM] Authenticating...
Apr 30 13:30:58 Tesla sddm-helper[793]: [PAM] returning.
Apr 30 13:30:58 Tesla sddm-helper[793]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=977) by (uid=0)
Apr 30 13:30:58 Tesla sddm-helper[793]: Writing cookie to "/tmp/xauth_mBICRd"
Apr 30 13:30:58 Tesla sddm-helper[793]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-arelpK --theme /usr/share/sddm/themes/sugar-candy"
Apr 30 13:30:58 Tesla sddm[696]: Greeter session started successfully
Apr 30 13:30:58 Tesla sddm[696]: Message received from greeter: Connect
Apr 30 13:31:35 Tesla sddm[696]: Message received from greeter: Login
Apr 30 13:31:35 Tesla sddm[696]: Reading from "/usr/share/xsessions/i3-with-shmlog.desktop"
Apr 30 13:31:35 Tesla sddm[696]: Session "/usr/share/xsessions/i3-with-shmlog.desktop" selected, command: "i3-with-shmlog" for VT 2
Apr 30 13:31:35 Tesla sddm-helper[841]: [PAM] Starting...
Apr 30 13:31:35 Tesla sddm-helper[841]: [PAM] Authenticating...
Apr 30 13:31:35 Tesla sddm-helper[841]: [PAM] Preparing to converse...
Apr 30 13:31:35 Tesla sddm-helper[841]: [PAM] Conversation with 1 messages
Apr 30 13:31:35 Tesla sddm-helper[841]: gkr-pam: unable to locate daemon control file
Apr 30 13:31:35 Tesla sddm-helper[841]: gkr-pam: stashed password to try later in open session
Apr 30 13:31:35 Tesla sddm-helper[841]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Apr 30 13:31:35 Tesla sddm-helper[841]: [PAM] returning.
Apr 30 13:31:35 Tesla sddm[696]: Authentication for user  "maximiliano"  successful
Apr 30 13:31:35 Tesla sddm-helper[841]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 30 13:31:35 Tesla sddm-helper[841]: pam_unix(sddm:session): session opened for user maximiliano(uid=1000) by maximiliano(uid=0)
Apr 30 13:31:35 Tesla sddm[696]: Auth: sddm-helper exited successfully
Apr 30 13:31:35 Tesla sddm[696]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Apr 30 13:31:35 Tesla sddm-helper[841]: gkr-pam: unlocked login keyring
Apr 30 13:31:35 Tesla sddm-helper[841]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Apr 30 13:31:35 Tesla sddm-helper[841]: Writing cookie to "/tmp/xauth_GrMoqp"
Apr 30 13:31:35 Tesla sddm-helper[841]: Starting X11 session: "" "/usr/share/sddm/scripts/Xsession \"i3-with-shmlog\""
Apr 30 13:31:35 Tesla sddm[696]: Session started true
Apr 30 13:31:47 Tesla sddm[696]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Apr 30 13:31:47 Tesla sddm[696]: Auth: sddm-helper (--socket /tmp/sddm-auth-357b02b6-2f64-43c6-8237-50a79f9ccd9e --id 1 --start i3-with-shmlog --user maximiliano) crashed (exit code 1)
Apr 30 13:31:47 Tesla sddm[696]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Apr 30 13:31:47 Tesla sddm[696]: Auth: sddm-helper exited with 1
Apr 30 13:31:47 Tesla systemd[1]: Stopping Simple Desktop Display Manager...
Apr 30 13:31:47 Tesla sddm[696]: Signal received: SIGTERM
Apr 30 13:31:47 Tesla sddm[696]: Socket server stopping...
Apr 30 13:31:47 Tesla sddm[696]: Socket server stopped.
Apr 30 13:31:47 Tesla sddm[696]: Display server stopping...
Apr 30 13:31:47 Tesla sddm[696]: Display server stopped.
Apr 30 13:31:47 Tesla sddm[696]: Running display stop script  QList("/usr/share/sddm/scripts/Xstop")
Apr 30 13:31:47 Tesla systemd[1]: sddm.service: Deactivated successfully.
Apr 30 13:31:47 Tesla systemd[1]: Stopped Simple Desktop Display Manager.
Apr 30 13:31:47 Tesla systemd[1]: sddm.service: Consumed 1.933s CPU time.

Last edited by maximiliano (2024-05-02 13:32:19)

Offline

#2 2024-04-30 21:09:06

seth
Member
Registered: 2012-09-03
Posts: 52,477

Re: [SOLVED] DE froozen after SDDM

Please post your complete system journal for one boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

for the current one, after failing to login.

And though it doesn't actually look like that, just because of symptom and mitigation:

hostnamectl

Offline

#3 2024-05-01 14:11:26

maximiliano
Member
Registered: 2013-04-16
Posts: 27

Re: [SOLVED] DE froozen after SDDM

Thanks seth!

I did this

journalctl -b 6c0acb9dda9a4708a587c7703bb2ee2b --no-pager | curl -F 'file=@-' 0x0.st

since I'm running on another arch install doing an arch-chroot to the broken one, I can't execute hostnamectl

This is my journactl of the last failed login journalctl

The most weird thing is, a few seconds after SDDM the system got frozen and I can't do anything but a hard reset.

Offline

#4 2024-05-01 14:23:14

seth
Member
Registered: 2012-09-03
Posts: 52,477

Re: [SOLVED] DE froozen after SDDM

You've a static hostname and it gets set early and doesn't change.
The kernel dumps

May 01 10:58:02 Tesla NetworkManager[594]: <info>  [1714571882.2470] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May 01 10:58:02 Tesla kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 100 Mbps Half Duplex, Flow Control: None
May 01 10:58:02 Tesla kernel: BUG: scheduling while atomic: kworker/1:0/27/0x00000002
May 01 10:58:02 Tesla kernel: Modules linked in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nft_masq uinput nft_chain_nat nf_tables nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc cmac algif_hash algif_skcipher af_alg bnep intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common psmouse serio_raw iTCO_wdt intel_tcc_cooling atkbd intel_pmc_bxt libps2 x86_pkg_temp_thermal vivaldi_fmap intel_powerclamp ee1004 crct10dif_pclmul crc32_pclmul iTCO_vendor_support polyval_clmulni mei_hdcp mei_pxp polyval_generic gf128mul snd_soc_avs ghash_clmulni_intel snd_soc_hda_codec sha512_ssse3 snd_hda_ext_core btusb sha256_ssse3 uvcvideo btrtl sha1_ssse3 videobuf2_vmalloc btintel aesni_intel snd_usb_audio snd_soc_core uvc videobuf2_memops btbcm crypto_simd snd_compress eeepc_wmi snd_usbmidi_lib videobuf2_v4l2 btmtk ac97_bus
May 01 10:58:02 Tesla kernel:  snd_hda_codec_realtek asus_wmi snd_pcm_dmaengine snd_ump snd_hda_codec_generic snd_hda_codec_hdmi cryptd videodev snd_rawmidi ledtrig_audio snd_hda_intel bluetooth platform_profile videobuf2_common snd_intel_dspcfg snd_seq_device rapl i8042 snd_intel_sdw_acpi e1000e mc mousedev joydev ecdh_generic sparse_keymap intel_cstate snd_hda_codec serio snd_hda_core ptp i2c_i801 intel_uncore pps_core rfkill wmi_bmof pcspkr mxm_wmi i2c_smbus snd_hwdep intel_pmc_core mei_me intel_vsec mei pmt_telemetry acpi_pad pmt_class mac_hid vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) nct6775 nct6775_core hwmon_vid snd_aloop snd_pcm snd_timer snd soundcore coretemp i2c_dev crypto_user loop dm_mod nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid amdgpu amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec gpu_sched drm_suballoc_helper nvme drm_buddy crc32c_intel nvme_core drm_display_helper xhci_pci nvme_auth cec xhci_pci_renesas video wmi
May 01 10:58:02 Tesla kernel: CPU: 1 PID: 27 Comm: kworker/1:0 Tainted: G           OE      6.8.8-arch1-1 #1 6e5d9eb17edb3e2ef7f1d13e0aec4b6c1833b648
May 01 10:58:02 Tesla kernel: Hardware name: System manufacturer System Product Name/STRIX Z270H GAMING, BIOS 0801 01/25/2017
May 01 10:58:02 Tesla kernel: Workqueue: events e1000_watchdog_task [e1000e]
May 01 10:58:02 Tesla kernel: Call Trace:
May 01 10:58:02 Tesla kernel:  <TASK>
May 01 10:58:02 Tesla kernel:  dump_stack_lvl+0x64/0x80
May 01 10:58:02 Tesla kernel:  __schedule_bug+0x56/0x70
May 01 10:58:02 Tesla kernel:  __schedule+0x10f0/0x1520
May 01 10:58:02 Tesla kernel:  ? ttwu_do_activate+0x64/0x200
May 01 10:58:02 Tesla kernel:  schedule+0x32/0xd0
May 01 10:58:02 Tesla kernel:  schedule_hrtimeout_range_clock+0xbe/0x140
May 01 10:58:02 Tesla kernel:  ? __pfx_hrtimer_wakeup+0x10/0x10
May 01 10:58:02 Tesla kernel:  usleep_range_state+0x64/0x90
May 01 10:58:02 Tesla kernel:  e1000e_read_phy_reg_mdic+0x87/0x280 [e1000e 151c2b7d541fc38ecc5e1e1d2bd1b47019bd5d3b]
May 01 10:58:02 Tesla kernel:  e1000e_update_stats+0x513/0x730 [e1000e 151c2b7d541fc38ecc5e1e1d2bd1b47019bd5d3b]
May 01 10:58:02 Tesla kernel:  e1000_watchdog_task+0xe7/0xab0 [e1000e 151c2b7d541fc38ecc5e1e1d2bd1b47019bd5d3b]
May 01 10:58:02 Tesla kernel:  process_one_work+0x17b/0x350
May 01 10:58:02 Tesla kernel:  worker_thread+0x30f/0x450
May 01 10:58:02 Tesla kernel:  ? __pfx_worker_thread+0x10/0x10
May 01 10:58:02 Tesla kernel:  kthread+0xe8/0x120
May 01 10:58:02 Tesla kernel:  ? __pfx_kthread+0x10/0x10
May 01 10:58:02 Tesla kernel:  ret_from_fork+0x34/0x50
May 01 10:58:02 Tesla kernel:  ? __pfx_kthread+0x10/0x10
May 01 10:58:02 Tesla kernel:  ret_from_fork_asm+0x1b/0x30
May 01 10:58:02 Tesla kernel:  </TASK>

which is most likely https://bbs.archlinux.org/viewtopic.php?id=294970

Offline

#5 2024-05-01 15:26:46

maximiliano
Member
Registered: 2013-04-16
Posts: 27

Re: [SOLVED] DE froozen after SDDM

seth wrote:

You've a static hostname and it gets set early and doesn't change.
The kernel dumps

May 01 10:58:02 Tesla NetworkManager[594]: <info>  [1714571882.2470] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May 01 10:58:02 Tesla kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 100 Mbps Half Duplex, Flow Control: None
May 01 10:58:02 Tesla kernel: BUG: scheduling while atomic: kworker/1:0/27/0x00000002
May 01 10:58:02 Tesla kernel: Modules linked in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nft_masq uinput nft_chain_nat nf_tables nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc cmac algif_hash algif_skcipher af_alg bnep intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common psmouse serio_raw iTCO_wdt intel_tcc_cooling atkbd intel_pmc_bxt libps2 x86_pkg_temp_thermal vivaldi_fmap intel_powerclamp ee1004 crct10dif_pclmul crc32_pclmul iTCO_vendor_support polyval_clmulni mei_hdcp mei_pxp polyval_generic gf128mul snd_soc_avs ghash_clmulni_intel snd_soc_hda_codec sha512_ssse3 snd_hda_ext_core btusb sha256_ssse3 uvcvideo btrtl sha1_ssse3 videobuf2_vmalloc btintel aesni_intel snd_usb_audio snd_soc_core uvc videobuf2_memops btbcm crypto_simd snd_compress eeepc_wmi snd_usbmidi_lib videobuf2_v4l2 btmtk ac97_bus
May 01 10:58:02 Tesla kernel:  snd_hda_codec_realtek asus_wmi snd_pcm_dmaengine snd_ump snd_hda_codec_generic snd_hda_codec_hdmi cryptd videodev snd_rawmidi ledtrig_audio snd_hda_intel bluetooth platform_profile videobuf2_common snd_intel_dspcfg snd_seq_device rapl i8042 snd_intel_sdw_acpi e1000e mc mousedev joydev ecdh_generic sparse_keymap intel_cstate snd_hda_codec serio snd_hda_core ptp i2c_i801 intel_uncore pps_core rfkill wmi_bmof pcspkr mxm_wmi i2c_smbus snd_hwdep intel_pmc_core mei_me intel_vsec mei pmt_telemetry acpi_pad pmt_class mac_hid vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) nct6775 nct6775_core hwmon_vid snd_aloop snd_pcm snd_timer snd soundcore coretemp i2c_dev crypto_user loop dm_mod nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid amdgpu amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec gpu_sched drm_suballoc_helper nvme drm_buddy crc32c_intel nvme_core drm_display_helper xhci_pci nvme_auth cec xhci_pci_renesas video wmi
May 01 10:58:02 Tesla kernel: CPU: 1 PID: 27 Comm: kworker/1:0 Tainted: G           OE      6.8.8-arch1-1 #1 6e5d9eb17edb3e2ef7f1d13e0aec4b6c1833b648
May 01 10:58:02 Tesla kernel: Hardware name: System manufacturer System Product Name/STRIX Z270H GAMING, BIOS 0801 01/25/2017
May 01 10:58:02 Tesla kernel: Workqueue: events e1000_watchdog_task [e1000e]
May 01 10:58:02 Tesla kernel: Call Trace:
May 01 10:58:02 Tesla kernel:  <TASK>
May 01 10:58:02 Tesla kernel:  dump_stack_lvl+0x64/0x80
May 01 10:58:02 Tesla kernel:  __schedule_bug+0x56/0x70
May 01 10:58:02 Tesla kernel:  __schedule+0x10f0/0x1520
May 01 10:58:02 Tesla kernel:  ? ttwu_do_activate+0x64/0x200
May 01 10:58:02 Tesla kernel:  schedule+0x32/0xd0
May 01 10:58:02 Tesla kernel:  schedule_hrtimeout_range_clock+0xbe/0x140
May 01 10:58:02 Tesla kernel:  ? __pfx_hrtimer_wakeup+0x10/0x10
May 01 10:58:02 Tesla kernel:  usleep_range_state+0x64/0x90
May 01 10:58:02 Tesla kernel:  e1000e_read_phy_reg_mdic+0x87/0x280 [e1000e 151c2b7d541fc38ecc5e1e1d2bd1b47019bd5d3b]
May 01 10:58:02 Tesla kernel:  e1000e_update_stats+0x513/0x730 [e1000e 151c2b7d541fc38ecc5e1e1d2bd1b47019bd5d3b]
May 01 10:58:02 Tesla kernel:  e1000_watchdog_task+0xe7/0xab0 [e1000e 151c2b7d541fc38ecc5e1e1d2bd1b47019bd5d3b]
May 01 10:58:02 Tesla kernel:  process_one_work+0x17b/0x350
May 01 10:58:02 Tesla kernel:  worker_thread+0x30f/0x450
May 01 10:58:02 Tesla kernel:  ? __pfx_worker_thread+0x10/0x10
May 01 10:58:02 Tesla kernel:  kthread+0xe8/0x120
May 01 10:58:02 Tesla kernel:  ? __pfx_kthread+0x10/0x10
May 01 10:58:02 Tesla kernel:  ret_from_fork+0x34/0x50
May 01 10:58:02 Tesla kernel:  ? __pfx_kthread+0x10/0x10
May 01 10:58:02 Tesla kernel:  ret_from_fork_asm+0x1b/0x30
May 01 10:58:02 Tesla kernel:  </TASK>

which is most likely https://bbs.archlinux.org/viewtopic.php?id=294970


Thanks again Seth!, I have my

 /etc/bluetooth/main.conf 

with the

 Autoenable=true 

commented, will try using it as "false" and will back to you.

Offline

#6 2024-05-01 15:35:24

maximiliano
Member
Registered: 2013-04-16
Posts: 27

Re: [SOLVED] DE froozen after SDDM

Something I noticed there are 2 files

[root@Tesla /]# ls -ltr etc/bluetooth/
total 24
-rw-r--r-- 1 root root  8890 Aug 26  2021 main.conf.pacnew
-rw-r--r-- 1 root root 11147 May  1 12:29 main.conf

The one that I think is active ( I set that to false, it was commented )

[root@Tesla /]# cat etc/bluetooth/main.conf | grep AutoEnable -B3
# set of intervals the last interval is repeated until the last attempt.
#ReconnectIntervals=1,2,4,8,16,32,64

# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'true'.
AutoEnable=false

And the other one

[root@Tesla /]# cat etc/bluetooth/main.conf.pacnew | grep AutoEnable -B3
# set of intervals the last interval is repeated until the last attempt.
#ReconnectIntervals=1,2,4,8,16,32,64

# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'false'.
#AutoEnable=false

So looks like the correct option is set that to false right ?

Offline

#7 2024-05-01 15:41:40

seth
Member
Registered: 2012-09-03
Posts: 52,477

Re: [SOLVED] DE froozen after SDDM

The bluetooth config might be a red herring, see the linked https://bugzilla.kernel.org/show_bug.cgi?id=218740
Your config files are probably equivalent, the "old" main.conf explicitly sets AutoEnable=false while the new one implicitly does so.

You maybe still want to pacdiff the file, but I don't think this is relevant here.

Offline

#8 2024-05-01 17:53:29

maximiliano
Member
Registered: 2013-04-16
Posts: 27

Re: [SOLVED] DE froozen after SDDM

seth wrote:

The bluetooth config might be a red herring, see the linked https://bugzilla.kernel.org/show_bug.cgi?id=218740
Your config files are probably equivalent, the "old" main.conf explicitly sets AutoEnable=false while the new one implicitly does so.

You maybe still want to pacdiff the file, but I don't think this is relevant here.

Thanks! Using the

 AutoEnable=false 

made mi I3 to be accesible again, but I can do anything absolutelly weird, the OS hangs trying to configure the network I think, I disabled the bluetooth systemd unit.

I created a new journal file http://0x0.st/XXcG.txt

Offline

#9 2024-05-01 18:13:28

maximiliano
Member
Registered: 2013-04-16
Posts: 27

Re: [SOLVED] DE froozen after SDDM

Also I have the pacman log from that day http://0x0.st/XXcF.txt maybe should I try to downgrade linux-firmware package ?

Offline

#10 2024-05-01 18:26:42

maximiliano
Member
Registered: 2013-04-16
Posts: 27

Re: [SOLVED] DE froozen after SDDM

I did a downgrade of the linux package using the

 downgrade 

tool, and now I'm on my main installation posting this, absolutely weird.

[2024-05-01T15:17:58-0300] [PACMAN] Running 'pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.8.1.arch1-1-x86_64.pkg.tar.zst'
[2024-05-01T15:19:00-0300] [ALPM] running '60-mkinitcpio-remove.hook'...
[2024-05-01T15:19:00-0300] [ALPM] transaction started
[2024-05-01T15:19:01-0300] [ALPM] downgraded linux (6.8.8.arch1-1 -> 6.8.1.arch1-1)
[2024-05-01T15:19:02-0300] [ALPM] transaction completed
[2024-05-01T15:19:02-0300] [ALPM] running '30-systemd-update.hook'...
[2024-05-01T15:19:02-0300] [ALPM] running '60-depmod.hook'...
[2024-05-01T15:19:03-0300] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET] ==> Starting build: '6.8.1-arch1-1'
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-05-01T15:19:04-0300] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-05-01T15:19:06-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET] ==> Starting build: '6.8.1-arch1-1'
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-05-01T15:19:07-0300] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-05-01T15:19:08-0300] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2024-05-01T15:19:08-0300] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-05-01T15:19:08-0300] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-05-01T15:19:09-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'ast'
[2024-05-01T15:19:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-05-01T15:19:12-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-05-01T15:19:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-05-01T15:19:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2024-05-01T15:19:12-0300] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-05-01T15:19:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-05-01T15:19:13-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'wd719x'
[2024-05-01T15:19:13-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
[2024-05-01T15:19:13-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
[2024-05-01T15:19:13-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
[2024-05-01T15:19:13-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
[2024-05-01T15:19:13-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'aic94xx'
[2024-05-01T15:19:14-0300] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-05-01T15:19:14-0300] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-05-01T15:19:16-0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-05-01T15:19:16-0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
[2024-05-01T15:19:17-0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful

Offline

#11 2024-05-01 20:24:02

seth
Member
Registered: 2012-09-03
Posts: 52,477

Re: [SOLVED] DE froozen after SDDM

Please don't bump - edit your previous thread if nobody has yet replied.
The journal in #8 somewhat expectably shows the e1000e bug, downgrading to 6.8.1 prevents the problem because the bug was introduced w/ 6.8.5
There's actually a 2nd active thread on this, https://bbs.archlinux.org/viewtopic.php?id=294828

Offline

#12 2024-05-02 13:30:53

maximiliano
Member
Registered: 2013-04-16
Posts: 27

Re: [SOLVED] DE froozen after SDDM

seth wrote:

Please don't bump - edit your previous thread if nobody has yet replied.
The journal in #8 somewhat expectably shows the e1000e bug, downgrading to 6.8.1 prevents the problem because the bug was introduced w/ 6.8.5
There's actually a 2nd active thread on this, https://bbs.archlinux.org/viewtopic.php?id=294828

Thanks Seth! I'll consider this fixed, will keep in touch on the thread you mentioned.

Offline

Board footer

Powered by FluxBB