Bug 436669 - SDDM theme synchronization is not working
Summary: SDDM theme synchronization is not working
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_sddm (show other bugs)
Version: 5.21.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-06 04:28 UTC by Lua
Modified: 2021-05-18 00:33 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lua 2021-05-06 04:28:20 UTC
SUMMARY


STEPS TO REPRODUCE
1. Change the color scheme in System Settings > Colors;
2. Go to System Settings > Startup/Shutdown > SDDM > Synchronize Settings;
3. Logout

OBSERVED RESULT
The synchronization won't happen.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-16-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
ADDITIONAL INFORMATION
Comment 1 David Edmundson 2021-05-07 10:15:05 UTC
Please confirm by looking at: /var/lib/sddm/.config/kdeglobals

and comparing to your own

Please also include output of kcmshell5 sddm and syncing settings
Comment 2 Lua 2021-05-07 21:24:05 UTC
cd /var/lib/sddm/.config/kdeglobals: permission denied, but the sddm folder exists. I can't access the root terminal either.

kcmshell5 sddm
kf.coreaddons: Two plugins with the same interface( QObject ) were registered. Use keywords to identify the plugins.
kf.i18n: "0 instead of 3 arguments to message {%1, by %2 (%3)} supplied before conversion."
kf.i18n: "0 instead of 2 arguments to message {%1 (%2)} supplied before conversion."
Cannot find cursor theme value.
Cannot find scaling DPI value.
Synchronization successful
Comment 3 Lua 2021-05-18 00:33:56 UTC
It's working now. I think I was doing something wrong.