SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's always good to have a color scheme reminding you when you are running something as root during your user session, I know several people who do this as well.
@IlyaK, the content of ~/.config/xfce4 is the same for both root and guest user, so that's not the cause of the issue.
@rkelsen, the problem is that many times I log as guest and want to run a root instance of a given program (thunar or terminal, for instance).
@deNiro and @dugan, it's a bit fatter if you open both images in their original sizes. Both guest and root accounts have the same font configuration -- I double checked on xfce settings -> appearance -> fonts
@upnort, thanks for your tip. I tried but it doesn't fix this issue, even adapting '<dir>/usr/local/share/fonts</dir>' to '<dir>/usr/share/fonts</dir>', which is where the fonts are actually located here. I used your original config file content and then adapted to this:
But it doesn't work. I'm not sure if this is really the way to fix it because if I open xfce settings -> appearance -> fonts the settings are the same for both guest and root.
Maybe I wasn't clear in my first post. The problem is booting as guest and then opening a given program as root.
Lets check how fontconfig resolves font pattern used by your app.
For example I use ``xterm`` and have ``fontFace`` set to ``mono``. So, I do:
Code:
$ fc-match --verbose mono
Output includes hinting, hintstyle, font name, and other stuff.
You may do the same for font your app uses and see if output is the same.
>Maybe I wasn't clear in my first post. The problem is booting as guest and then opening a given problem as root.
So, you simply open terminal and type something like ``sudo`` ?
And, yes, I open the terminal (as guest) and type:
Code:
sudo xfce4-terminal
So now I have a root instance of the terminal and check the fat font. I can do the same for thunar or whatever. And, as I said, this also applies to other DEs, like LXDE and LXQt, for instance.
And, yes, I open the terminal (as guest) and type:
Code:
sudo xfce4-terminal
So now I have a root instance of the terminal and check the fat font. I can do the same for thunar or whatever. And, as I said, this also applies to other DEs, like LXDE and LXQt, for instance.
Just for future reference. You should never open a root app with just using sudo. It can change the owner of your user's files to root and can break things. You should use kdesu if you have a full Slackware install or gksu from SBo. This ensures that root won't screw up the user's file permissions.
And it's very possible that using kdesu or gksu might not have the problem you're seeing with fonts, so definitely give it a try.
You may also want to check and see if there's any root owned files in your user's directory. As your regular user, run the following:
@bassmadrigal, thanks for the tip. Actually I'm one of Porteus devs I access root instances of thunar, terminal, etc through other ways (shortcuts that call scripts that call gksu). I was just trying to simplify things here. And, no, it doesn't make any difference calling them using sudo or gksu regarding the font issue.
Well, if I were actually curious about this (and I wouldn't be; just don't ignore the advice to not run as root!), I would start by comparing the graphical font rendering settings in Xfce, between the root and user accounts. Then I would look in /etc/skel to see if it adds anything to the user accounts that could be relevant.
Font settings propagate from the desktop environment to X11, GTK, and Freetype. Each presents new opportunities to get the settings wrong. I suspect the discrepancy is in the GTK layer.
Ed
May I throw my hat into the ring? Although Slackware is a multi-user OS I am the only user. It is my computer and I am the only one that is even interested in using it. The only other person in this house is my wife and she has her own Windows computer and also has a MAC.
Run as root user? In my case, no problemo
I feel like you're trolling. A user as experienced as yourself should know the answer to that. This has been discussed to death over the years. You can easily find lots of discussion about this topic on the internet, and it is generally inexperienced users asking the question.
If you need root access while in the GUI, open a terminal and use su or sudo to do whatever you need to do. In >20 years, I've not had many problems which couldn't be fixed this way. I can't recall any right now, but there were probably some.
Anyhow, each to their own, and with home routers being tightly locked down by default these days it probably doesn't matter as much. But there is still an element of risk. Some people don't like being protected from themselves. I don't mind it.
I'd probably cop the same flak for saying that I don't run anti-virus software... Haven't needed it since I started using Linux. My system, my risk.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.