Bug 449027 - Crash when clicking on application dashboard icon on panel
Summary: Crash when clicking on application dashboard icon on panel
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.23.5
Platform: Kubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
: 456605 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-01-23 18:41 UTC by Jan Rathmann
Modified: 2023-01-03 12:11 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Rathmann 2022-01-23 18:41:09 UTC
This crash happened randomly (not reproduceable for me) when I clicked on the panel icon to bring up the application dashboard.

Kubuntu 21.10
Plasma 5.23.5 (Wayland session)
Frameworks 5.90.0
Qt 5.15.2

Backtrace:
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140279635527232)
    at pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140279635527232)
    at pthread_kill.c:80
#2  __GI___pthread_kill (threadid=140279635527232, signo=signo@entry=6)
    at pthread_kill.c:91
#3  0x00007f956a8fa476 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
#4  0x00007f956ce0157c in KCrash::defaultCrashHandler(int) ()
   from /lib/x86_64-linux-gnu/libKF5Crash.so.5
#5  <signal handler called>
#6  g_main_context_check (context=0x7f9560000c20, max_priority=2147483647, 
    fds=<optimized out>, n_fds=1708669304) at ../../../glib/gmain.c:3945
#7  0x00007f9569421e4d in g_main_context_iterate.constprop.0 (
    context=context@entry=0x7f9560000c20, block=block@entry=1, 
    dispatch=dispatch@entry=1, self=<optimized out>)
    at ../../../glib/gmain.c:4128
#8  0x00007f95693cc003 in g_main_context_iteration (context=0x7f9560000c20, 
    may_block=1) at ../../../glib/gmain.c:4196
#9  0x00007f956b0095be in QEventDispatcherGlib::processEvents (
    this=0x7f9560000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#10 0x00007f956afaea9b in QEventLoop::exec (this=this@entry=0x7f9565d83b50, 
    flags=..., flags@entry=...)
    at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#11 0x00007f956adc28c2 in QThread::exec (
    this=this@entry=0x7f956b9c9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>)
    at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#12 0x00007f956b94fefb in QDBusConnectionManager::run (this=
    0x7f956b9c9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ./src/dbus/qdbusconnection.cpp:179
#13 0x00007f956adc3a71 in QThreadPrivate::start (
    arg=0x7f956b9c9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:329
#14 0x00007f956a94c927 in start_thread (arg=<optimized out>)
    at pthread_create.c:435
#15 0x00007f956a9dc9e4 in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100
Comment 1 Nate Graham 2022-01-23 21:52:19 UTC
Hmm, no KDE code implicated.
Comment 2 Jan Rathmann 2022-01-24 10:42:26 UTC
Would it help to make the full coredump avaiable? (37.4M in size)
Comment 3 Nate Graham 2022-01-24 18:25:02 UTC
Probably not, unfortunately.
Comment 4 Jan Rathmann 2022-02-25 08:17:02 UTC
Update: This kind of crash has continued to appear from time to time recently, triggered by the same action (clicking on dashboard icon) and with similar backtraces.

I'm not that experienced in reading backtraces, but could it indicate that there is some problem/bug with glib (not KDE related)?
Comment 5 Nate Graham 2022-07-13 19:56:33 UTC
*** Bug 456605 has been marked as a duplicate of this bug. ***
Comment 6 Bug Janitor Service 2022-09-27 20:09:56 UTC
A possibly relevant merge request was started @ https://invent.kde.org/qt/qt/qtwayland/-/merge_requests/56
Comment 7 David Edmundson 2023-01-03 11:43:07 UTC
>#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140279635527232)

Signal 6 is an abort. This is externally generated.
Comment 8 Jan Rathmann 2023-01-03 12:11:02 UTC
Fortunately I haven't seen this bug for a really long time, so it seems that something happened that fixed it :)