Please explain your logic here. I don't think it confirms anything you're saying. XFCE will honour per-user settings for this stuff, where root gets system settings. If the two are different, well guess what happens.
I'm not wasting my time testing anything. I already know what the problem is and so do you. Dugan told you what it is in post #8.

@rkelsen, you're funny

You didn't mention checking the settings that are listed graphically xfce4-settings-manager, which is the first place I would look...

Apart from that? You've asserted, several times, that the configuration files are the same across accounts. At this point, no-one, including you, has any reason to believe that's true. Post console output showing your diff commands. You should be logging that information for your own investigations anyway.

And no, we're not going to install Porteus and log into its GUI as root (because that would be stupid) to help you with this.

@dugan, as I said, Porteus doesn't need to be installed, since it's a live distro. And again: the issue doesn't happen when booting into GUI as root, so you don't have to do that. Xfce settings are the same for both guest and root, as I told you many times, and it was confirmed by another user who actually downloaded the ISO and saw with his own eyes.

You can't help if you're not reading, sorry.

Thanks anyway

Have you been able to confirm this on an actual full-fledged Slackware install? That could help narrow down whether it is a Porteus specific issue or something all Slackware users would encounter.

1 members found this post helpful.

@bassmadrigal, this issue doesn't happen on Slackware. I know it's specific to Porteus. I just thought that you guys could help me because I clearly lack knowledge to solve it

Then you shouldn't be here. Go bother Porteus.

1 members found this post helpful.

The problem is we are not familiar with the Slackware derivative; we don't know how it is different from Slackware. I suggest that you move over to Slackware, fulalas. I think you may like it. If not, then enjoy your distro.

1 members found this post helpful.

> 'Go bother Porteus'

Hmmm... I thought that Linux, as an ecosystem, was more flexible/configurable, not this closed-distro-box.

Sorry for bothering you, guys.

Thanks anyway!

But you said in post #22 that you are a Porteus Developer. I just don't get it. Anyway, this thread started out off topic because the topic in this forum is Slackware. What did the other developers on the Porteus Forum say?

@Gordie, I'm a Porteus Developer, but I'm not god I know people here are treating me like a rookie but I don't care; I'm just trying to fix this issue. I have direct contact with other Porteus Developers, but we are a really small team, and regarding this issue no one has a clue, like people here -- it seems this issue is not trivial after all.

Hi there!

You may try adding this in /etc/gtk-3.0/settings.ini :

Assuming you want to use DejaVu Sans. Also the suggestions by Shruggy on post #50 might be useful: /home/guest/.config/gtk-3.0/settings.ini and /root/.config/gtk-3.0/settings.ini . Try them on /etc/gtk-3.0/settings.ini (I somehow suspect you may not have it: it would set the GTK+3 settings system-wide)

I have a feeling it's GTK+3 related, and that's in itself just another nice Pandora box. Good luck with that. And good luck with this experiment!

Those were not suggestions made by me. I just downloaded the Porteus LiveCD ISO provided by the OP in #32, unpacked it with 7-zip (on Windows, duh!) and looked inside. Those settings are what I found there. The PC I'm currently using is a 12 years old laptop and wouldn't allow running anything in a VM. If Porteus were changing any fonts related settings dynamically, during boot or login, I obviously couldn't check it.

@folkenfanel, thanks for your help. I tried this /etc/gtk-3.0/settings.ini:

It doesn't fix the issue. The other tip (/home/guest/.config/gtk-3.0/settings.ini and /root/.config/gtk-3.0/settings.ini) I tried before, but it doesn't help either.

At this point I'm trying anything, but I don't think this is GTK related because I see this issue on LXQt, which is Qt based.

Could it be that you are loosing some environment variable while doing sudo?

Try
..remove any sensitive information, and post result here

1 members found this post helpful.