Bug 417509 - Adding default panel while using a vertical panel crashes plasmashell and prevents it from launching again
Summary: Adding default panel while using a vertical panel crashes plasmashell and pre...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.18.0
Platform: Other Linux
: VHI critical
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-12 18:24 UTC by Nate Graham
Modified: 2020-02-20 19:34 UTC (History)
1 user (show)

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

Attachments
Broken config file (21.27 KB, text/plain)
2020-02-12 18:24 UTC, Nate Graham 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2020-02-12 18:24:19 UTC 
Created attachment 125910 [details]
Broken config file

Everything from git master, but reproducible in Plasma 5.18 too


STEPS TO REPRODUCE
1. Have a vertical panel on the left side with an IOTM in it
2. Right-click on that panel > Add Panel > Default Panel


OBSERVED RESULT
Plasmashell crashes and does not start again


EXPECTED RESULT
It works


ADDITIONAL INFORMATION
If I manually edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc and remove all traces of the newly-added default panel, plasma starts again. However if I was a regular user and did not know how to do this, my conclusion would be that the system was irreparably broken and I would never want to use it again.

I'm attaching the plasma-org.kde.plasma.desktop-appletsrc file that makes plasma crash and be unable to launch.
Comment 1 David Edmundson 2020-02-20 18:50:53 UTC 
Running that config file loaded fine for me

If you can reproduce, can I have a backtrace please.
Comment 2 David Edmundson 2020-02-20 18:54:02 UTC 
and include plasmashellrc 

it contains the panel sizes
Comment 3 Nate Graham 2020-02-20 19:34:47 UTC 
I am no longer able to reproduce the issue, though it was 100% reproducible the other day. :( Will re-open and attach more info if it happens again.