Bug 477477 - Testing QT6/Plasma 6 on endeavouros: plasmashell crashed when adjusting panel
Summary: Testing QT6/Plasma 6 on endeavouros: plasmashell crashed when adjusting panel
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: master
Platform: Other Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-11-24 18:45 UTC by semlraug
Modified: 2023-12-01 13:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Logs (106.89 KB, text/plain)
2023-11-24 18:50 UTC, semlraug
Details

Note You need to log in before you can comment on or make changes to this bug.
Description semlraug 2023-11-24 18:45:15 UTC
SUMMARY
***
Plasmashell crashes when moving and changing panel
***


STEPS TO REPRODUCE
1. Right click panel and enter edit mode
2. choose to position panel to a different location
3. adjust the height of the panel

OBSERVED RESULT
Desktop freezes, then crashes
after desktop has been restarted the panel appears unchanged

EXPECTED RESULT
moved panel and changed panel height

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)

Operating System: EndeavourOS 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.6.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 3.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Acer
Product Name: Aspire A315-53
System Version: V2.02
ADDITIONAL INFORMATION

Over at https://forum.endeavouros.com/t/testing-plasma-6-beta-on-endeavour-os-is-this-approach-any-good/47539/132 other people are reporting similar behaviour when adjusting the panel
Comment 1 semlraug 2023-11-24 18:50:19 UTC
Created attachment 163435 [details]
Logs

See attachment for my attempt to gather the logs
Comment 2 semlraug 2023-11-24 18:51:10 UTC
BTW: does not happen all the time.
Comment 3 Nate Graham 2023-11-26 17:15:41 UTC
Can you attach a real backtrace? The one in your attachment is garbled. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Thanks!

FWIW I haven't been able to reproduce this.
Comment 4 semlraug 2023-11-26 17:38:22 UTC
I'm new to this so sorry for not providing the log in the right format.

Did as you suggested. Is this better?

#0  0x00007f350796257f in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#1  0x00007f3507fe9ad0 in QPlatformWindow::deliverUpdateRequest() () at /usr/lib/libQt6Gui.so.6
#2  0x00007f35079a5077 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6
#3  0x00007f350897318b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6
#4  0x00007f35079626d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#5  0x00007f3507962a5b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6
#6  0x00007f3507b99d24 in  () at /usr/lib/libQt6Core.so.6
#7  0x00007f3506583f69 in  () at /usr/lib/libglib-2.0.so.0
#8  0x00007f35065e2327 in  () at /usr/lib/libglib-2.0.so.0
#9  0x00007f3506582162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#10 0x00007f3507b97934 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#11 0x00007f350796cc5e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#12 0x00007f3507965178 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6
#13 0x00005630803fe22c in  ()
#14 0x00007f3507245cd0 in  () at /usr/lib/libc.so.6
#15 0x00007f3507245d8a in __libc_start_main () at /usr/lib/libc.so.6
#16 0x00005630803fe9e5 in  ()

Thanks for all the hard work :-).
Comment 5 semlraug 2023-11-26 17:53:42 UTC
Have again changed the panel (from left to right + change height, and when there was no chrash, I moved it back from right to left again, adjusting height). Then plasma chrashed again - here's the back trace of that event:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f66bbd6257f in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt6Core.so.6
[Current thread is 1 (Thread 0x7f66b6ccd9c0 (LWP 932))]
(gdb) bt
#0  0x00007f66bbd6257f in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#1  0x00007f66bc3e9ad0 in QPlatformWindow::deliverUpdateRequest() () at /usr/lib/libQt6Gui.so.6
#2  0x00007f66bbda5077 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6
#3  0x00007f66bcd7318b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6
#4  0x00007f66bbd626d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#5  0x00007f66bbd62a5b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6
#6  0x00007f66bbf99d24 in  () at /usr/lib/libQt6Core.so.6
#7  0x00007f66ba960f69 in  () at /usr/lib/libglib-2.0.so.0
#8  0x00007f66ba9bf327 in  () at /usr/lib/libglib-2.0.so.0
#9  0x00007f66ba95f162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#10 0x00007f66bbf97934 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#11 0x00007f66bbd6cc5e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#12 0x00007f66bbd65178 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6
#13 0x000055d7a886e22c in  ()
#14 0x00007f66bb645cd0 in  () at /usr/lib/libc.so.6
#15 0x00007f66bb645d8a in __libc_start_main () at /usr/lib/libc.so.6
#16 0x000055d7a886e9e5 in  ()
Comment 6 semlraug 2023-11-27 16:58:00 UTC
Just trying to be helpful and provide some more info:

