https://bugs.kde.org/show_bug.cgi?id=445428
Duncan <1i5t5.dun...@cox.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |1i5t5.dun...@cox.net
--- Comment #2 from Duncan <1i5t5.dun...@cox.net> ---
User running most of kde/plasma live-git here, and I /think/ this may now be
fixed, by the following commit to plasma-framework (select-copied from git
log), not sure what release version it should appear in, but frameworks version
is reported as 5.89.0 ATM, here (with that commit), so should be in frameworks
5.89 if it didn't make 5.88 (which is what you reported). So if it's not fixed
in 5.89, a similar fix needs applied elsewhere.
In the mean time a couple workarounds.
1) Here, I've found running the following command from krunner saves
plasmashell config as it quits and restarts.
killall plasmashell; sleep 1; plasmashell
2) Judging by the comment in the git log below, another workaround may be to
add a panel and immediately remove it, thereby triggering plasma to save its
config.
* commit 1f0df3dd2
| Author: Jan Blackquill <uhh...@gmail.com>
| AuthorDate: Tue Oct 5 12:56:42 2021 -0400
| Commit: Jan Blackquill <uhh...@gmail.com>
| CommitDate: Tue Oct 5 13:04:48 2021 -0400
|
| Corona: save after ending edit mode
|
| Plasma can be somewhat amnesiac if you make changes to it that don't
| involve adding/removing panels and it subsequently unexpectedly ends,
| such as when it or the compositor crashes.
|
| Calling requireConfigSync after edit mode ends guarantees that any
changes
| made by the user in edit mode will be applied.
|
| src/plasma/corona.cpp | 4 ++++
| 1 file changed, 4 insertions(+)
--
You are receiving this mail because:
You are watching all bug changes.
