Dedicated profile is not created.

VERIFIED FIXED in Firefox 67

Status

()

defect
--
major
VERIFIED FIXED
4 months ago
3 months ago

People

(Reporter: Ovidiu, Assigned: mossop)

Tracking

Trunk
mozilla67
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox67 verified)

Details

Attachments

(1 attachment)

Affected versions

  • Nightly 67.0a1

Affected platforms

  • Mac OS, Windows

Steps to reproduce

  1. Install 2 builds with Dedicated Profile enabled
  2. Open both of them at the same time or alternative
  3. Go to about:profiles and check how many profiles are created.
    Expected result
    *Each build that has the Dedicated feature should have its own profile.
  • There are 3 profiles: default, default-nightly and default-nightly-1
    NOTE: In this case, I used Nightly builds but if you use beta with Dedicated feature the profile name will change to default-beta.

Actual result
There are 2 profiles: default, default-nightly
The second build uses the default profile.

Additional notes

  • We will test on Ubuntu and update the bug report.
Blocks: 1474285
Severity: normal → major
Assignee

Comment 1

4 months ago

This is a result of the fix for bug 1522751.

Blocks: 1522751
Assignee

Updated

4 months ago
Assignee: nobody → dtownsend
Assignee

Comment 2

4 months ago

Using an old default profile that is empty (like from bug 1518591) causes us to
also show the user a welcome page when that isn't necessary.

Instead leave old empty profiles alone (older versions will use them as the
default), create a new profile but don't set the flag to say that the old
default was skipped.

Comment 3

4 months ago
Pushed by dtownsend@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c699c4e694a1
Don't use empty profiles for dedicated profiles and don't show the welcome page in this case. r=froydnj

Comment 4

4 months ago
bugherder
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67

I verified this on multiple OSes and I have different results:

On Mac OS 10.14:

  • if both installs are open at the same there are 3 profiles: default, default-nightly and default-nightly-1
  • if the installs are open alternatively there are 3 profiles: default, default-nightly and default-nightly-1

On Windows 10 :

  • if both installs are open at the same there are 2 profiles: default, default-nightly and when you open the second install a new window is open not a new profile.
  • if the installs are open alternatively there are 3 profiles: default, default-nightly and default-nightly-1

On Ubuntu 16.04:

  • if both installs are open at the same there are 2 profiles: default, default-nightly and when you open the second install a new window is open not a new profile.
  • if the installs are open alternatively there are 3 profiles: default, default-nightly and default-nightly-1

Please let me know if I need to file a separate bug for this issue.

Flags: needinfo?(dtownsend)
Assignee

Comment 6

4 months ago

Are you running the second install with -no-remote? Until bug 1518639 is fixed what you describe is what I would expect without -no-remote.

Flags: needinfo?(dtownsend)

No, I don't use -no-remote, I've just opened them normally, double click on the icon.

Updated

4 months ago
Depends on: 1528568

I verified this on Windows 10 and Ubuntu 16.04 with the latest Nightly 67.0a1(2019-03-07) and I can confirm the fix.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.