Wrong documentation on cloning a user profile dir for new chromium instance
Reported by
m...@alechko.net,
Jul 21 2016
|
|||
Issue descriptionChrome Version : 51.0.2704.63 (Developer Build) Built on 8.4, running on Debian 8.2 (64-bit) URLs (if applicable) : http://dev.chromium.org/user-experience/user-data-directory Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Firefox: IE: What steps will reproduce the problem? (1) Try to clone a user profile dir with all bookmarks, extensions etc. (2) (3) What is the expected result? New identical profile to use in a new chromium instance (multiple sessions) What happens instead? Launching as new empty profile Please provide any additional information below. Attach a screenshot if possible. While trying to create 3 different sessions with chromium, I've tried to clone my dev profile into 2 new ones, and nothing seemed to work, I alway got a fresh start in each instance instead of getting the bookmarks, etc. from the parent profile. After asking at the IRC #chromium-support channel, it seems that the documentation on this issue is misleading and wrong, as it refers to clone the "Default" profile and load it with a "chromium --user-data-dir=/path/to/profile", while this approach is not working, the one that does works is "chromium --profile-directory=profile", and it's not mentioned anywhere in the docs. As I've understood from the user "Torne" in the IRC channel, "--user-data-dir" won't work for the same chromium process, and to make it work I need a new process with new config root dir, i.e. ~/.config/chromium-new and then launch a chromium with the new path. Also not mentioned anywhere in the docs. So I guess the relevant docs pages needs to be refreshed. http://dev.chromium.org/user-experience/user-data-directory http://dev.chromium.org/developers/creating-and-using-profiles Cheers :)
,
Jul 21 2017
--Chrome Identity automated triaging-- This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 11 2018
--Chrome Identity automated triaging-- This available, signin or profiles-related bug has gone at least 30 days since the last automated post without any further update. This bug will be closed out due to inactivity. Please re-open the bug and provide an update if it is still a valid or reproducible bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by torne@chromium.org
, Jul 21 2016Labels: Documentation
Status: Available (was: Unconfirmed)