Hi,
I have a user for which /run/user/${USER} directory is not automatically created. I manually created the directory and made it owned by the user and all was fine but after reboot it had disappeard and I had to do it again.
Could this be related to the fact that the user uses a remote connection via vncserver?
Frédéric
Allegedly, on or about 20 September 2017, Frédéric Bron sent:
I have a user for which /run/user/${USER} directory is not automatically created. I manually created the directory and made it owned by the user and all was fine but after reboot it had disappeard and I had to do it again.
Normally, the /run directory is a tmpfs mount (the contents are only held in RAM, they're not actually stored on disc). So, anything that's inside that directory will always need recreating (if needed) after a reboot. Though, having said that, I think that things in it are always going to be created upon demand (such as while the user is logging in), rather than being created once then restored.
Normally, the /run directory is a tmpfs mount (the contents are only held in RAM, they're not actually stored on disc). So, anything that's inside that directory will always need recreating (if needed) after a reboot. Though, having said that, I think that things in it are always going to be created upon demand (such as while the user is logging in), rather than being created once then restored.
Yes, you're right, it's normal that it is not there after reboot. What is not normal is why it is not created automatically.
Thanks,
Frédéric
On Wed, 20 Sep 2017 18:18:16 +0200 Frédéric Bron wrote:
Yes, you're right, it's normal that it is not there after reboot. What is not normal is why it is not created automatically.
I don't know if they fixed it yet or not, but I ran into this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1471519
I had a completely bogus entry in the /etc/tmpfiles.d directory due to screwing up when I was upgrading, and that shut down then entire tmpfile mechanism (rather than simply ignoring the one bogus entry).
I don't know if they fixed it yet or not, but I ran into this bug:
I do not think this is that.
What I understood is that: 1. we connect by ssh to launch the vncserver. The ssh connection creates the /run/user/${USER} directory 2. we launch vnc viewer 3. we exit the terminal where we launched vncviewer and at this moment the directory is removed.
Why?
On 09/20/2017 11:10 PM, Frédéric Bron wrote:
What I understood is that:
- we connect by ssh to launch the vncserver. The ssh connection
creates the /run/user/${USER} directory 2. we launch vnc viewer 3. we exit the terminal where we launched vncviewer and at this moment the directory is removed.
Why?
Maybe because the user session is now gone? (I don't think you meant to say vnc *viewer* for 2 and 3.) It would depend on what you're running on the vnc server. Normally, the display manager (gdm, sddm, etc.) create the session and launch the window manager. I'm guessing that the window manager itself doesn't keep the session open, so you will need to find some other way to do it.
On 09/21/17 14:10, Frédéric Bron wrote:
I don't know if they fixed it yet or not, but I ran into this bug:
I do not think this is that.
What I understood is that:
- we connect by ssh to launch the vncserver. The ssh connection
creates the /run/user/${USER} directory 2. we launch vnc viewer 3. we exit the terminal where we launched vncviewer and at this moment the directory is removed.
Why?
Just to confuse this even more....
If I do this....
1. connect to remote system via ssh, launch vncserver 2. connect from local to remote system by vncviewer 3. exit the ssh session
the /run/user/${USER} directory is removed.
If I do this...
1. connect to remote system via ssh, launch vncserver 2. exit the ssh session 3. connect from local to remote system by vncviewer
the /run/user/${USER} directory is there OK.
But if I use remmina instead of vncviewer the /run/user/${USER} directory is there no matter what order I perform the operations.
On 09/21/17 18:34, Ed Greshko wrote:
On 09/21/17 14:10, Frédéric Bron wrote:
I don't know if they fixed it yet or not, but I ran into this bug:
I do not think this is that.
What I understood is that:
- we connect by ssh to launch the vncserver. The ssh connection
creates the /run/user/${USER} directory 2. we launch vnc viewer 3. we exit the terminal where we launched vncviewer and at this moment the directory is removed.
Why?
Just to confuse this even more....
If I do this....
- connect to remote system via ssh, launch vncserver
- connect from local to remote system by vncviewer
- exit the ssh session
the /run/user/${USER} directory is removed.
If I do this...
1. connect to remote system via ssh, launch vncserver 2. exit the ssh session 3. connect from local to remote system by vncviewer
the /run/user/${USER} directory is there OK.
But if I use remmina instead of vncviewer the /run/user/${USER} directory is there no matter what order I perform the operations.
One more interesting thing....
After I logout of the vnc (remmina) session, KDE is the desktop, I logged in via ssh as another user. The /run/user/${USER} directory for the vncserver user still exists.
On Wed, Sep 20, 2017 at 10:56:35AM +0200, Frédéric Bron wrote:
Hi,
I have a user for which /run/user/${USER} directory is not automatically created. I manually created the directory and made it owned by the user and all was fine but after reboot it had disappeard and I had to do it again.
Could this be related to the fact that the user uses a remote connection via vncserver?
In short yes it could be, and it is likely to be a bug.
The directory is created by logind. There have been lots of bugs in this area where because a user isn't ‘logging in’ in the normal sense, the directory doesn't get created, eg:
https://bugzilla.redhat.com/show_bug.cgi?id=753882 https://bugzilla.redhat.com/show_bug.cgi?id=967509
If you can come up with an easy reproducer for the bug, I think you should file it.
Rich.
The directory is created by logind. There have been lots of bugs in this area where because a user isn't ‘logging in’ in the normal sense, the directory doesn't get created, eg:
https://bugzilla.redhat.com/show_bug.cgi?id=753882 https://bugzilla.redhat.com/show_bug.cgi?id=967509
OK, I will. Which component of fedora should I give? systemd?
Frédéric
-
Ed Greshko -
Frédéric Bron -
Richard W.M. Jones -
Samuel Sieb -
Tim -
Tom Horsley