Bug 483073

Summary: Crashed after another app crashed
Product: [Applications] drkonqi Reporter: Justin Zobel <justin>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: REPORTED ---    
Severity: crash CC: bugseforuns, christophe, nate, sitter
Priority: NOR    
Version First Reported In: master   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=500179
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Justin Zobel 2024-03-10 05:47:52 UTC 
Built from src using kdesrc-build:

Sun 2024-03-10 16:09:19 ACDT 1745848 1001 1004 SIGSEGV present      /home/justin/kde/usr/bin/systemsettings                                     14.4M
Sun 2024-03-10 16:09:20 ACDT 1746099 1001 1004 SIGABRT present      /usr/lib64/kf6/drkonqi                                                     806.7K

#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  0x00007f2cc2e44256 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007f2cc2e28835 in __GI_abort () at abort.c:79
#5  0x00007f2cc3863e7a in qAbort () at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/corelib/global/qglobal.cpp:161
#6  0x00007f2cc3867dd1 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  0x00007f2cc386915e in QMessageLogger::fatal (this=0x1aa4b3, 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  0x00007f2cc4296dca in init_platform (pluginNamesWithArguments=<optimized out>, platformPluginPath=..., platformThemeName=..., argc=@0x7ffd2c70e66c: 17, argv=0x7ffd2c70e888) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1284
#10 0x00007f2cc42947ae in QGuiApplicationPrivate::createPlatformIntegration (this=0x55d6c79f97c0) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1532
#11 0x00007f2cc4297140 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 0x00007f2cc38ecc3e in QCoreApplicationPrivate::init (this=0x55d6c79f97c0) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:900
#13 0x00007f2cc428f59a in QGuiApplicationPrivate::init (this=0x1aa4b3) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1579
#14 0x00007f2cc4a34dd1 in QApplicationPrivate::init (this=0x1aa4b3) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:473
#15 0x000055d6c68a617f in ??? ()
#16 0x00007f2cc2e2a30e in __libc_start_call_main (main=main@entry=0x55d6c68a6100, argc=argc@entry=19, argv=argv@entry=0x7ffd2c70e888) at ../sysdeps/nptl/libc_start_call_main.h:58
#17 0x00007f2cc2e2a3c9 in __libc_start_main_impl (main=0x55d6c68a6100, argc=19, argv=0x7ffd2c70e888, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd2c70e878) at ../csu/libc-start.c:360
#18 0x000055d6c68a6035 in ??? ()
Comment 1 Harald Sitter 2024-03-11 15:58:02 UTC 
Did the compositor crash maybe?  This isn't really a crash but qapplication failing to start.
Comment 2 Justin Zobel 2024-03-12 01:50:12 UTC 
Yes the session was destroyed. The starting bug/crash was applying settings in systemsettings: https://bugs.kde.org/show_bug.cgi?id=483072
Comment 3 Christophe Marin 2024-03-25 11:00:29 UTC 
*** Bug 482251 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Marin 2024-03-25 11:19:20 UTC 
I don't have a clear way to reproduce but each time I see this crash, it happens when restoring an application using the tray icon if the screens were turned off due to inactivity before (not immediately before, but I don't think I ever had the crash if the screens didn't turn off before)

coredumpctl always saves bt for gmenudbusmenuproxy, kwalletd6 and kwin_x11 in this case (and sometimes xembedsniproxy)
Comment 5 Christophe Marin 2024-04-02 11:01:51 UTC 
*** Bug 484108 has been marked as a duplicate of this bug. ***