Created attachment 160199 [details] The log from Crashed Processes Viewer SUMMARY xdg-desktop-portal-kde silently crashes when logging into a Plasma 6 session. STEPS TO REPRODUCE 1. Log into a new Plasma 6 session OBSERVED RESULT Nothing unual seems to happen but when opening the crashed process viewer xdg-desktop-portal-kde shows up every time a session is started EXPECTED RESULT xdg-desktop-portal-kde should not crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon Unstable (Updated a few days ago) (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 ADDITIONAL INFORMATION
Created attachment 160200 [details] Acual log
Stack trace of thread 1006: #0 0x00007f0700296a7c __pthread_kill_implementation (libc.so.6 + 0x96a7c) #1 0x00007f0700242476 __GI_raise (libc.so.6 + 0x42476) #2 0x00007f07002287f3 __GI_abort (libc.so.6 + 0x287f3) #3 0x00007f0700aadf26 _Z6qAbortv (libQt6Core.so.6 + 0xadf26) #4 0x00007f0700aaeeab _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0xaeeab) #5 0x00007f0701122864 n/a (libQt6Gui.so.6 + 0x122864) #6 0x00007f07011adc79 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x1adc79) #7 0x00007f07011ae948 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1ae948) #8 0x00007f0700b3e637 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x13e637) #9 0x00007f07011b13c4 _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x1b13c4) #10 0x00007f070198d3bd _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0x18d3bd) #11 0x00005616194f7117 n/a (xdg-desktop-portal-kde + 0x45117) #12 0x00007f0700229d90 __libc_start_call_main (libc.so.6 + 0x29d90) #13 0x00007f0700229e40 __libc_start_main_impl (libc.so.6 + 0x29e40) #14 0x00005616194f77b5 n/a (xdg-desktop-portal-kde + 0x457b5)
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols. Could you please install debug symbols, reproduce the crash, and attach a new symbolicated backtrace? You can use the `coredumpctl` command-line program to do this, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. Can you do that? Thanks again?
I can't reproduce after doing a full update. If I run coredumpctl the last xdg-desktop-portal-kde crash shows up as inaccessible and the rest are labeled missing.
Awesome, thanks for following up!