New issue
Advanced search Search tips

Issue 672684 link

Starred by 1 user
Status: Fixed
Owner:
rkjnsn@chromium.org
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

X org server can fail to start when TMPDIR is set

Project Member Reported by rkjnsn@chromium.org, Dec 9 2016 
When starting, if TMPDIR is set, the xkb component of the X server appears to try create a temporary file in $TMPDIR and then move it to /tmp. This obviously fails if both directories are not on the same filesystem.

What steps will reproduce the problem?
(1) Edit ~/.profile to set TMPDIR to a path on a separate filesystem from /tmp
(2) sudo service chrome-remote-desktop restart

What is the expected result?
The host starts successfully.

What happens instead?
Starting the X server fails with an error such as the following:
[xkb] Can't rename /usr/local/google/tmp/filezA5HaZ to /tmp/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm, error: Invalid cross-device link

Solution appears to be to omit TMPDIR from the environment used to start the X server
Project Member

Comment 1 by bugdroid1@chromium.org, Dec 21 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/606e53489b319ad2354e496da7ffd0dee732d6e4

commit 606e53489b319ad2354e496da7ffd0dee732d6e4
Author: rkjnsn <rkjnsn@chromium.org>
Date: Wed Dec 21 21:04:50 2016

Don't include TMPDIR in X server environment

Presence of TMPDIR can cause the X server to fail to start.

BUG= 672684 

Review-Url: https://codereview.chromium.org/2566363002
Cr-Commit-Position: refs/heads/master@{#440210}

[modify] https://crrev.com/606e53489b319ad2354e496da7ffd0dee732d6e4/remoting/host/linux/linux_me2me_host.py

Comment 2 by rkjnsn@chromium.org, Jan 12 2017

Status: Fixed (was: Assigned)
Should be fixed by the above commit.
►

Sign in to add a comment