Bug 477669 - Plasmashell sometimes crashes when panel edit mode is exited
Summary: Plasmashell sometimes crashes when panel edit mode is exited
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.27.80
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-11-28 11:41 UTC by 31113
Modified: 2023-11-29 14:52 UTC (History)
2 users (show)

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


Attachments
What drkonqi-coredump-gui let me copy to clipboard (40.36 KB, text/plain)
2023-11-28 11:41 UTC, 31113
Details

Note You need to log in before you can comment on or make changes to this bug.
Description 31113 2023-11-28 11:41:15 UTC
Created attachment 163568 [details]
What drkonqi-coredump-gui let me copy to clipboard

SUMMARY
changing the panel's width from custom to any of the other options or from the other options to custom and then clicking on the desktop sometimes crashes plasmashell. Can be avoided when, instead of clicking on the desktop, one exits edit mode by clicking on the exit edit mode button on top.



STEPS TO REPRODUCE
1. Change panel width to custom
2. exit edit mode
3. chenge panel width to fill width
4. click on empty space on desktop

OBSERVED RESULT
plasmashell crashes. change to panel width is not saved

EXPECTED RESULT
plasmashell doesn't crash. (and I always expect that to exit the edit mode, but i don't know if that's what should happen.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.1
Kernel Version: 6.6.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-4130 CPU @ 3.40GHz
Memory: 3,3 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4400

ADDITIONAL INFORMATION

I have kde-unstable and extra-testing enabled in pacman.conf

I already let drkonqi report this automatically, but I thought a description of my actions that led to the crash might be more useful.
Comment 1 Nate Graham 2023-11-28 21:16:26 UTC
Cannot reproduce. I think you might be missing a step between 2 and 3, since you can't change the panel back to "Fill Width" mode without re-entering edit mode, but the way that you did that wasn't specified. Can you clarify? Thanks!
Comment 2 31113 2023-11-28 22:16:13 UTC
(In reply to Nate Graham from comment #1)
> Cannot reproduce. I think you might be missing a step between 2 and 3, since
> you can't change the panel back to "Fill Width" mode without re-entering
> edit mode, but the way that you did that wasn't specified. Can you clarify?
> Thanks!

I right click the panel and enter edit mode. I just now managed to recreate the crash by just entering and exiting the edit mode a couple of times, without changing the width or any option. 

Also I just noticed I don't have debug symbols on my system, so the txt I attached is probably worthless? Sorry for that, I'm trying to fix that but I don't have enough space on my root partition. (What does that mean for the automatic report btw?)
Comment 3 31113 2023-11-28 23:23:15 UTC
Okay, sadly you can't edit here. The root partition is of course completely unrelated, that was a separate warning that popped up. 

The problem is actually that gdb takes too much ram to run on my system, so when I recreate the crash and then click on "see developer information" and then on "install debug symbols", after a while drkonqi gets killed by systemd-oomd or my computer completely freezes and I have to restart. I've tried increasing the swap twice with no successs, at this point idk what to do. I can't exactly download more ram.
Comment 4 31113 2023-11-29 14:25:42 UTC
I just made a fresh account to see if it still happens without my configs and, yes, it still happpens. 

But I also just downloaded kde neon unstable and live booted that and I can't reproduce the issue on neon. 

So either I messed up something deeper than the configs in my home folder, or it's a packaging issue with Arch or some commit that didn't yet make it to the arch kde-unstable repo, but is already included in the neon unstable iso from today, fixed the issue.
Comment 5 Nate Graham 2023-11-29 14:52:41 UTC
Yep, I suspect Arch packages are just a bit behind and don't include the new code changes that fixed it (first time I've ever said that!).