| Summary: | Blank screen after login. Wayland only. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | gigastarcraft2 |
| Component: | Startup process | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde, nate, sadiyumusak |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
gigastarcraft2
2023-05-12 16:18:17 UTC
Can you attach /home/nate/.local/share/sddm.log? Er, with the correct file path, of course. :) Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! dbus-daemon[2975]: [session uid=1000 pid=2975] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=2976 comm="/usr/bin/startplasma-wayland") dbus-daemon[2975]: [session uid=1000 pid=2975] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.4' (uid=1000 pid=3000 comm="/usr/bin/ksplashqml") kdeinit5: preparing to launch '/usr/lib/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 3008, result = 0 dbus-daemon[2975]: [session uid=1000 pid=2975] Activating service name='org.freedesktop.portal.Documents' requested by ':1.5' (uid=1000 pid=3007 comm="/usr/lib/xdg-desktop-portal") dbus-daemon[2975]: [session uid=1000 pid=2975] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.6' (uid=1000 pid=3014 comm="/usr/lib/xdg-document-portal") dbus-daemon[2975]: [session uid=1000 pid=2975] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' dbus-daemon[2975]: [session uid=1000 pid=2975] Successfully activated service 'org.freedesktop.portal.Documents' dbus-daemon[2975]: [session uid=1000 pid=2975] Activating service name='org.freedesktop.impl.portal.desktop.gtk' requested by ':1.5' (uid=1000 pid=3007 comm="/usr/lib/xdg-desktop-portal") (kwin_wayland:2997): Gtk-WARNING **: 10:55:33.222: cannot open display: (kwin_wayland:3046): Gtk-WARNING **: 10:55:33.284: cannot open display: (kwin_wayland:3048): Gtk-WARNING **: 10:55:33.343: cannot open display: (kwin_wayland:3050): Gtk-WARNING **: 10:55:33.401: cannot open display: (kwin_wayland:3052): Gtk-WARNING **: 10:55:33.459: cannot open display: (kwin_wayland:3054): Gtk-WARNING **: 10:55:33.517: cannot open display: (kwin_wayland:3056): Gtk-WARNING **: 10:55:33.575: cannot open display: (kwin_wayland:3058): Gtk-WARNING **: 10:55:33.634: cannot open display: (kwin_wayland:3060): Gtk-WARNING **: 10:55:33.692: cannot open display: (kwin_wayland:3062): Gtk-WARNING **: 10:55:33.750: cannot open display: (kwin_wayland:3064): Gtk-WARNING **: 10:55:33.808: cannot open display: The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? kdeinit5: Communication error with launcher. Exiting! Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. Thanks! > The Wayland connection broke. Did the Wayland compositor die? If you run `coredumpctl --reverse`, do you see any kwin_wayland crashes there? If you do, can you follow the instructions in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to paste a backtrace of the crash? (In reply to Nate Graham from comment #5) > Thanks! > > > The Wayland connection broke. Did the Wayland compositor die? > If you run `coredumpctl --reverse`, do you see any kwin_wayland crashes > there? If you do, can you follow the instructions in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > to paste a backtrace of the crash? I am on OpenRC. Anyway I get blank screen and can't run this command when logging into Wayland session I can only run it in X11 environment. Ok, well then just get a backtrace of the kwin_wayland crash using whatever tools and methods work for your setup. I've been testing Wayland from time to time to see the progress for some time. Yesterday I've encountered the same problem, although no important change took place in my system configuration after the last successful login to Wayland session one or two weeks ago. When I create a new user, I can login to Wayland session, with nothing in "~/.local/share/wayland-session.log". Oddly, after logging out, I can see the same content in that file as in mine after Wayland login failure (see below). Disabling all startup apps and scripts had no effect. Adding the same desktop layout including the same third party widgets to the new user session didn't cause any problems either. ~/.local/share/wayland-session.log: =================================== Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. I get the same output from the following command: =========================================== export QT_LOGGING_RULES="kwin_*.debug=true" startplasma-wayland > ~/startplasma-wayland.log 2>&1 SOFTWARE/OS VERSIONS Operating System: Kdebian 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Sorry, I forgot to add that the command "XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland" or "dbus-run-session startplasma-wayland" does launch the wayland session for me as well, but produces the following terminal output: ============================================== dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 ' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1 requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.kde.KSplash' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland") dbus-daemon [7937]: [session uid=1000 pid=79371 Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service name='org.freedesktop.systemd1' requested by 1.3' (uid=1000 pid=7964 comm="/usr/bin/kwin_wayland_wrapper --xwayland") dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemdi' failed: Process org.freedesktop.systemdi exited with status 1 kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid=7977, result = 0 No backend specified, automatically choosing drm The Wayland connection broke. Did the Wayland compositor die?f0 "") unless they are emitted in the object's thread QThread (0x55ba74a45218 "libinput-connection"). Current thread is QThread(0x55ba749f1b70").handled with .catch(). To termina The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? Gdk-Message: 17:00:53.965: Lost connection to Wayland compositor. The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I'm afraid we still need a backtrace. (In reply to Nate Graham from comment #11) > I'm afraid we still need a backtrace. Sorry, can you tell me how to get that backtrace? I did in Comment 5. Sorry, it seems I was lost somewhere there - so I tried again to obtain a backtrace. 1. From SDDM, I was again pushed back immediately (sometimes seeing a black screen for a second, and/or hearing the login sound). 2. I then switched to terminal, and executed these commands: export QT_LOGGING_RULES="kwin_*.debug=true" startplasma-wayland > ~/startplasma-wayland.log 2>&1 The result was the same, with this output: Error: could not determine $DISPLAY. Error: Can not contact kdeinit5! org.kde.startup: "kdeinit5_shutdown" () exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. 3. There the command "coredumpctl --reverse" didn't return any results, but "sudo coredumpctl --reverse" did, but the list didn't include either "kwin" or "wayland". The closest thing I saw was "plasmashell". I can copy here the output of command "sudo coredump gdb <number> if it makes sense. The abbreviated list: /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/bin/gmenudbusmenuproxy /usr/bin/plasmashell /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/lib/insync/insync /usr/bin/gmenudbusmenuproxy /usr/bin/xembedsniproxy /usr/bin/plasmashell /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/bin/gmenudbusmenuproxy /usr/bin/python3.11 /usr/bin/gmenudbusmenuproxy /usr/bin/plasmashell /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil /usr/bin/xembedsniproxy /usr/bin/kaccess /usr/bin/kup-daemon /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd /usr/bin/gmenudbusmenuproxy /usr/bin/ksmserver /usr/bin/kded5 4. I then tried the command "XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland", which let me login to Plasma Wayland session. I tried to obtain a backtrace from there by launching Konsole, and executing the command "sudo coredumpctl --reverse" with the same result: no "kwin" or "wayland". I can also copy here the output of command "sudo coredump gdb <number> for "plasmashell" if it makes sense. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! I fixed it by changing QT_STYLE_OVERRIDE flag to breeze. https://www.reddit.com/r/artixlinux/comments/133a1fz/kde_wayland_on_dinit_not_working/ |