This is the first crash, then there was another four after this as if it tried to restart 4 times and crashed each time. Sun 2024-03-10 16:09:20 ACDT 1746080 1001 1004 SIGABRT present /usr/lib64/kf6/xdg-desktop-portal-kde 983.6K Sun 2024-03-10 16:09:21 ACDT 1746146 1001 1004 SIGABRT present /usr/lib64/kf6/xdg-desktop-portal-kde 981.8K Sun 2024-03-10 16:09:21 ACDT 1746173 1001 1004 SIGABRT present /usr/lib64/kf6/xdg-desktop-portal-kde 984.0K Sun 2024-03-10 16:09:22 ACDT 1746194 1001 1004 SIGABRT present /usr/lib64/kf6/xdg-desktop-portal-kde 983.1K Sun 2024-03-10 16:09:22 ACDT 1746210 1001 1004 SIGABRT present /usr/lib64/kf6/xdg-desktop-portal-kde 982.5K #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78 #2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at pthread_kill.c:89 #3 0x00007fa9f6c44256 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x00007fa9f6c28835 in __GI_abort () at abort.c:79 #5 0x00007fa9f7663e7a in qAbort () at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/corelib/global/qglobal.cpp:161 #6 0x00007fa9f7667dd1 in qt_message_fatal<QString&> (context=<optimized out>, message=<optimized out>) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:2030 #7 qt_message (msgType=QtFatalMsg, context=..., msg=<optimized out>, ap=<optimized out>) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:378 #8 0x00007fa9f766915e in QMessageLogger::fatal (this=0x1aa4a0, msg=0x8 <error: Cannot access memory at address 0x8>) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:901 #9 0x00007fa9f7e96dca in init_platform (pluginNamesWithArguments=<optimized out>, platformPluginPath=..., platformThemeName=..., argc=@0x7ffeb6d293fc: 1, argv=0x7ffeb6d29558) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1284 #10 0x00007fa9f7e947ae in QGuiApplicationPrivate::createPlatformIntegration (this=0x5654bf7cc680) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1532 #11 0x00007fa9f7e97140 in QGuiApplicationPrivate::createEventDispatcher (this=0x0) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1551 #12 0x00007fa9f76ecc3e in QCoreApplicationPrivate::init (this=0x5654bf7cc680) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:900 #13 0x00007fa9f7e8f59a in QGuiApplicationPrivate::init (this=0x1aa4a0) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1579 #14 0x00007fa9f8634dd1 in QApplicationPrivate::init (this=0x1aa4a0) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:473 #15 0x00005654bdfc2026 in ??? () #16 0x00007fa9f6c2a30e in __libc_start_call_main (main=main@entry=0x5654bdfc1fd0, argc=argc@entry=1, argv=argv@entry=0x7ffeb6d29558) at ../sysdeps/nptl/libc_start_call_main.h:58 #17 0x00007fa9f6c2a3c9 in __libc_start_main_impl (main=0x5654bdfc1fd0, argc=1, argv=0x7ffeb6d29558, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffeb6d29548) at ../csu/libc-start.c:360 #18 0x00005654bdf3fb05 in ??? ()
*** This bug has been marked as a duplicate of bug 482730 ***
Just FYI this wasn't when the system booted. It was after applying the display settings in the other bug (https://bugs.kde.org/show_bug.cgi?id=483072). The order of crashes was in quick succession: System settings DrKonqi XDG Portal
OK, maybe it's something else. Still, the symptoms and backtrace look the same. So can you check again if it still happens after you have Frameworks 6.1, where the fix for Bug 482730 landed? Thanks!
(In reply to Nate Graham from comment #3) > OK, maybe it's something else. Yes, it's something else. I can reproduce with master snapshots updated every day. I posted my findings there: https://bugs.kde.org/show_bug.cgi?id=483073#c4