You are not logged in.
- Topics: Active | Unanswered
#1 2024-05-13 18:51:06
- brentward
- Member
- Registered: 2024-05-13
- Posts: 4
[SOLVED] KDE Plasma using sddm goes to black screen on logon
When I try to log into plasma using sddm I get a black screen, no mouse cursor is visible but my mouse works and I can launch apps using the screen corner.
If I use gdm I can launch plasma.
I'm trying to launch into Wayland but X11 doesn't work either.
I'm using the linux-zen kernel and an Nvidia gpu and I have gone through the Nvidia setup in the wiki including setting the kernel parameters with nvidia_drm.modeset=1 and nvidia_drm.fbdev=1.
This started happening about a week ago right before I was planning to reinstall Arch. I did a reinstall thinking it was a configuration issue, but the issue is happening with a fresh install. As a result I'm not sure what was updated when this started.
I've read through recent similar forum posts when people switched to Plasma 6, but I couldn't resolve it using that info.
Examining journalctl it seems that xdg-desktop-portal.service is crashing and failing to start.
May 13 10:50:02 brents-arch systemd-coredump[1079]: Process 905 (xdg-desktop-por) of user 1000 dumped core.
Stack trace of thread 905:
#0 0x000077683361bad8 g_log_structured_array (libglib-2.0.so.0 + 0x61ad8)
#1 0x000077683361bdd7 g_log_default_handler (libglib-2.0.so.0 + 0x61dd7)
#2 0x000077683361c05c g_logv (libglib-2.0.so.0 + 0x6205c)
#3 0x000077683361c3d4 g_log (libglib-2.0.so.0 + 0x623d4)
#4 0x00007768334d9db4 n/a (libgio-2.0.so.0 + 0xecdb4)
#5 0x00007768333b0bab n/a (libgobject-2.0.so.0 + 0x22bab)
#6 0x00007768333b15d8 n/a (libgobject-2.0.so.0 + 0x235d8)
#7 0x00007768333b36cb g_object_new_valist (libgobject-2.0.so.0 + 0x256cb)
#8 0x00007768333b3a80 g_object_new (libgobject-2.0.so.0 + 0x25a80)
#9 0x0000776832b4e30e n/a (libgiognomeproxy.so + 0x230e)
#10 0x00007768333cc2b9 g_type_create_instance (libgobject-2.0.so.0 + 0x3e2b9)
#11 0x00007768333b14a5 n/a (libgobject-2.0.so.0 + 0x234a5)
#12 0x00007768333b2ac7 g_object_new_with_properties (libgobject-2.0.so.0 + 0x24ac7)
#13 0x00007768333b3aa2 g_object_new (libgobject-2.0.so.0 + 0x25aa2)
#14 0x000077683345fcad n/a (libgio-2.0.so.0 + 0x72cad)
#15 0x0000776833465a0e n/a (libgio-2.0.so.0 + 0x78a0e)
#16 0x0000776833474a8a g_proxy_resolver_get_default (libgio-2.0.so.0 + 0x87a8a)
#17 0x0000636dc610175e n/a (xdg-desktop-portal + 0x6375e)
#18 0x00007768333cc2b9 g_type_create_instance (libgobject-2.0.so.0 + 0x3e2b9)
#19 0x00007768333b14a5 n/a (libgobject-2.0.so.0 + 0x234a5)
#20 0x00007768333b2ac7 g_object_new_with_properties (libgobject-2.0.so.0 + 0x24ac7)
#21 0x00007768333b3aa2 g_object_new (libgobject-2.0.so.0 + 0x25aa2)
#22 0x0000636dc6112b77 n/a (xdg-desktop-portal + 0x74b77)
#23 0x00007768334fe655 n/a (libgio-2.0.so.0 + 0x111655)
#24 0x00007768334930ec n/a (libgio-2.0.so.0 + 0xa60ec)
#25 0x0000776833497385 n/a (libgio-2.0.so.0 + 0xaa385)
#26 0x00007768334f968b n/a (libgio-2.0.so.0 + 0x10c68b)
#27 0x00007768334930ec n/a (libgio-2.0.so.0 + 0xa60ec)
#28 0x0000776833493135 n/a (libgio-2.0.so.0 + 0xa6135)
#29 0x0000776833616a89 n/a (libglib-2.0.so.0 + 0x5ca89)
#30 0x00007768336789b7 n/a (libglib-2.0.so.0 + 0xbe9b7)
#31 0x0000776833617787 g_main_loop_run (libglib-2.0.so.0 + 0x5d787)
#32 0x0000636dc60af2f7 n/a (xdg-desktop-portal + 0x112f7)
#33 0x0000776832fd9c88 n/a (libc.so.6 + 0x25c88)
#34 0x0000776832fd9d4c __libc_start_main (libc.so.6 + 0x25d4c)
#35 0x0000636dc60af8e5 n/a (xdg-desktop-portal + 0x118e5)
Stack trace of thread 909:
#0 0x00007768330c7e9d syscall (libc.so.6 + 0x113e9d)
#1 0x00007768336719e0 g_cond_wait (libglib-2.0.so.0 + 0xb79e0)
#2 0x00007768335df8dc n/a (libglib-2.0.so.0 + 0x258dc)
#3 0x000077683364b687 n/a (libglib-2.0.so.0 + 0x91687)
#4 0x0000776833646236 n/a (libglib-2.0.so.0 + 0x8c236)
#5 0x0000776833046ded n/a (libc.so.6 + 0x92ded)
#6 0x00007768330ca0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 910:
#0 0x00007768330bc39d __poll (libc.so.6 + 0x10839d)
#1 0x00007768336788fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x0000776833617787 g_main_loop_run (libglib-2.0.so.0 + 0x5d787)
#3 0x00007768334ff4a4 n/a (libgio-2.0.so.0 + 0x1124a4)
#4 0x0000776833646236 n/a (libglib-2.0.so.0 + 0x8c236)
#5 0x0000776833046ded n/a (libc.so.6 + 0x92ded)
#6 0x00007768330ca0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 911:
#0 0x00007768330c7e9d syscall (libc.so.6 + 0x113e9d)
#1 0x0000776833672337 g_cond_wait_until (libglib-2.0.so.0 + 0xb8337)
#2 0x00007768335df8a5 n/a (libglib-2.0.so.0 + 0x258a5)
#3 0x000077683364c24b n/a (libglib-2.0.so.0 + 0x9224b)
#4 0x0000776833646236 n/a (libglib-2.0.so.0 + 0x8c236)
#5 0x0000776833046ded n/a (libc.so.6 + 0x92ded)
#6 0x00007768330ca0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1071:
#0 0x00007768330c7e9d syscall (libc.so.6 + 0x113e9d)
#1 0x0000776833672337 g_cond_wait_until (libglib-2.0.so.0 + 0xb8337)
#2 0x00007768335df8a5 n/a (libglib-2.0.so.0 + 0x258a5)
#3 0x000077683364c24b n/a (libglib-2.0.so.0 + 0x9224b)
#4 0x0000776833646236 n/a (libglib-2.0.so.0 + 0x8c236)
#5 0x0000776833046ded n/a (libc.so.6 + 0x92ded)
#6 0x00007768330ca0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 908:
#0 0x00007768330bc39d __poll (libc.so.6 + 0x10839d)
#1 0x00007768336788fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x0000776833615f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x0000776833615fea n/a (libglib-2.0.so.0 + 0x5bfea)
#4 0x0000776833646236 n/a (libglib-2.0.so.0 + 0x8c236)
#5 0x0000776833046ded n/a (libc.so.6 + 0x92ded)
#6 0x00007768330ca0dc n/a (libc.so.6 + 0x1160dc)
ELF object binary architecture: AMD x86-64Last edited by brentward (2024-05-14 07:24:39)
Offline
#2 2024-05-13 19:42:14
- brentward
- Member
- Registered: 2024-05-13
- Posts: 4
Re: [SOLVED] KDE Plasma using sddm goes to black screen on logon
Here is the output of journalctl -b for the boot in question:
http://0x0.st/XKvo.log
Any other logs that would be helpful?
Offline
#3 2024-05-13 22:22:02
- seth
- Member
- Registered: 2012-09-03
- Posts: 56,993
Re: [SOLVED] KDE Plasma using sddm goes to black screen on logon
There's way more stuff broken…
May 13 10:50:02 brents-arch kwin_wayland[898]: kwin_core: Failed to load cursor theme "breeze_cursors"
May 13 10:50:02 brents-arch kwin_wayland[898]: kwin_core: Failed to load cursor theme "default"
May 13 10:50:02 brents-arch kwin_wayland[898]: kwin_core: Unable to load any cursor theme
…
May 13 10:50:02 brents-arch systemd[853]: plasma-ksplash.service: Failed with result 'exit-code'.
May 13 10:50:02 brents-arch systemd[853]: Failed to start Splash screen shown during boot.
…
May 13 10:50:02 brents-arch systemd[853]: at-spi-dbus-bus.service: Main process exited, code=dumped, status=5/TRAP
May 13 10:50:02 brents-arch systemd[853]: at-spi-dbus-bus.service: Failed with result 'core-dump'.
…
# xdg-desktop-portal-gtk
May 13 10:50:02 brents-arch systemd-coredump[1029]: Process 932 (xdg-desktop-por) of user 1000 dumped core.
Stack trace of thread 932:
#0 0x000075d6e64efad8 g_log_structured_array (libglib-2.0.so.0 + 0x61ad8)
#1 0x000075d6e64efdd7 g_log_default_handler (libglib-2.0.so.0 + 0x61dd7)
#2 0x000075d6e64f005c g_logv (libglib-2.0.so.0 + 0x6205c)
…
# xdg-desktop-portal
May 13 10:50:02 brents-arch systemd-coredump[1079]: Process 905 (xdg-desktop-por) of user 1000 dumped core.
Stack trace of thread 905:
#0 0x000077683361bad8 g_log_structured_array (libglib-2.0.so.0 + 0x61ad8)
#1 0x000077683361bdd7 g_log_default_handler (libglib-2.0.so.0 + 0x61dd7)
#2 0x000077683361c05c g_logv (libglib-2.0.so.0 + 0x6205c)
#3 0x000077683361c3d4 g_log (libglib-2.0.so.0 + 0x623d4)
…
May 13 10:50:02 brents-arch systemd[853]: plasma-plasmashell.service: Failed with result 'exit-code'.
May 13 10:50:02 brents-arch systemd[853]: Failed to start KDE Plasma Workspace.… and I'd first and foremost look at
pacman -Qikk glib2Offline
#4 2024-05-13 22:37:25
- brentward
- Member
- Registered: 2024-05-13
- Posts: 4
Re: [SOLVED] KDE Plasma using sddm goes to black screen on logon
I reinstalled my system because there were lots of packages I installed trying to get to a usable state, so I've created a new journtalctl -b log:
http://0x0.st/XKwy.txt
Here is the output of pacman -Qikk glib2:
http://0x0.st/XKwv.txt
For further context, I can start plasma through startplasma-wayland and so far from what I can tell it seems to be working normally.
Offline
#5 2024-05-14 06:35:26
- seth
- Member
- Registered: 2012-09-03
- Posts: 56,993
Re: [SOLVED] KDE Plasma using sddm goes to black screen on logon
May 13 15:25:34 brents-arch systemd-coredump[907]: Process 877 (xdg-desktop-por) of user 1000 dumped core.
Stack trace of thread 877:
#0 0x000074e953c3bad8 g_log_structured_array (libglib-2.0.so.0 + 0x61ad8)
#1 0x000074e953c3bdd7 g_log_default_handler (libglib-2.0.so.0 + 0x61dd7)
#2 0x000074e953c3c05c g_logv (libglib-2.0.so.0 + 0x6205c)
#3 0x000074e953c3c3d4 g_log (libglib-2.0.so.0 + 0x623d4)
#4 0x000074e953af9db4 n/a (libgio-2.0.so.0 + 0xecdb4)
#5 0x000074e9539d0bab n/a (libgobject-2.0.so.0 + 0x22bab)
#6 0x000074e9539d15d8 n/a (libgobject-2.0.so.0 + 0x235d8)
#7 0x000074e9539d36cb g_object_new_valist (libgobject-2.0.so.0 + 0x256cb)
#8 0x000074e9539d3a80 g_object_new (libgobject-2.0.so.0 + 0x25a80)
#9 0x000074e95316e30e n/a (libgiognomeproxy.so + 0x230e)
#10 0x000074e9539ec2b9 g_type_create_instance (libgobject-2.0.so.0 + 0x3e2b9)
#11 0x000074e9539d14a5 n/a (libgobject-2.0.so.0 + 0x234a5)
#12 0x000074e9539d2ac7 g_object_new_with_properties (libgobject-2.0.so.0 + 0x24ac7)
#13 0x000074e9539d3aa2 g_object_new (libgobject-2.0.so.0 + 0x25aa2)
#14 0x000074e953a7fcad n/a (libgio-2.0.so.0 + 0x72cad)
#15 0x000074e953a85a0e n/a (libgio-2.0.so.0 + 0x78a0e)
#16 0x000074e953a94a8a g_proxy_resolver_get_default (libgio-2.0.so.0 + 0x87a8a)
#17 0x00005bd44759275e n/a (xdg-desktop-portal + 0x6375e)
#18 0x000074e9539ec2b9 g_type_create_instance (libgobject-2.0.so.0 + 0x3e2b9)
#19 0x000074e9539d14a5 n/a (libgobject-2.0.so.0 + 0x234a5)
#20 0x000074e9539d2ac7 g_object_new_with_properties (libgobject-2.0.so.0 + 0x24ac7)
#21 0x000074e9539d3aa2 g_object_new (libgobject-2.0.so.0 + 0x25aa2)
#22 0x00005bd4475a3b77 n/a (xdg-desktop-portal + 0x74b77)
#23 0x000074e953b1e655 n/a (libgio-2.0.so.0 + 0x111655)
#24 0x000074e953ab30ec n/a (libgio-2.0.so.0 + 0xa60ec)
#25 0x000074e953ab7385 n/a (libgio-2.0.so.0 + 0xaa385)
#26 0x000074e953b1968b n/a (libgio-2.0.so.0 + 0x10c68b)
#27 0x000074e953ab30ec n/a (libgio-2.0.so.0 + 0xa60ec)
#28 0x000074e953ab3135 n/a (libgio-2.0.so.0 + 0xa6135)
#29 0x000074e953c36a89 n/a (libglib-2.0.so.0 + 0x5ca89)
#30 0x000074e953c989b7 n/a (libglib-2.0.so.0 + 0xbe9b7)
#31 0x000074e953c37787 g_main_loop_run (libglib-2.0.so.0 + 0x5d787)
#32 0x00005bd4475402f7 n/a (xdg-desktop-portal + 0x112f7)
#33 0x000074e9535f9c88 n/a (libc.so.6 + 0x25c88)
#34 0x000074e9535f9d4c __libc_start_main (libc.so.6 + 0x25d4c)
#35 0x00005bd4475408e5 n/a (xdg-desktop-portal + 0x118e5)keeps crashing, apparently when querying the resolver config through glib-networking.
I can start plasma through startplasma-wayland and so far from what I can tell it seems to be working normally.
log into plasma using sddm I get a black screen, no mouse cursor is visible but my mouse works and I can launch apps using the screen corner.
If I use gdm I can launch plasma.
I'm trying to launch into Wayland but X11 doesn't work either.
Do you get a mouse cursor on the X11 session?
Try to remove "nvidia_drm.fbdev=1"
You also still have
May 13 15:25:34 brents-arch kwin_wayland[868]: kwin_core: Failed to load cursor theme "breeze_cursors"
May 13 15:25:34 brents-arch kwin_wayland[868]: kwin_core: Failed to load cursor theme "default"
May 13 15:25:34 brents-arch kwin_wayland[868]: kwin_core: Unable to load any cursor theme
May 13 15:25:34 brents-arch wpa_supplicant[752]: wlp0s20f0u11: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-50 noise=9999 txrate=6500
May 13 15:25:34 brents-arch kcminit_startup[874]: Initializing "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
May 13 15:25:34 brents-arch kwin_wayland[868]: kf.plasma.core: Could not locate plasma theme "default" in plasma/desktoptheme/ using search path QList("/home/brent/.local/share", "/var/lib/flatpak/exports/share", "/home/brent/.local/share/flatpak/exports/share")
May 13 15:25:34 brents-arch kwin_wayland[868]: kf.plasma.core: Could not locate plasma theme "default" in plasma/desktoptheme/ using search path QList("/home/brent/.local/share", "/var/lib/flatpak/exports/share", "/home/brent/.local/share/flatpak/exports/share")
May 13 15:25:34 brents-arch ksplashqml[871]: org.kde.plasma.ksplashqml: Failed to resolve package url QUrl("") package.valid false package.path "" originalPackagePath "" packageName "org.kde.breezedark.desktop" theme "org.kde.breezedark.desktop"
May 13 15:25:34 brents-arch systemd[825]: plasma-ksplash.service: Main process exited, code=exited, status=1/FAILURE
May 13 15:25:34 brents-arch systemd[825]: plasma-ksplash.service: Failed with result 'exit-code'.
May 13 15:25:34 brents-arch systemd[825]: Failed to start Splash screen shown during boot.and one thing that's highly suspicious there is that it checks ~/.local and flatpak - does this also affect a fresh user account and do you have questionable™ stanzas in your shell config or /etc/profile* ?
Offline
#6 2024-05-14 07:23:52
- brentward
- Member
- Registered: 2024-05-13
- Posts: 4
Re: [SOLVED] KDE Plasma using sddm goes to black screen on logon
There was indeed something questionable in my .zshenv file. I tested a fresh user and the issue went away. Your mentioning of flatpak helped me find the offending line immediately and it is working now. Thanks!
Offline