Issue metadata
Sign in to add a comment
|
Problems with Crostini on a secondary profile |
||||||||||||||||||||||||
Issue description@dgreid since multi-profile is going away can we just prevent Crostini from running in a secondary profile? @rjwright -- if we do that, we should disable Crostini settings in the secondary profile. We already do this with settings like Network & People, and michaelpg/stevenjb can give more context there if needed. Chrome version: 68.0.3416.0 (Official Build) dev (64-bit) OS: Chrome Repro: 1. I first logged into both profiles 2. Then in Profile A, I enabled "Linux Apps" in settings and got the terminal window with the new container (cool!). I also confirmed that I had the Terminal app in launcher at that point 3. I move to Profile B, when I press "turn on" to enable linux apps in settings, a window pops up, but then immediately disappears. No Terminal app icon appears in Launcher and the settings menu looks as if it all worked (the only option under linux apps is to delete them). In an attempt to try again, I select the option to delete linux apps in settings. After enabling again, it doesn't work again. 4. Going back to Profile A, the Terminal icon is no longer in in Launcher.
,
May 3 2018
Do we know why this breaks? I am regularly using different VMs in different profiles with vmc start.
,
May 14 2018
,
May 17 2018
,
May 17 2018
We have restricted Crostini UI to just the Primary profile (first signed in). This doesn't restrict usage of vmc in other profiles. At present there is a risk of name collision for vms in different profiles (because the UI defaults to creating "termina") |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by timloh@chromium.org
, May 3 2018