Bug 487800 - Plasm shell crashes after I eject Extenal SD card reader
Summary: Plasm shell crashes after I eject Extenal SD card reader
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.0.4
Platform: Manjaro Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-05-30 16:24 UTC by Bohdan Mart
Modified: 2024-06-29 03:47 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (68.26 KB, text/plain)
2024-05-30 16:24 UTC, Bohdan Mart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bohdan Mart 2024-05-30 16:24:14 UTC
Application: plasmashell (6.0.4)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.1.90-1-MANJARO x86_64
Windowing System: Wayland
Distribution: Manjaro Linux
DrKonqi: 6.0.4 [CoredumpBackend]

-- Information about the crash:
I've isnterted SD card reader. Opened it in Dolphin. copied some files. ejected it using unplug button in Dolphin.

Plasm shell crashed, but dolphin don't.


It reproduced twice in a row. 

Bus 003 Device 021: ID 0483:5720 STMicroelectronics Mass Storage Device

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  0x00007f839aaad51d in Plasma::Theme::~Theme() () at /usr/lib/libPlasma.so.6
#5  0x00007f837f448d45 in ??? () at /usr/lib/qt6/plugins/kf6/kirigami/platform/KirigamiPlasmaStyle.so
#6  0x00007f839838a39b in QObjectPrivate::deleteChildren() () at /usr/lib/libQt6Core.so.6
#7  0x00007f839838e6f0 in QObject::~QObject() () at /usr/lib/libQt6Core.so.6
#8  0x00007f83820d2baa in ??? () at /usr/lib/qt6/qml/org/kde/ksvg/libcorebindingsplugin.so


Reported using DrKonqi
Comment 1 Bohdan Mart 2024-05-30 16:24:15 UTC
Created attachment 169990 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 fanzhuyifan 2024-05-30 17:54:59 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols that we need to figure out exactly what's going wrong.

Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this.
Thanks again!
Comment 3 Bug Janitor Service 2024-06-14 03:47:16 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 4 Bug Janitor Service 2024-06-29 03:47:38 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!