https://bugs.kde.org/show_bug.cgi?id=510655
Bug ID: 510655
Summary: Crash in Application Dashboard after grabbing an icon
Classification: Plasma
Product: plasmashell
Version First 6.4.5
Reported In:
Platform: Bazzite
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Application Dashboard widget
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
# Crash in Application Dashboard
## What happened?
I'm getting plasmashell crashes when dragging an application in the Application
Dashboard.
Steps to reproduce:
1. Open the application dashboard
2. Hover over "All applications" to show all apps
3. Grab an app icon from the app list, drag it somewhere and drop it
4. (pick one)
4.1. Try to scroll down through the list of all applications
4.2. Repeat step 3 multiple times
Result: The dashboard freezes completely. Then the panel disappears. 2-4
seconds later the system recovers by restarting plasmashell and showing a crash
report window/pop-up.
(see the attached video for a few examples)
When it comes to step 4, the crash can be caused by either:
- (4.1) just scrolling through the list
- (4.2) grabbing another icon and dropping it (sometimes it requires multiple
drag-drops, sometimes just grabbing/clicking an icon)
Notably, to recreate the crash you need to have the "All Applications" view
displayed *while* dragging the app launcher/icon. If you do any of the
following, the crash will NOT happen:
(Case 1; won't crash because the "All Apps" section was not visible at first)
1. Have anything other than "All applications" displayed
2. Drag-drop any icon anywhere
3. Go to "All Applications"
4. Scroll through the list
Result: No crash. The "All Applications" list loaded after the drag-drop
interaction.
(Case 2; won't crash because the "All Apps" section was reloaded)
1. Have "All applications" displayed
2. Drag-drop any icon anywhere
3. Hover over anything other than "All applications" (make sure you haven't
scrolled yet)
4. Go back to "All Applications"
5. Scroll through the list
Result: No crash. I assume the "All apps" component unmounted and re-mounted
due to the user navigating away from it and then navigating back.
(Case 3; won't crash, but the list unloads for some reason)
1. Have anything other than "All applications" displayed
2. Drag-drop any icon anywhere
3. All the icons in the middle section disappear from the currently active app
category
Result: No crash, but there is a bug: all the icons disappear from the middle
section. So I'm not sure if the categories would crash too, since their app
list cannot be interacted with after a drag-drop.
(Case 4; favorites won't crash, the bug seems isolated to the middle section)
1. Have anything other than "All applications" displayed
2. Have enough applications under "Favorites" (the left section) so that it
displays a scroll bar
3. Drag around any icon
4. Scroll through the "Favorites" section
Result: No crash. It looks like the bug is entirely isolated to the middle
section of the dashboard.
In my case I first discovered the issue when I was simply trying to pin my apps
from the "All applications" to the "Favorites" section. (Pinning the apps with
the "right-click -> Add to favorites" action does not cause a crash). At first
this happened pretty much instantly. But the more I tried to recreate the bug,
the longer it takes to crash. When I started recording, it already started
taking 2-5 seconds for plasma to crash after scrolling. At first it crashed
instantly or took up to a second.
## System specs
### KDE
KDE Plasma 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
KWin (Wayland)
### OS
aurora:stable
Aurora (Version: 42.20251012.1)
Linux 6.16.7-200.fc42.x86_64
Mesa 25.1.9 (LLVM 20.1.8)
I've tested both an existing install of Aurora and a clean install. In both
cases I can reproduce the bug. I selected Bazzite as a platform since it's a
sibling distro of Aurora and from my recollection this also happened to me on
Bazzite once (I just ignored it and assumed it cannot be recreated. Adding
stuff to favorites is something I only do once or twice and often I just close
the dashboard rather than keep interacting with it).
In a day or two I'll try testing a couple of other distros, like KDE Linux,
unless someone beats me to it. (Just to confirm this isn't something related to
my distro specifically)
### Hardware
I managed to recreate the bug on multiple devices, one all Intel with
integrated graphics and one all AMD with a dedicated GPU. So I don't think it's
a hardware issue.
### Logs
I tried generating a proper crash log, but the result is always "information is
not useful". So the following is the only information I have for now:
```
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7fed8ba212c0 (LWP 107714))]
Cannot QML trace cores :(
add symbol table from file "/lib64/libc.so.6"
add symbol table from file "/lib64/libKF6Crash.so.6"
Traceback (most recent call last):
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 813, in
print_preamble
print_preamble_internal()
~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 804, in
print_preamble_internal
print_sentry_payload(thread)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 728, in
print_sentry_payload
payload = SentryEvent().make(program, thread)
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 521, in
make
stacktrace = SentryTrace(crash_thread, True).to_dict()
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 368, in
to_dict
SentryTrace.load_solib(self.thread, cramped_memory)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 332, in
load_solib
raise UnexpectedMappingException(f"No solib and no image found for frame
#{i} on thread {thread}! You could try with debug symbols downloading
enabled.")
UnexpectedMappingException: No solib and no image found for frame #4 on thread
<gdb.InferiorThread id=1.1 target-id="Thread 0x7fed8ba212c0 (LWP 107714)">! You
could try with debug symbols downloading enabled.
No solib and no image found for frame #4 on thread <gdb.InferiorThread id=1.1
target-id="Thread 0x7fed8ba212c0 (LWP 107714)">! You could try with debug
symbols downloading enabled.
Sentry is attempting to send 2 pending events
```
--
You are receiving this mail because:
You are watching all bug changes.
