New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 702307 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

/etc/init.d/chrome-remote-desktop fails when run as user

Project Member Reported by sergeyu@chromium.org, Mar 16 2017

Issue description

1. Configure and stop the host (/etc/init.d/chrome-remote-desktop stop)
2. Run "/etc/init.d/chrome-remote-desktop start" as user, e.g. without sudo

It appears that the host is being started successfully, but it's not actually started and the log shows the following message:

[0316/113203.037224:FATAL:remoting_user_session.cc(272)] Check failed: initgroups(pwinfo->pw_name, pwinfo->pw_gid) == 0. initgroups failed: Operation not permitted
#0 0x000000423c07 <unknown>
#1 0x00000041b98b <unknown>
#2 0x00000041bf7d <unknown>
#3 0x000000409a4c <unknown>
#4 0x7f66f9ae6f45 __libc_start_main
#5 0x000000408f49 <unknown>

I see this in 58.0.2999.0 compiled from trunk about a month ago, but it probably affects current M58 branch and potentially M57.
 
Cc: ajnolley@chromium.org
AJ, Do you know if this issue also affects M56 or M57 builds? 

Comment 2 by rkjnsn@chromium.org, Mar 16 2017

Looks like the problem is that sudo (used previously) is setuid, and allows
a user to sudo as themselves without a password. The PAM wrapper (as
discussed) currently isn't setuid. This could be fixed by updating the PAM
wrapper to support setuid operation. In the mean time, the init script
could be modified to avoid using the wrapper when not run as root.
Owner: rkjnsn@chromium.org
Status: Assigned (was: Untriaged)
The second option SGTM as a stopgap solution.
Sergey: In the M57 QA release, but not in the M56 release, running stop then start, the host appears to be active but does not appear to be running. It cannot be connected to, though the host is in the list. However, the log file created in TMP when running start is blank. Also, the Enable button is usually, but not always shown. A few times it was the Disable button shown, but the host still could not be connected to. 
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 17 2017

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

commit a35ddcb44aeea4436fa75bb6419e3b428377642c
Author: rkjnsn <rkjnsn@chromium.org>
Date: Fri Mar 17 22:23:13 2017

Use sudo when starting session as normal user

The PAM wrapper currently only works when started as root, so use sudo
for sessions started by the user for now.

BUG= 702307 

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

[modify] https://crrev.com/a35ddcb44aeea4436fa75bb6419e3b428377642c/remoting/host/installer/linux/debian/chrome-remote-desktop.init

Comment 6 by rkjnsn@chromium.org, Mar 17 2017

Status: Fixed (was: Assigned)
Labels: -M-58 M-59
The change didn't make it to M58
 Issue 725143  has been merged into this issue.
Status: Verified (was: Fixed)
Verified Fixed in 59.0.3071.47

Sign in to add a comment