parentlock directory collides between users
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
People
(Reporter: rm.riches, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
Two users on the same Linux machine (one using VNC) started Firefox 68.3.0esr several minutes apart.
Actual results:
For the second user, creating each new browser window suffered a delay of several seconds. Investigation showed that the first user's session had create "/tmp/firefox-esr/.parentlock", and this non-user-specific directory name was key to causing or avoiding the delays.
Expected results:
The second user's session should have created new browser windows without a delay of several seconds. Based on investigation, each user's session should have created a user-specific directory for the .parent lock file.
|
Reporter | |
Comment 1•6 years ago
|
||
Firefox 60.9.0 created /tmp/firefox-esr-$USER or something similar but still user-specific. That avoided the collision where one user's Firefox session apparently tries to access things associated with the other user. The delays and directory name change appear to have begun with the jump from Firefox 60.9.0esr to 68.2.0esr.
I have found a workaround of setting the following environment variables in all user sessions:
TMPDIR /home/$USER/tmp
GCONF_TMPDIR $TMPDIR
KDETMP $TMPDIR
KDEVARTMP $TMPDIR
TEMP $TMPDIR
TMP $TMPDIR
With those variables set to those values, the .parentlock file's directory is created elsewhere than in /tmp, which avoids the collision between Firefox processes owned by different users.
|
||
Comment 2•6 years ago
|
||
Hi Robert,
Which Remote access software are you using?
Can you confirm whether this is also happening for last Firefox Nightly version? (You can download it from here https://nightly.mozilla.org/ ) If after doing this you can still reproduce the bug, would you send a screenshot or a video of the bug?
Thanks in advance. I've already chosen a component for this bug in hope that someone with more expertise may look at it. We'll await their answer.
Best regards, Clara.
|
||
Updated•6 years ago
|
|
|
Reporter | |
Comment 4•6 years ago
|
||
Thank you, all involved, for identifying this symptom as a duplicate of the other bug. The description and comments of that bug are entirely consistent with my observations that led to filing this. To tie up loose ends, the remote access software I use is simply a combination of ssh and VNC, tied together with custom scripts I wrote. The client machine PXE-boots a kernel and initrd based on TinyCore Linux, including scripts that launch an ssh session to the server. That session launches a VNC server on the server machine. Other related scripts launch a VNC viewer. The end result of the scripts and so forth is a user running a full set of X client processes on the server. One of the processes the user can launch from either a terminal window or a window manager menu is Firefox.
Description
•