ungoogled-software/ungoogled-chromium

--disable-machine-id doesn't work with regular profiles and vice versa

Open

#668 opened on Feb 5, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (771 forks)batch import
help wanted

Repository metrics

Stars
 (18,674 stars)
PR merge metrics
 (Avg merge 1d 11h) (9 merged PRs in 30d)

Description

Description

When creating a profile and then running chromium with --disable-machine-id, the profile gets destroyed. The same happens when you create a profile with --disable-machine-id and then run chromium without the option.

While this behavior may be intentional, it makes it impossible to migrate an already existing user data and the usefulness of this option is limited.

It would be better if this option disabled checking of settings integrity using a machine ID when loading settings, but saved the correct checksum anyway. This would allow migration of settings from and to regular Chrome. Or migrating an existing profile to a new machine.

Environment details

  • ungoogled-chromium version: 72.0.3626.81 (downloaded binary from chromium.woolyss.com)
  • OS: Windows 8.1 x64

Contributor guide

Research direction
Investigate the profile migration logic in Chromium, specifically how disable machine id interacts with profile checksums. Propose a change to store the correct checksum even when verification is disabled, allowing seamless migration between regular and ungoogled chromium profiles.
Tech stack
cpppython
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40