Re: /run/user/1000 errors

[Greg Wooledge]

On Thu, May 13, 2021 at 11:50:54AM -0700, Gary L. Roach wrote:
> When trying to install the Bacula backup system on my computer, I get the
> following error:
>
> *QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000
> instead of 0*

Well, that error message is wrong. The correct owner of /run/user/1000
is 1000, not 0.

What probably happened here is you logged in as your normal unprivileged
user (with UID 1000) and then used something like su to temporarily
gain elevated privileges -- but whatever method you used left some of
your regular user's environment variables intact.

These environment variables will refer to directories like /run/user/1000
which are yours, and not root's.

> I have noticed the same problem on other software packages. I have searched
> the internet for answers to this and have found dozens of cases with dozens
> of different ways to fix the problem, none of which seem to work for me.

As a first suggestion, it sounds like whatever you're doing expects
a complete login environment belonging to root, rather than one belonging
to you but with temporary powers granted.

So, try launching a complete root login environment with "su -" or
with "sudo -i" and see if that helps. Or, if you prefer, drop to a
text console (e.g. Ctrl-Alt-F2) and login directly as root there. Or,
if you prefer, and if you've configured your system to allow it, you
could try "ssh root@localhost".

[Gary L. Roach]

Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-16-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM

When trying to install the Bacula backup system on my computer, I get the following error:

    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0

I have noticed the same problem on other software packages. I have searched the internet for answers to this and have found dozens of cases with dozens of different ways to fix the problem, none of which seem to work for me. This is a recent problem that has started to occur since I was forced to reinstall my operating system. This problem  effects multiple software packages which seems to point to some  common cause.

Any help will be sincerely appreciated.

Gary R.

[Gary L. Roach]

Thanks for the reply. Your suggestion to use the Ctl-Alt-F2 console
worked. Although it worked, it is a pain to use as a normal way of
installing software. Any suggestions as to how to fix the root cause?

Gary R.

[Sven Hartge]

Gary L. Roach <garyro...@gmail.com> wrote:

> Thanks for the reply. Your suggestion to use the Ctl-Alt-F2 console
> worked. Although it worked, it is a pain to use as a normal way of
> installing software. Any suggestions as to how to fix the root cause?

Quite simple:

Don't use just "sudo", use "sudo -i" or "su -" to become root.

Any other method will keep parts of your users environment active,
causing the problems you noticed.

Grüße,
Sven.

--
Sigmentation fault. Core dumped.