[SOLVED] SDDM black screen after login (wayland)

MrQuest · 2023-03-27 14:31:06

Hi!

I had installed Hyprland and it was working fine. Couple of days ago this problem started. SDDM opens with password prompt, I put my password, log in, and then it blinks to black screen and nothing happens. I did had installed KDE, Cinnamon and Gnome as well. I have also tried to launch them without any luck.

Currently I am launching Hyprland just by opening another TTY, loggin in in terminal and launching hyprland manually.

I have examined journalctl output, but nothing stands out, really hope on help here.

Here's journalctl output:

Mar 27 17:10:02 myhost sddm-helper[1657]: [PAM] Starting...
Mar 27 17:10:02 myhost sddm-helper[1657]: [PAM] Authenticating...
Mar 27 17:10:02 myhost dbus-daemon[821]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.24' (uid=0 pid>
Mar 27 17:10:02 myhost dbus-daemon[821]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 27 17:10:02 myhost sddm-helper[1657]: pam_systemd_home(sddm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 27 17:10:02 myhost sddm-helper[1657]: [PAM] Preparing to converse...
Mar 27 17:10:02 myhost sddm-helper[1657]: [PAM] Conversation with 1 messages
Mar 27 17:10:02 myhost sddm-helper[1657]: gkr-pam: unable to locate daemon control file
Mar 27 17:10:02 myhost sddm-helper[1657]: gkr-pam: stashed password to try later in open session
Mar 27 17:10:02 myhost sddm-helper[1657]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Mar 27 17:10:02 myhost sddm-helper[1657]: [PAM] returning.
Mar 27 17:10:02 myhost sddm[937]: Authentication for user  "user42"  successful
Mar 27 17:10:02 myhost sddm-helper[1657]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 27 17:10:02 myhost sddm-greeter[1099]: Message received from daemon: LoginSucceeded
Mar 27 17:10:02 myhost sddm-helper[1657]: pam_unix(sddm:session): session opened for user user42(uid=1000) by (uid=0)
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0290] policy: auto-activating connection 'Jumpgate' (dcc4cb6e-a59e-44d1-8da3-b7d1b12f8218)
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0294] device (wlp3s0): Activation: starting connection 'Jumpgate' (dcc4cb6e-a59e-44d1-8da3-b7d1b12f8218)
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0295] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0296] manager: NetworkManager state is now CONNECTING
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0298] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0301] device (wlp3s0): Activation: (wifi) access point 'Jumpgate' has security, but secrets are required.
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0301] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mar 27 17:10:02 myhost NetworkManager[837]: <warn>  [1679926202.0303] device (wlp3s0): no secrets: No agents were available for this request.
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0304] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0305] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 27 17:10:02 myhost NetworkManager[837]: <warn>  [1679926202.0307] device (wlp3s0): Activation: failed for connection 'Jumpgate'
Mar 27 17:10:02 myhost systemd[1]: Created slice User Slice of UID 1000.
Mar 27 17:10:02 myhost NetworkManager[837]: <info>  [1679926202.0313] device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 27 17:10:02 myhost sddm-helper[1081]: [PAM] Closing session
Mar 27 17:10:02 myhost sddm-helper[1081]: pam_unix(sddm-greeter:session): session closed for user sddm
Mar 27 17:10:02 myhost systemd[1]: Starting User Runtime Directory /run/user/1000...
Mar 27 17:10:02 myhost systemd-logind[824]: New session 2 of user user42.
Mar 27 17:10:02 myhost sddm-helper[1081]: [PAM] Ended.
Mar 27 17:10:02 myhost sddm[937]: Auth: sddm-helper exited successfully
Mar 27 17:10:02 myhost sddm[937]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Mar 27 17:10:02 myhost systemd[1]: Finished User Runtime Directory /run/user/1000.
Mar 27 17:10:02 myhost systemd[1]: session-c1.scope: Deactivated successfully.
Mar 27 17:10:02 myhost systemd-logind[824]: Session c1 logged out. Waiting for processes to exit.
Mar 27 17:10:02 myhost systemd[1]: Starting User Manager for UID 1000...
Mar 27 17:10:02 myhost systemd-logind[824]: Removed session c1.
Mar 27 17:10:02 myhost dbus-daemon[821]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.27' (uid=0 pid>
Mar 27 17:10:02 myhost dbus-daemon[821]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 27 17:10:02 myhost (systemd)[1665]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 27 17:10:02 myhost (systemd)[1665]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[user42] ruser=[<unknown>] rh>
Mar 27 17:10:02 myhost (systemd)[1665]: pam_unix(systemd-user:session): session opened for user user42(uid=1000) by (uid=0)
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: /home/user42/.config/autostart/Findex.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: /home/user42/.config/autostart/Picom startup.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignorin>
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: /etc/xdg/autostart/org.kde.plasma-welcome.desktop:93: Unknown key name 'SingleMainWindow' in section 'Desktop Entry', igno>
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: /etc/xdg/autostart/Fortivpn.desktop: stat() failed, ignoring: No such file or directory
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: Exec binary '/usr/bin/teams' does not exist: No such file or directory
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: /home/user42/.config/autostart/teams.desktop: not generating unit, error parsing Exec= line: No such file or directory
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: Exec binary 'kgpg' does not exist: No such file or directory
Mar 27 17:10:02 myhost systemd-xdg-autostart-generator[1675]: /home/user42/.config/autostart/org.kde.kgpg.desktop: not generating unit, error parsing Exec= line: No such file or di>
Mar 27 17:10:02 myhost systemd[1665]: Queued start job for default target Main User Target.
Mar 27 17:10:02 myhost systemd[1665]: Created slice User Application Slice.
Mar 27 17:10:02 myhost systemd[1665]: Reached target Paths.
Mar 27 17:10:02 myhost systemd[1665]: Reached target Timers.
Mar 27 17:10:02 myhost systemd[1665]: Starting D-Bus User Message Bus Socket...
Mar 27 17:10:02 myhost systemd[1665]: Listening on GnuPG network certificate management daemon.
Mar 27 17:10:02 myhost systemd[1665]: Listening on GCR ssh-agent wrapper.
Mar 27 17:10:02 myhost systemd[1665]: Listening on GNOME Keyring daemon.
Mar 27 17:10:02 myhost systemd[1665]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 27 17:10:02 myhost systemd[1665]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 27 17:10:02 myhost systemd[1665]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 27 17:10:02 myhost systemd[1665]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 27 17:10:02 myhost systemd[1665]: Listening on p11-kit server.
Mar 27 17:10:02 myhost systemd[1665]: Listening on PipeWire Multimedia System Socket.
Mar 27 17:10:02 myhost systemd[1665]: Listening on Sound System.
Mar 27 17:10:02 myhost systemd[1665]: Listening on D-Bus User Message Bus Socket.
Mar 27 17:10:02 myhost systemd[1665]: Reached target Sockets.
Mar 27 17:10:02 myhost systemd[1665]: Reached target Basic System.
Mar 27 17:10:02 myhost systemd[1]: Started User Manager for UID 1000.
Mar 27 17:10:02 myhost systemd[1665]: Starting Update XDG user dir configuration...
Mar 27 17:10:02 myhost systemd[1]: Started Session 2 of User user42.
Mar 27 17:10:02 myhost systemd[1665]: Started GNOME Keyring daemon.
Mar 27 17:10:02 myhost systemd[1665]: Finished Update XDG user dir configuration.
Mar 27 17:10:02 myhost systemd[1665]: Reached target Main User Target.
Mar 27 17:10:02 myhost systemd[1665]: Startup finished in 192ms.
Mar 27 17:10:02 myhost gnome-keyring-daemon[1679]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Mar 27 17:10:02 myhost systemd[1665]: Created slice User Core Session Slice.
Mar 27 17:10:02 myhost systemd[1665]: Starting D-Bus User Message Bus...
Mar 27 17:10:02 myhost systemd[1665]: Started D-Bus User Message Bus.
Mar 27 17:10:02 myhost sddm-helper[1657]: gkr-pam: the password for the login keyring was invalid.
Mar 27 17:10:02 myhost sddm-helper[1657]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Mar 27 17:10:02 myhost sddm-helper[1687]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Mar 27 17:10:02 myhost sddm-helper[1657]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "Hyprland"
Mar 27 17:10:02 myhost sddm-helper[1690]: Jumping to VT 1
Mar 27 17:10:02 myhost sddm-helper[1690]: VT mode didn't need to be fixed
Mar 27 17:10:03 myhost sddm[937]: Session started true
Mar 27 17:10:03 myhost sddm-helper[1657]: [PAM] Closing session
Mar 27 17:10:03 myhost sddm-helper[1657]: pam_unix(sddm:session): session closed for user user42
Mar 27 17:10:03 myhost sddm-helper[1657]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Mar 27 17:10:03 myhost sddm-helper[1657]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 27 17:10:03 myhost sddm-helper[1657]: [PAM] Ended.
Mar 27 17:10:03 myhost sddm[937]: Auth: sddm-helper exited with 1
Mar 27 17:10:03 myhost systemd-logind[824]: Session 2 logged out. Waiting for processes to exit.
Mar 27 17:10:04 myhost kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
Mar 27 17:10:12 myhost systemd[1]: Stopping User Manager for UID 964...
Mar 27 17:10:12 myhost systemd[1086]: Activating special unit Exit the Session...
Mar 27 17:10:12 myhost systemd[1086]: Stopped target Main User Target.
Mar 27 17:10:12 myhost systemd[1086]: Stopping D-Bus User Message Bus...
Mar 27 17:10:12 myhost systemd[1086]: Stopped D-Bus User Message Bus.
Mar 27 17:10:12 myhost systemd[1086]: Removed slice User Core Session Slice.
Mar 27 17:10:12 myhost systemd[1086]: Stopped target Basic System.
Mar 27 17:10:12 myhost systemd[1086]: Stopped target Paths.
Mar 27 17:10:12 myhost systemd[1086]: Stopped target Sockets.
Mar 27 17:10:12 myhost systemd[1086]: Stopped target Timers.
Mar 27 17:10:12 myhost systemd[1086]: Closed D-Bus User Message Bus Socket.
Mar 27 17:10:12 myhost systemd[1086]: Closed GnuPG network certificate management daemon.
Mar 27 17:10:12 myhost systemd[1086]: Closed GCR ssh-agent wrapper.
Mar 27 17:10:12 myhost systemd[1086]: Closed GNOME Keyring daemon.
Mar 27 17:10:12 myhost systemd[1086]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 27 17:10:12 myhost systemd[1086]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 27 17:10:12 myhost systemd[1086]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 27 17:10:12 myhost systemd[1086]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 27 17:10:12 myhost systemd[1086]: Closed p11-kit server.
Mar 27 17:10:12 myhost systemd[1086]: Closed PipeWire Multimedia System Socket.
Mar 27 17:10:12 myhost systemd[1086]: Closed Sound System.
Mar 27 17:10:12 myhost systemd[1086]: Removed slice User Application Slice.
Mar 27 17:10:12 myhost systemd[1086]: Reached target Shutdown.
Mar 27 17:10:12 myhost systemd[1086]: Finished Exit the Session.
Mar 27 17:10:12 myhost systemd[1086]: Reached target Exit the Session.
Mar 27 17:10:12 myhost (sd-pam)[1090]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<u>
Mar 27 17:10:12 myhost systemd[1]: user@964.service: Deactivated successfully.
Mar 27 17:10:12 myhost systemd[1]: Stopped User Manager for UID 964.
Mar 27 17:10:12 myhost systemd[1]: Stopping User Runtime Directory /run/user/964...
Mar 27 17:10:12 myhost systemd[1]: run-user-964.mount: Deactivated successfully.
Mar 27 17:10:12 myhost systemd[1]: user-runtime-dir@964.service: Deactivated successfully.
Mar 27 17:10:12 myhost systemd[1]: Stopped User Runtime Directory /run/user/964.
Mar 27 17:10:12 myhost systemd[1]: Removed slice User Slice of UID 964.
Mar 27 17:10:45 myhost systemd[1]: Started Getty on tty3.

Let me know if any additional information is needed. I am working on Lenovo ThinkPad E14 G3 (AMD) running ArcoLinux.

Last edited by MrQuest (2023-03-27 18:27:12)

MrQuest · 2023-03-27 18:26:53

Oh my god.. like, fore real, O.M.G..

As a guy, who would, probably, use journalctl as primary source of investigation you would look through back and forth trying to solve this.

But there are no traces of what's happening at all, because here is how I fixed it.

At some webpage I have found that there could be a log file

~/.local/share/sddm/wayland-session.log

Inside that log file I have found that I had something like this:

path not found in ~/.profile like 27

. Turned out in this file I had command that was issued on missing file, and instead of ignoring it it just broke everything. I removed that line (since I clearly didn't needed it) and everything started to work!

Arch Linux

#1 2023-03-27 14:31:06

[SOLVED] SDDM black screen after login (wayland)

#2 2023-03-27 18:26:53

Re: [SOLVED] SDDM black screen after login (wayland)

Board footer