Bug 480305

Summary:	With Application Dashboard, holding down Alt+F1 shortcut (but not Meta key) crashes Plasma
Product:	[Plasma] plasmashell	Reporter:	Andrew Shark <ashark>
Component:	Application Dashboard widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bad63r, nate
Priority:	NOR	Keywords:	qt6
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Andrew Shark 2024-01-25 07:35:14 UTC

My Kickoff menu (Start menu) on one of the screens is binded to the Alt + F1 shortcut.

The kickoff menu may have three variants (alternatives). Mine in this monitor is configured as Whole screen (the big icons on the black blur background).

I am on Wayland session. This monitor is configured so it scales 200% (UHD monitor), while the other monitor is 100%.

When I press Alt + F1 single time, I can see a "small lag" - the start menu is not immediately drawn. For a fraction of a second the icons appear with the wrong scale (not 200% scale), and after a bit of time, it is finally shown.

Now, if I will press Alt + F1 several times in a row (I guess, it triggers cancel when it is in the middle position - already activated, but not yet drawn fully), the Plasma desktop "crashes". Applications stay opened, but I see that panel disappears, and after some time appears again (plasma self recovered).

Now, if I will press and hold Alt + F1, then plasma is going to state where it cannot self-recover anymore (the panel is no more shown).

Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.7.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon Pro W6600

Comment 1 Nate Graham 2024-01-25 23:07:22 UTC

Does it happen with any other launcher menus, like Kickoff or Kicker?

Can you attach a symbolicated backtrace of the crash?

Comment 2 Nate Graham 2024-01-25 23:18:28 UTC

Cannot reproduce with Kicker or Kickoff, but I can reproduce the crash fairly instantly with Application Dashboard.

The backtrace looks fairly unhelpful, though:

(gdb) bt
#0  0x00007f2365125bcd in __GI___poll (fds=0x6e5afd0, nfds=18, timeout=1661)
    at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f236451deb4 in g_main_context_poll_unlocked
    (priority=2147483647, n_fds=18, fds=0x6e5afd0, timeout=<optimized out>, context=0x7f234c000ef0)
    at ../glib/gmain.c:4653
#2  g_main_context_iterate_unlocked.isra.0
    (context=context@entry=0x7f234c000ef0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at ../glib/gmain.c:4344
#3  0x00007f23644c0ad3 in g_main_context_iteration (context=0x7f234c000ef0, may_block=1) at ../glib/gmain.c:4414
#4  0x00007f2365a4096f in QEventDispatcherGlib::processEvents (this=0x1893c40, flags=...)
    at /usr/src/debug/qt6-qtbase-6.6.0-6.fc39.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:393
#5  0x00007f23657ad9bb in QEventLoop::exec (this=this@entry=0x7ffd8423a690, flags=..., flags@entry=...)
    at /usr/src/debug/qt6-qtbase-6.6.0-6.fc39.x86_64/src/corelib/global/qflags.h:34
#6  0x00007f23657a97bd in QCoreApplication::exec ()
    at /usr/src/debug/qt6-qtbase-6.6.0-6.fc39.x86_64/src/corelib/global/qflags.h:74
#7  0x00007f2365ff8b4d in QGuiApplication::exec ()
    at /usr/src/debug/qt6-qtbase-6.6.0-6.fc39.x86_64/src/gui/kernel/qguiapplication.cpp:1921
#8  0x00007f2367dc2aa9 in QApplication::exec ()
    at /usr/src/debug/qt6-qtbase-6.6.0-6.fc39.x86_64/src/widgets/kernel/qapplication.cpp:2569
#9  0x0000000000425f4f in main (argc=<optimized out>, argv=<optimized out>)
    at /home/nate/kde/src/plasma-workspace/shell/main.cpp:214

Comment 3 Tom 2025-04-07 22:15:48 UTC

Can't reproduce this. I'm on Wayland.
Specs:
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
Kernel Version: 6.12.21-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1145G7 @ 2.60GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Xe Graphics

Can someobody check this as well? If we can't reproduce this, I will close it as resolved.

Comment 4 Nate Graham 2025-04-08 16:39:58 UTC

Comment 5 Andrew Shark 2025-04-08 17:27:51 UTC

Seems this is fixed now.

Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor 1: NVIDIA GeForce GTX 1660 Ti
Graphics Processor 2: Intel® UHD Graphics