New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 26 users
Status: Verified
Owner: ----
Closed: Feb 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocked on:
issue 350301



Sign in to add a comment
Support Ubuntu 14.04 in CRD host
Project Member Reported by sergeyu@chromium.org, Apr 24 2014 Back to list
Currently CRD host doesn't work OOB on Ubuntu 14.04. Currently there are two known issues
 1. unity-2d is not supported in Trusty, and default Unity is 
rendered upside-down with some GL drivers (e.g. NVidia).
 2. Pulseaudio integration is broken (see  bug 350301 ).



 
Issue 353710 has been merged into this issue.
Status: Available
Owner: lambroslambrou@chromium.org
Status: Assigned
Status: Started
Project Member Comment 6 by bugdroid1@chromium.org, Jun 9 2014
------------------------------------------------------------------
r275817 | lambroslambrou@chromium.org | 2014-06-09T16:20:01.622924Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/remoting/host/linux/linux_me2me_host.py?r1=275817&r2=275816&pathrev=275817

Load LLVMpipe GL driver in Chromoting desktop session

This sets up LD_LIBRARY_PATH in the virtual desktop session, so that
the software-rendered GL driver (LLVMpipe) is loaded instead of any
installed hardware drivers.

BUG= 366432 
NOTRY=true

Review URL: https://codereview.chromium.org/317373006
-----------------------------------------------------------------
Project Member Comment 7 by bugdroid1@chromium.org, Jun 9 2014
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9dd7a32845332803aa4833fcc8238ea10d46cb2a

commit 9dd7a32845332803aa4833fcc8238ea10d46cb2a
Author: lambroslambrou@chromium.org <lambroslambrou@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Mon Jun 09 16:20:01 2014

Load LLVMpipe GL driver in Chromoting desktop session

This sets up LD_LIBRARY_PATH in the virtual desktop session, so that
the software-rendered GL driver (LLVMpipe) is loaded instead of any
installed hardware drivers.

BUG= 366432 
NOTRY=true

Review URL: https://codereview.chromium.org/317373006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275817 0039d316-1c4b-4281-b951-d872f2087c98


Labels: Merge-Requested M-36
Status: Assigned
Please could we merge r275817 into M36? I've verified this on last night's Canary build of the Chromoting Host package, and this CL doesn't affect Chrome.
Labels: -Merge-Requested Merge-Approved
Labels: -Merge-Approved Merge-Merged
Merged in r276489.
Project Member Comment 11 by bugdroid1@chromium.org, Jun 11 2014
Labels: merge-merged-1985
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cf0a383d1a5a66f5680a53c9f18b20321ed8d9d8

commit cf0a383d1a5a66f5680a53c9f18b20321ed8d9d8
Author: lambroslambrou@chromium.org <lambroslambrou@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Wed Jun 11 20:44:00 2014

Merge 275817 "Load LLVMpipe GL driver in Chromoting desktop session"

> Load LLVMpipe GL driver in Chromoting desktop session
> 
> This sets up LD_LIBRARY_PATH in the virtual desktop session, so that
> the software-rendered GL driver (LLVMpipe) is loaded instead of any
> installed hardware drivers.
> 
> BUG= 366432 
> NOTRY=true
> 
> Review URL: https://codereview.chromium.org/317373006

TBR=lambroslambrou@chromium.org

Review URL: https://codereview.chromium.org/329203003

git-svn-id: svn://svn.chromium.org/chrome/branches/1985/src@276489 0039d316-1c4b-4281-b951-d872f2087c98


Project Member Comment 12 by bugdroid1@chromium.org, Jun 11 2014
------------------------------------------------------------------
r276489 | lambroslambrou@chromium.org | 2014-06-11T20:44:00.260238Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1985/src/remoting/host/linux/linux_me2me_host.py?r1=276489&r2=276488&pathrev=276489

Merge 275817 "Load LLVMpipe GL driver in Chromoting desktop session"

> Load LLVMpipe GL driver in Chromoting desktop session
> 
> This sets up LD_LIBRARY_PATH in the virtual desktop session, so that
> the software-rendered GL driver (LLVMpipe) is loaded instead of any
> installed hardware drivers.
> 
> BUG= 366432 
> NOTRY=true
> 
> Review URL: https://codereview.chromium.org/317373006

TBR=lambroslambrou@chromium.org

Review URL: https://codereview.chromium.org/329203003
-----------------------------------------------------------------
I think this change is wrong in a number of ways: it appears to override the user's LD_LIBRARY_PATH rather than append to it; it will likely interfere with any non-GUI NVIDIA Cuda binary invoked inside the CRD session; and it is highly Ubuntu-specific rather than deriving the Mesa path from the host OS package manager.
Thanks for the feedback. To address your points:

It doesn't override the user's LD_LIBRARY_PATH because we get in there first, before any user scripts get to run. The CRD session process begins with a completely blank environment, and then adds stuff to it (LD_LIBRARY_PATH now being one of them). The reverse problem could potentially exist (the user sets their own LD_LIBRARY_PATH overriding ours). I'm not sure how problematic that would be in practice, but we don't have any better solution.

For running NVIDIA CUDA programs in the session: it's a fair point, but if that proved to be a problem for those users, they could easily undo the effect of this change for that binary, or for the whole session, by unsetting the variable (perhaps in a custom ~/.chrome-remote-desktop-session). I expect many more users will benefit from this change than will be inconvenienced by it.

Finally, you're right that the path is Ubuntu-specific. If you know how to get the path from the package manager, please share that info and we can update the script. Right now, we are only aiming to support Ubuntu 12.04 and 14.04 (hopefully versions in between will work as well). Generalizing this particular path is just one of many problems to solve in order for CRD to support other Linux platforms :)

> It doesn't override the user's LD_LIBRARY_PATH because we get in there first, before any user scripts get to run.

Actually, no. pam_env is earlier, for example.

> The CRD session process begins with a completely blank environment, and then adds stuff to it (LD_LIBRARY_PATH now being one of them). The reverse problem could potentially exist (the user sets their own LD_LIBRARY_PATH overriding ours). I'm not sure how problematic that would be in practice, but we don't have any better solution.

I wouldn't worry about this. Everyone knows that the contract with environment variables is that they are appended to if their format is a list and so it should not surprise a user if overriding without append causes problems.

Labels: Chromoting-Bug-Cleanup
Owner: ----
Status: Available
We still don't work OOTB for Ubuntu 14.04. The only outstanding problem now is that compiz doesn't seem to like the stock Xvfb that Trusty uses. The Xvfb binary from Precise seems to work fine.

We need to find out why compiz fails to load, and figure out what changed in Xvfb to break compiz.

For now, Ubuntu 14.04 users need to customize ~/.chrome-remote-desktop-session to choose a different desktop environment (or install the Precise version of Xvfb).

Cc: rmsousa@chromium.org marja@chromium.org jamiewa...@chromium.org
 Issue 423818  has been merged into this issue.
Labels: -M-36
Status: Fixed
Given the lack of bug reports, we believe this is fixed enough.
Status: Verified
Sign in to add a comment