In order to get sizeable scrollbars I set/choose `oxygen` in "systemsettings5/Appearances/ Application Style/Widget Style" afterward click "Configure" to increase thickness of scrollbars.

`systemsettings5` sometimes freeze = don't appear/cannot click "Apply", sometime don't accept changes = going to other settings and back still show "Breeze" instead of "Oxygen" even if "Apply" was clicked, and sometimes just crash it = simply close (systemsettings5).

This happens for all if I start `sudo -i systemsettings5` but even as user over `kickoff` as user. To reproduce/see the error I start booth in the CLI, here the Error-line-s:

Code: Select all

Plugin changed to:  "org.kde.oxygen"
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so" instead.


My system:

Code: Select all

OS: Ubuntu 18.04.4 LTS x86_64
Host: MS-7B09 1.0
Kernel: 5.3.0-53-generic
Shell: bash 4.4.20
Resolution: 3840x2160
DE: KDE
WM: KWin
WM Theme: Oxygen
Theme: Breeze Dark [KDE], Breeze-Dark [GTK2/3]
Icons: Breeze-dark [KDE], Breeze-dark [GTK2/3]
Terminal: konsole
Terminal Font: Noto Mono 18
CPU: AMD Ryzen Threadripper 1900X 8- (16) @ 3.800GHz
GPU: AMD Radeon RX Vega 64


Please tell me if additional input from my side are required for detecting and solve the problem or the command i should input to get information or...
knowing anyone the problem and can tell me how to solve it?

Thanks a lot in advance and best regards.

Hi!

Do never use sudo guiprogram, sudo is no solution, it is an administration tool for command line (there are ways to use it with graphical programs, but not this way). Check you user permissions in homefolder:

Code: Select all

find $HOME ! -user $USER -ls

If there is no output, everything is fine. Else you have to correct your users permissions.

koffeinfriedhof wrote:Hi!

Do never use sudo guiprogram, sudo is no solution, it is an administration tool for command line (there are ways to use it with graphical programs, but not this way). Check you user permissions in homefolder:

Code: Select all

find $HOME ! -user $USER -ls

If there is no output, everything is fine. Else you have to correct your users permissions.

Hallo Koffeinfriedhof,

Once we had kdesudo, than we could create/manipulate pkexec, and now? Is there an alternative?

Sadly, if a user want to change color-theme (even the standard one) from breeze to breeze-dark or have to Scale Display for apps like [i]krusader[i], [i]synaptic[i], etc. we have not other chance. Even [i]qt5ct[i] must be started twice, one from [i]kickoff[i] and one with [i]sudo -i qt5ct[i]. The only alternative is to get a [i]systemsettings5[i] that assign the adjustments to complete system, but, apparently, is not possible. With kubuntu 20.04 is also not possible to make the adjustments contemporarily as user and root = start one from kickoff and one over konsole. Systemsettings5 become more and more inconsistent and buggiest.

Besides my nagging, how to detect errors if apps can no longer start in the konsole?

I have endless output issuing the command, can you tell me how to remedy/correct this?

Thanks anyway for your feedback.

I find the Solution here

If issuing following command:

Code: Select all

find $HOME ! -user $USER -ls


...you get any "output", than correct with following command:

Code: Select all

sudo chown -R $USER:$USER /home/$USER


...now check again with the first command if everything going well

Thanks again to "koffeinfriedhof"

advantagedtony wrote:Once we had kdesudo, than we could create/manipulate pkexec, and now? Is there an alternative?

Depending on what you want to do and how your system is set up:: Yes.

Normally, there is no need to run any graphical program as root, as root is only to set up your system or to make major changes. If you are not handy with terminal and vim/emacs/nano/… there are options to save your users files from being owned by root.
At first: If you want to edit a file in e.g. /etc/, you can just open it with kate, edit it, and on saving, the PolicyKit / PolKit will popup a permission-request asking for your password, or list another user with appropriate rights - asking for his password. The only files you cannot edit this way are those, hidden from normal users, like the sudoers configuration (available via sudo visudo) or similar, as you cannot see them browsing the filesystem.

The problem with graphical programs: On start, a program looks up its configuration saved in ~/.config, its other files in ~/.local/share, … and so on. (These folders are defined via xdg-user-dirs and depend on what you have set up there). If you start this program with sudo, it will change the owner, and perhaps the group, to root, as this user changes the settings by moving the window to another position, clickling something, etc.. No problem to take over the ownage of your files, its root. But your user does not have any rights on these files anymore.

sudo itself is to start any program as (mostly) any user available on your system. Without giving a username, it automatically takes the root-account (uid 0). You can start a graphical program with sudo -H program which will set the HOME-Variable to the taken users one, but only $HOME. So there is still a chance to crash some permissions. So you may start a programm with sudo -H but you have to know what you are doing - and now you know how to fix it And: You often do not change your users settings, but the ones for root.

Besides my nagging, how to detect errors if apps can no longer start in the konsole?

You always can run apps via konsole. But do not use sudo with it Start them as your user.