Just installed Opensuse Plasma on my Surface GO. Everything is working beautifully. Except YAST: YAST is ignoring my Plasma Font Settings. I’ve opted to increase the Font sizes rather than scale the desktop. (Scaling the desktop has produced mixed results depending on the application.) The problem is that YAST’s Font Size is about 4. Is this a GTK setting somewhere?
EDIT: Okay, I’m realizing that I have to edit the font settings as superuser since YAST is running under that profile, but how to invoke systemsettings as su?
I have KDE so here it is: “Alt+F2 => kdesu systemsettings5”
As you mention GTK I assume you are on GNOME? Then it would be “Alt+F2 => gksu gnome-control-center”. (Disclaimer: I asked the duck for GNOME commands. Others, like “unity-control-center” may be required.)
I don’t know in other DE’s. However, “Alt+F2” should work anywhere, AFAIK. It won’t work from terminal as it can’t find the proper environment variable.
First of all, glad if it worked. However, AFAIK this:
had you start the DE as root. That is very dangerous, as you may mess up a lot of other things. That’s why I suggested the Alt+F2 etc. Just for the record.
Yeah. Unfortunately “kdesu systemsettings5” just didn’t/doesn’t work on my system, whether issued in krunner or the terminal. Seems to be broken. That is, nothing pops up.
(This was one of the first solutions I tried.)
If that works for the next person, then that’s probably “safer”. Other than that, starting an X session as Root is probably only midly more dangerous than su commands at terminal.
The one thing I would add in my instructions:
If one is stuck in a TTY, go to a different TTY (ctrl-alt-F2-F6), login under ones username and issue the command to reboot as follows:
sudo shutdown -r now
Edit: Incidentally, I’m using Plasma. I mentioned GTK because I wasn’t sure if YAST was a GTK app. I didn’t think so, but was trying all possibilities.
Well, I’m not the specialist on this but others might object more “fiercely”. As far as I get it actually logging in to the DE as root may start processes, save settings etc. that you are not aware of and subsequently may cause trouble. Even if I’m the only user I learned to avoid it.
However, it seems strange to me that systemsettings5 wouldn’t start as root in your system. I just double checked, and I have to correct myself. It won’t work in terminal with sudo but after
su -
it came up. Does it start as normal user at all?
If it is still of interest you might post the full command and return when starting
kdesu systemsettings5
from a terminal in the X session (e.g. konsole) after becoming root. Otherwise,
Just found my error. I was wondering why “kdesu systemsettings5” wouldn’t work in terminal and tried again. My fault: I have tried it in an SSH session on my home server. Apparantly that won’t work. On my local machine it starts without issue.
Sorry, I can’t edit my first post anymore. Hopefully,anybody searching will read the post to this end! :shame:
QT5’s qt5ct is the standard configurator of font sizes for YaST2, while the foundation of KDE/Plasma is also QT5. Thus, YaST2 would be expected to use a normal user’s own QT settings. However, since YaST2 is normally run as root, it relies on root’s configuration. From Alt-F2, Konsole or other X terminal you can run yast2 in normal user mode, from which it will use normal user’s settings, and be severely restricted in what it can do.
It has no impact on any ordinary user’s settings to login as root and run startx. The primary danger of running X as root is the power it has to expose that which should not be exposed, and the damage possible in the hands of the inexperienced and unlearned. A mere mortal running as root can cause a lot of damage through ignorance. With adequate knowledge and wisdom, X as root poses nominal danger, which is severely reduced by avoiding internet exposure. Thus, startx logged in as root long enough to run qt5ct and exit poses zero practical risk.
