Description of problem: Happened during openQA KDE desktop_login test, after the test created a user account, logged in as that user, and then logged out; it should have returned to SDDM but in fact seemed to crash to VT on tty2. Version-Release number of selected component: xdg-desktop-portal-kde-5.24.4-1.fc37 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user/session.slice/plasma-xdg-desktop-portal-kde.service cmdline: /usr/libexec/xdg-desktop-portal-kde crash_function: qt_message_fatal executable: /usr/libexec/xdg-desktop-portal-kde journald_cursor: s=531452f63d834872971f6ffe51b34a8b;i=25c0;b=415fecee09b74c82825075faa3a0f901;m=7e6c177;t=5ddc92314dc3a;x=128c06f7b6f22f9d kernel: 5.18.0-0.rc4.20220428git8f4dd16603ce834.36.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (8 frames) #4 qt_message_fatal at global/qlogging.cpp:1914 #5 QMessageLogger::fatal at global/qlogging.cpp:893 #6 init_platform at kernel/qguiapplication.cpp:1254 #7 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1474 #8 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1491 #9 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:835 #10 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1520 #11 QApplicationPrivate::init at kernel/qapplication.cpp:513 Potential duplicate: bug 1717252
Created attachment 1876652 [details] File: backtrace
Created attachment 1876653 [details] File: core_backtrace
Created attachment 1876654 [details] File: cpuinfo
Created attachment 1876655 [details] File: dso_list
Created attachment 1876656 [details] File: environ
Created attachment 1876657 [details] File: limits
Created attachment 1876658 [details] File: maps
Created attachment 1876659 [details] File: mountinfo
Created attachment 1876660 [details] File: open_fds
Created attachment 1876661 [details] File: proc_pid_status
This is still happening on every run of the test.
Hmm, I think this is more something going wrong with sddm than an xdg-desktop-portal-kde issue, actually. xdg-desktop-portal-kde 'crashing' - along with most of the rest of the session - seems to be kinda normal on logout from a Wayland session; the Wayland compositor goes away and everything running on top of it just freaks out and dies. You'd think that could be handled more gracefully, but I don't think it's the *problem* here, the problem is that when that happens, we should return to a running sddm, but we're not. I'm going to try and reproduce this manually to see whether we're on the wrong tty, or sddm just died, or what.
Yeah, pretty sure there's something up with sddm here. Gonna close this bug and open a new one on SDDM.