We then should at least offer an easy "reset panel to factory defaults" button to have the users reset their config.
There is the tool called xfce4-panel-profiles in the X11:xfce repo that can back up panel configs and restore them. But as Stefan pointed it out, in some cases it fails. https://bugzilla.xfce.org/show_bug.cgi?id=14934
OTOH, if knowledgeable Users like Manfred do not test from there, we'll ship these bugs unnoticed to Factory/Tumbleweed, so it's good that at least someone is testing the "unreleased" code ;-)
Indeed! I wouldn't have noticed it if Manfred didn't bring it up and I
appreciate that :-)
Maurizio Galli (MauG)
On Sun, Dec 16, 2018 at 7:37 PM Stefan Seyfried
Hi all
Am 16.12.18 um 12:02 schrieb:
Hello Mafred, First of all thanks for bringing up the bug. When you modify your panel, configs are stored here: .config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml. If the plugins IDs in that config file don't match the file in the root directory, the panel fails to load them or mistakes them for something else.
The new update restores the correct ID numbers as they were before the "bad" update. However, if meanwhile you modified the panel, this update breaks your config again because the plugins would be using a different ID again. This was the reason I suggested in Factory ML to wait for the fix before updating.
I was thinking about these problems when I last modified the panel xml file to add the statusnotifier plugin and the xfce4-notifyd notification plugin.
A problem is, that if we have used plugin IDs 1-10 before and now add plugin 11 and 12, but the user had already added id 11 by configuring an additional plugin, then there might be trouble.
I had envisioned to use higher IDs for the "factory shipped" configuration, say, starting at ID=100 (or 256 or whatever).
The drawback is, that this would break updates for sure. We then should at least offer an easy "reset panel to factory defaults" button to have the users reset their config.
Please keep in mind that repos like X11:xfce are for development and the packages there are be considered as "experimental".
OTOH, if knowledgeable Users like Manfred do not test from there, we'll ship these bugs unnoticed to Factory/Tumbleweed, so it's good that at least someone is testing the "unreleased" code ;-)
Have fun,
Stefan -- Stefan Seyfried
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-xfce+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-xfce+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-xfce+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-xfce+owner@opensuse.org