Bug 485954

Summary:	plasmashell crashes after editing panel widgets
Product:	[Plasma] plasmashell	Reporter:	Richard Albrecht <albrecht0xff>
Component:	Panel	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	akselmo, nate, niccolo.venerandi
Priority:	NOR
Version First Reported In:	6.0.4
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	journald log output after editing panel widgets crash and plasmashell restart output after ten minutes of stucking

Description Richard Albrecht 2024-04-22 12:06:06 UTC

SUMMARY
Plasmashell crashes after editing panel widgets

STEPS TO REPRODUCE
1. switch to KDE 6 (wayland)
2. add some widgets or edit one of the widgets on the panel

OBSERVED RESULT
plasmashell reported a lot of errors and then got stuck and crashed
then after about ten minutes, plasmashell restarted, and then everything was normal.

EXPECTED RESULT
nothing ever happens

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed, KDE Plasma 6.0.4, wayland
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

Comment 1 Richard Albrecht 2024-04-22 12:10:05 UTC

Created attachment 168792 [details]
journald log output after editing panel widgets

Here is journald log output after editing panel widgets (for example, cpu usage monitor widget)

then plasmashell got stuck, it cannot be killed via `killall plasmashell` or `kquitapp6 plasmashell`

Comment 2 Richard Albrecht 2024-04-22 12:12:58 UTC

Created attachment 168793 [details]
crash and plasmashell restart output after ten minutes of stucking

And here is crash and plasmashell restart output after ten minutes of stucking

Comment 3 Richard Albrecht 2024-05-11 05:18:02 UTC

This bug is still not fixed, today when I click the system monitor widget on the panel, plasmashell stuck again, and using kuitapp6 cannot stop it, here is kuitapp6 output:

richard@Albrecht0xff:~> kquitapp6 plasmashell
"Quitting application plasmashell failed. Error reported was:\n\n     org.freedesktop.DBus.Error.NoReply : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

Comment 4 Akseli Lahtinen 2024-06-10 13:37:10 UTC

Hi, can you install debug symbols and paste the backtrace with them installed? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Backtraces

Thanks!

Comment 5 Nate Graham 2024-07-31 03:52:16 UTC

Comment 6 Bug Janitor Service 2024-08-15 03:47:06 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

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

Comment 7 Bug Janitor Service 2024-08-30 03:48:02 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.