for portability you can use konsave or plasma-config-saver sort of things.
I still do not understand why you would run gui apps as root because there is polkit and that is not possible by default on wayland and that is not supported either.
(all kde apps (except dolphin) have good polkit integration)
Thanks for your comment.
I use openSUSE and every YAST settings module has a GUI and runs after asking for the root password. In my case I suffer bad eyesight and cannot read the non custom themed version.
Please do not assume that your use case solutions are suited for me. If I wanted to use CLI modules I wouldn't ask for "kdesu" applications.
The "kdesu" command is an official integral part of KDE Plasma and I would like to use it. But that's of no use to me if the GUI's created by "kdesu" are tiny, differently colored and low contrast Guis. So I ask whether there is a solution to apply my theme customizations to the root account. For example in the same manner than I can apply theme modifications to the KDE login page (SDDM) by a simple one-click "apply theme modifications to login page"...
But thanks for mentioning konsave - I will look into that!
p.
Oh I see your usecase and sorry for wrong assumptions.
> The "kdesu" command is an official integral part of KDE Plasma
It is more of a remnant from the past though. Back when polkit was not there/really adopted.
The main issue is with YAST. They should move to polkit by now.
Meanwhile what you can do is to use konsave or similar tools to backup .config files ("dotfiles") and note which files are saved. Then write some script/rsync with maybe a periodic timer to copy them to `/root/.config`. Or do it manually.
I do not know about any tool that does this automatically.
Thanks.
I have to play around a bit with konsave before I really trust it not to break stuff. But periodically backing it up to my server seems a good idea... (I do that any way, so...) - I work on three machines at different locations - this way I could pull in the configurations when updated.
For just syncing the color theme locally this is my solution right now:
The custom color schemes are located in "\~/.local/share/color-schemes"... - so now I just created a symlink in the root user's directory to my user color scheme and then applied it once for root.
I am often fiddling around with the color settings to eek out a bit more readability and less strain - every change I make gets immediately applied to the next tome I use a root session (mostly Yast!). I hope that doesn't create any problems down the line - at the moment I am happy with it.
Also I have to say I never found it useful that KDE systemsettings is able to highlight all changed settings... but now it's useful to cycle through all custom settings in one window and apply them to another user account.
Though I still think KDE should integrate a solution for saving all customizations in one profile file at once that can be applied as is or selectively to another profile.
I have to admit I like yast. A lot. I used Arch before and after a few years I just didn't know anymore which files I edited either in user space or system wide to achieve a certain behavior. Short term it's great but after a while I got lost. Also things things changed... - you really do not want to know how many conf and env entries and tweaks I used to get the scaling I needed - and then some of these files would be ignored, renamed or splitted up. Really hard to keep track...
Maybe it's just me not being organized enough but I really like the organization Yast offers - if this could be done without kdesu in a more modern way - I am with you!
I just hope there will still be GUIs to offer a organized overview over the core settings of the system - I think I remember Fedora having quite a few problems pioneering Polkit... but that's been years ago - so maybe you are right and it offers a better approach now.
We'll see. Cheers,p.
p.s.: Oops, long post...
Don't get me wrong. YAST is a nice tool to manage and configure the system, all from one place. But on a modern system as we're approaching image-based (coreos, ignition) or config based (nixos) more robust systems, such configuration is itself outdated. In these scenarios the modifications you do to system are supposed to be reproducible and won't require to configure each time.
(I haven't used YAST in a year or so, can't tell if options have been changed.)
Nah... Yast is still the same...
But you have a good point there: Reproducibility of full or partial system configurations really is needed! Didn't know about Nixos... interesting....
p.
Unfortunately the days of user controlling the software is long gone and (Linux) developers become the ones deciding what user can and can't do. Sounds familiar?
for portability you can use konsave or plasma-config-saver sort of things. I still do not understand why you would run gui apps as root because there is polkit and that is not possible by default on wayland and that is not supported either. (all kde apps (except dolphin) have good polkit integration)
Thanks for your comment. I use openSUSE and every YAST settings module has a GUI and runs after asking for the root password. In my case I suffer bad eyesight and cannot read the non custom themed version. Please do not assume that your use case solutions are suited for me. If I wanted to use CLI modules I wouldn't ask for "kdesu" applications. The "kdesu" command is an official integral part of KDE Plasma and I would like to use it. But that's of no use to me if the GUI's created by "kdesu" are tiny, differently colored and low contrast Guis. So I ask whether there is a solution to apply my theme customizations to the root account. For example in the same manner than I can apply theme modifications to the KDE login page (SDDM) by a simple one-click "apply theme modifications to login page"... But thanks for mentioning konsave - I will look into that! p.
Oh I see your usecase and sorry for wrong assumptions. > The "kdesu" command is an official integral part of KDE Plasma It is more of a remnant from the past though. Back when polkit was not there/really adopted. The main issue is with YAST. They should move to polkit by now. Meanwhile what you can do is to use konsave or similar tools to backup .config files ("dotfiles") and note which files are saved. Then write some script/rsync with maybe a periodic timer to copy them to `/root/.config`. Or do it manually. I do not know about any tool that does this automatically.
Thanks. I have to play around a bit with konsave before I really trust it not to break stuff. But periodically backing it up to my server seems a good idea... (I do that any way, so...) - I work on three machines at different locations - this way I could pull in the configurations when updated. For just syncing the color theme locally this is my solution right now: The custom color schemes are located in "\~/.local/share/color-schemes"... - so now I just created a symlink in the root user's directory to my user color scheme and then applied it once for root. I am often fiddling around with the color settings to eek out a bit more readability and less strain - every change I make gets immediately applied to the next tome I use a root session (mostly Yast!). I hope that doesn't create any problems down the line - at the moment I am happy with it. Also I have to say I never found it useful that KDE systemsettings is able to highlight all changed settings... but now it's useful to cycle through all custom settings in one window and apply them to another user account. Though I still think KDE should integrate a solution for saving all customizations in one profile file at once that can be applied as is or selectively to another profile. I have to admit I like yast. A lot. I used Arch before and after a few years I just didn't know anymore which files I edited either in user space or system wide to achieve a certain behavior. Short term it's great but after a while I got lost. Also things things changed... - you really do not want to know how many conf and env entries and tweaks I used to get the scaling I needed - and then some of these files would be ignored, renamed or splitted up. Really hard to keep track... Maybe it's just me not being organized enough but I really like the organization Yast offers - if this could be done without kdesu in a more modern way - I am with you! I just hope there will still be GUIs to offer a organized overview over the core settings of the system - I think I remember Fedora having quite a few problems pioneering Polkit... but that's been years ago - so maybe you are right and it offers a better approach now. We'll see. Cheers,p. p.s.: Oops, long post...
Don't get me wrong. YAST is a nice tool to manage and configure the system, all from one place. But on a modern system as we're approaching image-based (coreos, ignition) or config based (nixos) more robust systems, such configuration is itself outdated. In these scenarios the modifications you do to system are supposed to be reproducible and won't require to configure each time. (I haven't used YAST in a year or so, can't tell if options have been changed.)
Nah... Yast is still the same... But you have a good point there: Reproducibility of full or partial system configurations really is needed! Didn't know about Nixos... interesting.... p.
Unfortunately the days of user controlling the software is long gone and (Linux) developers become the ones deciding what user can and can't do. Sounds familiar?
I found this and it worked for me with Kubuntu 2204 to open the System Settings for root without a root profile: \`sudo -i systemsettings5\`.