Bug 466028 - Upgrading to KDE 5.27 resulted in older version of desktop
Summary: Upgrading to KDE 5.27 resulted in older version of desktop
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.27.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-18 19:19 UTC by Wyatt Childers
Modified: 2023-02-23 05:46 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wyatt Childers 2023-02-18 19:19:39 UTC
SUMMARY
When I updated my computer to 5.27, it reset my plasma layout to a layout I haven't had for months. Basically all my panel customizations since then have been reverted.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 62.0 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: ASUS

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-02-22 03:26:44 UTC
So in Plasma 5.27, we moved to a totally new multi-monitor system, which also entailed changing how monitors are bound to desktops. We added migration code to make it as seamless as possible, but unfortunately, due to how broken the previous system was, it's not possible for the migration code to handle everything perfectly, especially if the previous config data was in a weird or inconsistent state. Evidently in your case the migration code did not do the right thing. Sorry about that.

Can you find your missing desktop in the Manage Desktop and Panels window?

You access it by entering edit mode on the desktop and clicking on the "Manage Desktop and Panels" button in the toolbar that pops down from the top of the screen.
Comment 2 Wyatt Childers 2023-02-22 16:18:26 UTC
(In reply to Nate Graham from comment #1)
> So in Plasma 5.27, we moved to a totally new multi-monitor system, which
> also entailed changing how monitors are bound to desktops. We added
> migration code to make it as seamless as possible, but unfortunately, due to
> how broken the previous system was, it's not possible for the migration code
> to handle everything perfectly, especially if the previous config data was
> in a weird or inconsistent state. Evidently in your case the migration code
> did not do the right thing. Sorry about that.
> 
> Can you find your missing desktop in the Manage Desktop and Panels window?
> 
> You access it by entering edit mode on the desktop and clicking on the
> "Manage Desktop and Panels" button in the toolbar that pops down from the
> top of the screen.

Aha! I had no idea about this fancy "Manage Desktop and Panels" system; that's very neat! Yes, I was able to find it there; thank you!

I'm not sure if there's anything we could do to make the migration code better (for other fokls)? I *might* have the old state in a restic/could pull out some information (though I don't know where all of this is stored).
Comment 3 Nate Graham 2023-02-22 21:07:44 UTC
Thanks for the offer. Unfortunately it doesn't really help as the old state is inherently non-determinstic. That's why stuff was so bad before, especially with 3+ screens or a frequently-changing screen arrangement.
Comment 4 Wyatt Childers 2023-02-23 05:20:23 UTC
(In reply to Nate Graham from comment #3)
> Thanks for the offer. Unfortunately it doesn't really help as the old state
> is inherently non-determinstic. That's why stuff was so bad before,
> especially with 3+ screens or a frequently-changing screen arrangement.

The odd thing is, I was/am on a desktop, and never had any issues with the old way doing anything surprising; i.e., for me anyways it was very deterministic. Maybe this isn't the case, but because of that, it seems like the migration script should be able to handle this equally as well, no?
Comment 5 Nate Graham 2023-02-23 05:46:33 UTC
If your setup is simple, then yes, the old data would be helpful so we can improve the migration code.