Bug 434553 - Invisible crash while changing panel display (auto-hide vs always visible)
Summary: Invisible crash while changing panel display (auto-hide vs always visible)
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.21.3
Platform: Manjaro Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-17 17:36 UTC by pveax
Modified: 2021-04-17 04:33 UTC (History)
1 user (show)

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


Attachments
journalctl -b --no-host -o short-precise.txt (73.34 KB, text/plain)
2021-03-17 17:36 UTC, pveax
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pveax 2021-03-17 17:36:16 UTC
Created attachment 136795 [details]
journalctl -b --no-host -o short-precise.txt

SUMMARY
Silent almost not visible crash. Blue blurred line of about 50 px wide was displayed over the bottom panel of the screen. Re-edit the panel from always visible to auto-hide and than back removes that blue blurred line.


STEPS TO REPRODUCE
1. Edit visibility of bottom panel: auto-hide to always visible and back and at some point got crash.

OBSERVED RESULT
invisible crash (present in journalctl)

EXPECTED RESULT
journalctl free of crash

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.12.0-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-8259U CPU @ 2.30GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics 655

ADDITIONAL INFORMATION

Core dumped:

```
$ gdb /usr/bin/plasmashell core.plasmashell.1000.2a432adc973e4c8f899593a9f19064d3.825.1615999771000000
...
[New LWP 6661]
[New LWP 10097]
[New LWP 20507]
Warning: couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error
Warning: couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error

warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
--Type <RET> for more, q to quit, c to continue without paging--
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f5f6177def5 in raise () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f5f5d1bc280 (LWP 825))]
(gdb) bt
#0  0x00007f5f6177def5 in raise () at /usr/lib/libc.so.6
#1  0x00007f5f6177df80 in <signal handler called> () at /usr/lib/libc.so.6
#2  0x00007f5f618a5566 in __memmove_avx_unaligned_erms () at /usr/lib/libc.so.6
#3  0x00007f5f621cb917 in QImage::copy(QRect const&) const () at /usr/lib/libQt5Gui.so.5
#4  0x00007f5f61410582 in  () at /usr/lib/libKF5KIOWidgets.so.5
#5  0x00007f5f61dd9d86 in  () at /usr/lib/libQt5Core.so.5
#6  0x00007f5f5f954845 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () at /usr/lib/libKF5KIOCore.so.5
#7  0x00007f5f61dd9d86 in  () at /usr/lib/libQt5Core.so.5
#8  0x00007f5f5f930ad3 in KIO::SlaveInterface::data(QByteArray const&) () at /usr/lib/libKF5KIOCore.so.5
#9  0x00007f5f5f932f8d in KIO::SlaveInterface::dispatch(int, QByteArray const&) () at /usr/lib/libKF5KIOCore.so.5
#10 0x00007f5f5f93129a in KIO::SlaveInterface::dispatch() () at /usr/lib/libKF5KIOCore.so.5
#11 0x00007f5f5f934d9b in KIO::Slave::gotInput() () at /usr/lib/libKF5KIOCore.so.5
#12 0x00007f5f61dd9d86 in  () at /usr/lib/libQt5Core.so.5
#13 0x00007f5f61dcf532 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#14 0x00007f5f62a41752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#15 0x00007f5f61da2a2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#16 0x00007f5f61da5523 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#17 0x00007f5f61dfc054 in  () at /usr/lib/libQt5Core.so.5
#18 0x00007f5f60187b84 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#19 0x00007f5f601dbc21 in  () at /usr/lib/libglib-2.0.so.0
#20 0x00007f5f601863b1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#21 0x00007f5f61dfb691 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#22 0x00007f5f61da13ac in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#23 0x00007f5f61da9844 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#24 0x0000563b70b3320b in  ()
#25 0x00007f5f61768b25 in __libc_start_main () at /usr/lib/libc.so.6
#26 0x0000563b70b3333e in  ()
(gdb) 

```
Comment 1 Nate Graham 2021-03-18 16:58:31 UTC
#4  0x00007f5f61410582 in  () at /usr/lib/libKF5KIOWidgets.so.5
#5  0x00007f5f61dd9d86 in  () at /usr/lib/libQt5Core.so.5
#6  0x00007f5f5f954845 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () at /usr/lib/libKF5KIOCore.so.5
#7  0x00007f5f61dd9d86 in  () at /usr/lib/libQt5Core.so.5
#8  0x00007f5f5f930ad3 in KIO::SlaveInterface::data(QByteArray const&) () at /usr/lib/libKF5KIOCore.so.5
#9  0x00007f5f5f932f8d in KIO::SlaveInterface::dispatch(int, QByteArray const&) () at /usr/lib/libKF5KIOCore.so.5
#10 0x00007f5f5f93129a in KIO::SlaveInterface::dispatch() () at /usr/lib/libKF5KIOCore.so.5
#11 0x00007f5f5f934d9b in KIO::Slave::gotInput() () at /usr/lib/libKF5KIOCore.so.5
#12 0x00007f5f61dd9d86 in  () at /usr/lib/libQt5Core.so.5

Backtrace is missing some symbols. Can you rebuild kio and kio-widgets with debug symbols and get a new backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Arch-based_distros_.28Arch.2C_EndeavourOS.2C_Manjaro.29

Also do you know what you were doing at the time? Were there any file move/copy operations or any drag-and-drop tasks, or anything like that?
Comment 2 Bug Janitor Service 2021-04-02 04:33:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2021-04-17 04:33:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!