New issue
Advanced search Search tips

Issue 730773 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chromium-Packagers


Sign in to add a comment

Cannot build with enable_supervised_users=false

Reported by evange...@foutrelis.com, Jun 7 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36

Steps to reproduce the problem:
Try building Chromium with enable_supervised_users=false

What is the expected behavior?
Expected result is a successful build of Chromium with the Supervised Users feature disabled.

What went wrong?
The build fails at the point shown in the attached log excerpt.

Did this work before? N/A 

Chrome version: 59.0.3071.86  Channel: stable
OS Version: 
Flash Version: 

Relevant thread on chromium-packagers:

https://groups.google.com/a/chromium.org/d/msg/chromium-packagers/tldUg3YReuY/RQAZM0iDCgAJ
 
chromium-59.0.3071.86-0-x86_64-build.log
4.6 KB View Download
Components: Services>SupervisedUser
Labels: -Pri-2 Pri-3
I threw together this CL: https://codereview.chromium.org/2928823003

It compiles, no idea if it runs.
After applying Patch Set 2 on top of 59.0.3071.86 and building with 'enable_supervised_users=false', I got a segmentation fault in browser_sync::ProfileSyncService::IsSignedIn().

I tested moving the following line back into its original place:

    SigninManagerBase* signin = SigninManagerFactory::GetForProfile(profile);

And setting init_params.signin_wrapper as follows (not sure if it's correct):

==================================
    init_params.signin_wrapper =
#if BUILDFLAG(ENABLE_SUPERVISED_USERS)
        base::MakeUnique<SupervisedUserSigninManagerWrapper>(profile, signin);
#else
        base::MakeUnique<SigninManagerWrapper>(signin);
#endif
==================================

After that, opening chrome://settings/ resulted in a segfault in settings::ProfileInfoHandler::IsProfileManagingSupervisedUsers(), so I wrapped that in an #if/#else/#endif using BUILDFLAG(ENABLE_SUPERVISED_USERS).

Then, clicking on "Manage other people" resulted in a CHECK() failure, at which point I gave up.

Supervised users seems to be assumed enabled by code all over the place. I'm starting to question whether proper support for 'enable_supervised_users=false' is feasible, and even if it gets fixed now, how long it would last before it gets out of sync and breaks again. Then, there's also the fact that the 'enable_supervised_users=false' case is not part of the tests, so any build and/or runtime failures will go unnoticed.
Labels: TE-NeedsTriageHelp
Seems this is chromium build related issue which is difficult to triage the issue from te team end.Hence adding TE-NeedsTriageHelp  for further investigation.
Status: WontFix (was: Unconfirmed)

Sign in to add a comment