Tested changing the panel into a floating panel (from non-floating).
Scenario: 
- open panel edit mode
- in "style" switch to floating
- then I changed width
- then clicked outside of panel/edit menu:

Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fc31f76257f in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt6Core.so.6
[Current thread is 1 (Thread 0x7fc31a78b9c0 (LWP 953))]
(gdb) bt
#0  0x00007fc31f76257f in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#1  0x00007fc31fde9ad0 in QPlatformWindow::deliverUpdateRequest() () at /usr/lib/libQt6Gui.so.6
#2  0x00007fc31f7a5077 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6
#3  0x00007fc32077318b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6
#4  0x00007fc31f7626d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#5  0x00007fc31f762a5b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6
#6  0x00007fc31f999d24 in  () at /usr/lib/libQt6Core.so.6
#7  0x00007fc31e41cf69 in  () at /usr/lib/libglib-2.0.so.0
#8  0x00007fc31e47b327 in  () at /usr/lib/libglib-2.0.so.0
#9  0x00007fc31e41b162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#10 0x00007fc31f997934 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#11 0x00007fc31f76cc5e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#12 0x00007fc31f765178 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6
#13 0x000056451bc0722c in  ()
#14 0x00007fc31f045cd0 in  () at /usr/lib/libc.so.6
#15 0x00007fc31f045d8a in __libc_start_main () at /usr/lib/libc.so.6
#16 0x000056451bc079e5 in  ()
(gdb) 

I also tested:
- enter edit mode
- click outside edit menu
- press esc:

0  0x00007fbc91360c75 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt6Core.so.6
[Current thread is 1 (Thread 0x7fbc8c2659c0 (LWP 6179))]
(gdb) bt
#0  0x00007fbc91360c75 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#1  0x00007fbc9237317b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6
#2  0x00007fbc913626d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#3  0x00007fbc919e9ad0 in QPlatformWindow::deliverUpdateRequest() () at /usr/lib/libQt6Gui.so.6
#4  0x00007fbc913a5077 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6
#5  0x00007fbc9237318b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6
#6  0x00007fbc913626d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6
#7  0x00007fbc91362a5b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6
#8  0x00007fbc91599d24 in  () at /usr/lib/libQt6Core.so.6
#9  0x00007fbc8fef8f69 in  () at /usr/lib/libglib-2.0.so.0
#10 0x00007fbc8ff57327 in  () at /usr/lib/libglib-2.0.so.0
#11 0x00007fbc8fef7162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#12 0x00007fbc91597934 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#13 0x00007fbc9136cc5e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6
#14 0x00007fbc91365178 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6
#15 0x00005622c165022c in  ()
#16 0x00007fbc90c45cd0 in  () at /usr/lib/libc.so.6
#17 0x00007fbc90c45d8a in __libc_start_main () at /usr/lib/libc.so.6
#18 0x00005622c16509e5 in  ()
Comment 7 Nate Graham 2023-11-28 21:30:57 UTC
Thanks. Is this 100% reproducible for you? I ask because I can't reproduce it and I suspect it's already been fixed as a part of some of the other Panel-related work that went in recently.
Comment 8 semlraug 2023-11-29 06:04:40 UTC
Not quite 100%. But, in my setup, I would say 90% of the time.

Over at EndeavorOS more people are testing Plasma 6 as well and have experienced this crash as well. I've asked them to report their backtraces too. I hope they will do so once Plasma 6 has reached beta status.

FYI: I'm running an updated EndeavorOS with kde-unstable, core-testing and extra-testing.
Comment 9 Nate Graham 2023-11-29 17:58:02 UTC
Does EndeavourOS track the latest git master for Plasma 6? Or is it still shipping the alpha release?
Comment 10 semlraug 2023-11-29 18:17:48 UTC
I'm unsure how to answer your question (I'm no dev) but I have asked over at EndeavourOS how to answer you.

What I *do* know is that EndeavourOS is based on Arch Linux, that we use the arch kde-unstable, core-testing and extra-testing repo's[1] tp help test Plasma 6.

As soon as I get an answer from anyone more knowledgeable than me, I'll let you know.

[1] https://wiki.archlinux.org/title/official_repositories#Testing_repositories
Comment 11 semlraug 2023-11-29 18:19:59 UTC
Got his answer for you: "yes it [EndeavourOS] tracks releases and not git dev snapshots.

Hope this is the answer that clarifies the situation,.
Comment 12 semlraug 2023-11-29 18:23:58 UTC
Some more information for you:

You can answer that EndeavourOS uses the Arch repositories, so it does the same as Arch.
It is the alpha release, not the git version:
source=(https://download.kde.org/unstable/plasma/$_dirver/$pkgname-$pkgver.tar.xz{,.sig})

source=(https://download.kde.org/unstable/frameworks/$pkgver/$pkgname-$pkgver.tar.xz{,.sig})

From this thread: https://forum.endeavouros.com/t/testing-plasma-6-beta-on-endeavour-os-is-this-approach-any-good/47539/181?u=semlraug
Comment 13 Nate Graham 2023-11-30 20:45:28 UTC
Ok, in that case you're using the Alpha release which is a month old. It's very likely the bug has already been fixed in the Beta 1 release, so I'd recommend upgrading to that once EndeavourOS provides it, and test again.
Comment 14 semlraug 2023-12-01 13:53:02 UTC
I am now on the Beta release and have not been able to reproduce this crash. I'll mark this report as solved. Thanks!