Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #235168 > unrolled thread

Re: /run/user/1000 errors

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: /run/user/1000 errors Greg Wooledge <greg@wooledge.org> - 2021-05-13 21:00 +0200
    Re: /run/user/1000 errors "Gary L. Roach" <garyroach719@gmail.com> - 2021-05-14 21:40 +0200
      Re: /run/user/1000 errors Sven Hartge <sven@svenhartge.de> - 2021-05-14 22:20 +0200

#235168 — Re: /run/user/1000 errors

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".

[toc] | [next] | [standalone]

#235199

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.


On 5/13/21 11:55 AM, Greg Wooledge wrote:
> 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".

[toc] | [prev] | [next] | [standalone]

#235200

Gary L. Roach <garyroach719@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.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web