Bug 489565

Summary:	Resizing Kickoff placed in bottom panel via upper right corner causes Plasma to hang
Product:	[Plasma] plasmashell	Reporter:	FezzedOne
Component:	Application Launcher (Kickoff) widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	crash	CC:	akselmo, justin, kde, mikel5764, nate, noahadvs, notmart
Priority:	NOR
Version First Reported In:	6.1.1
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Backtrace from gdb

Description FezzedOne 2024-07-01 19:49:41 UTC

Created attachment 171251 [details]
Backtrace from gdb

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY

When I attempt to resize a newly added Kickoff widget via the corner, Plasma hangs and I have to `killall -9 plasma` to get it to restart.

STEPS TO REPRODUCE
1. Add a new Kickoff widget to the panel.
1. Open up the Kickoff menu.
2. Click and drag the upper-right corner to resize it (my panel is on the bottom of the screen).

OBSERVED RESULT

Plasma hangs as soon as I start dragging.

EXPECTED RESULT

Plasma shouldn't hang.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.9.7-2-cachyos on Arch
(available in About System)
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Attached is a backtrace from `gdb`.

Comment 1 Akseli Lahtinen 2024-07-02 08:06:13 UTC

Can reproduce, it only happens from upper right corner. Strange.

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.80
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.1
Kernel Version: 6.9.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600

Comment 2 Akseli Lahtinen 2024-07-02 10:32:16 UTC

Hm after rebuilding my system to master branches again, it doesnt happen to me anymore.

Comment 3 Nate Graham 2024-07-02 21:04:49 UTC

Also cannot reproduce with today's git master, and also with Qt 6.7.1. The backtrace is all in Qt; I wonder if this could be a Qt 6.7.2 regression.

Comment 4 Justin Zobel 2024-09-02 06:45:14 UTC

Can confirm with git master and Qt 6.7.2 so it is likely as Nate said a regression.

The kickoff menu freezes and stutters. The only way to get the system back is systemctl --user restart plasma-plasmashell

I did see a crash in kaccess just around the time this freeze happens, not sure if relevant but figured I'd paste just in case.


#0  __pthread_kill_implementation (threadid=<optimized out>, signo=6, no_tid=0) at pthread_kill.c:44
#1  __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#2  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at pthread_kill.c:89
#3  0x00007f330aa51296 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007f330aa35838 in __GI_abort () at abort.c:79
#5  0x00007f330b26bbca in qAbort () at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/corelib/global/qglobal.cpp:161
#6  0x00007f330b26f721 in qt_message_fatal<QString&> (context=..., message=...) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/corelib/global/qlogging.cpp:2052
#7  qt_message (msgType=QtFatalMsg, context=..., msg=<optimized out>, ap=<optimized out>)
    at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/corelib/global/qlogging.cpp:374
#8  0x00007f330b270b1c in QMessageLogger::fatal (this=0xca7, msg=0x8 <error: Cannot access memory at address 0x8>)
    at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/corelib/global/qlogging.cpp:889
#9  0x00007f330ba9b57a in init_platform (pluginNamesWithArguments=..., platformPluginPath=..., platformThemeName=..., argc=@0x7fff49bba98c: 1, argv=0x7fff49bbae38)
    at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/gui/kernel/qguiapplication.cpp:1285
#10 0x00007f330ba98f16 in QGuiApplicationPrivate::createPlatformIntegration (this=0x564e49f65210)
    at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/gui/kernel/qguiapplication.cpp:1533
#11 0x00007f330ba9b8f0 in QGuiApplicationPrivate::createEventDispatcher (this=0x0) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/gui/kernel/qguiapplication.cpp:1552
#12 0x00007f330b2f405e in QCoreApplicationPrivate::init (this=0x564e49f65210) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qcoreapplication.cpp:905
#13 0x00007f330ba93c3a in QGuiApplicationPrivate::init (this=0xca7) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/gui/kernel/qguiapplication.cpp:1580
#14 0x00007f330c640a11 in QApplicationPrivate::init (this=0xca7) at /home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.7.2/src/widgets/kernel/qapplication.cpp:472
#15 0x0000564e2e2ab05e in main (argc=1, argv=0x7fff49bbae38) at /home/justin-ksb/kde/src/plasma-desktop/kaccess/main.cpp:38

Comment 5 Justin Zobel 2024-09-02 06:45:37 UTC

Forgot to note that it only appears to happen to newly added kickoff applets.

Comment 6 Nate Graham 2025-01-23 20:51:01 UTC

At this point we require Qt 6.8, which doesn't seem to be affected,