[Bug] If left empty, zone labels get recreated when upgrading PlasmaZones

[pairomaniac]

Description

When you upgrade the app, if your zones don't have labels (I tend to leave the fields empty) they are replaced with the default values e.g. Zone 1, Zone 2, Zone 3.

I use the rpm from COPR if that makes a difference.

Expected Behavior

Either don't have the upgrade process replacing the values, or have a toggle for disabling zone labels, since you can already disable the numbers.

Steps to Reproduce

1. Create a layout with zones without a label
2. Upgrade PlasmaZones
3. Check the labels of that layout

PlasmaZones Version

2.0.2

Display Server

Wayland

Desktop Environment

Plasma 6.6.2

Distribution

Fedora 43

Relevant Logs

No response

Configuration

No response

Checklist

• I searched existing discussions and issues
• I can reproduce this with default settings

[fuddlesworth]

This might be due to the other bug I fixed in a previous version where system layouts were getting automatically copied to local directory.

[pairomaniac]

It seems like it, after another clean install (everything removed from the home folder) I no longer had the issue.

However I did have quite a lot of woes upgrading to 2.1.0 - pretty much everything was broken from the get go. I removed my 2.0.2 config and rebooted once more, seemed to help. Issues such as forced auto-tiling, shortcuts weren't working etc.

I did notice that when clicking the Edit button from the Layouts menu, it doesn't seem to pick the monitor it's set to, or your actual primary monitor:

maalis 14 20:04:26 pingu plasmazonesd[2662]: Launching editor "for layout: {a02bb39b-9a9f-4436-97db-1b8f3d644ceb} on screen: HDMI-A-2"
maalis 14 20:04:27 pingu plasmazones-editor[6985]: Loaded 18 shaders
maalis 14 20:04:29 pingu plasmazonesd[2662]: Saved state to KConfig: zones= 2 pending= 2 preTile= 6 preFloat= 1 userSnapped= 4

Also clicking Open Layouts Folder gives the following error:

[pairomaniac]

The Layout Editor itself opens to the correct screen when using the Application or a Hotkey shortcut.

[fuddlesworth]

I did extensive rewrites of the configuration and virtual desktop handling. Getting virtual desktops working with mode switching uncovered a rabbit hole of old bad code. So yeah old configs might not work sadly (hence the warning in the release notes). However it was needed to get everything working properly without hacks.

I'll take a look at the other issues though

[fuddlesworth]

Fixed both issues in v2.2.0

[pairomaniac]

Awesome, I was able to do the changes with the manual selection. I do still wonder if it's picking the primary monitor from the correct place? Since I have my Samsung monitor as primary.

[fuddlesworth]

Looks like QT's library call doesn't match KDE's handling of primary screen and that's what the problem is.

[fuddlesworth]

Try v2.2.1. If this doesn't fix it, i'll just have to remove the primary stuff.

[pairomaniac]

Yup that did the trick!