Closed
Bug 1966579
Opened 3 months ago
Closed 3 months ago
Nightly is unusable when launched with a new profile
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
VERIFIED
FIXED
140 Branch
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox138 | --- | unaffected |
firefox139 | --- | unaffected |
firefox140 | --- | verified |
firefox141 | --- | verified |
People
(Reporter: bhidecuti, Unassigned)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-quality-foundation?])
Attachments
(1 file)
2.34 MB,
video/mp4
|
Details |
Found in
- 140.0a1 (2025-05-14)
Affected versions
- 140.0a1
Tested platforms
- Affected platforms: macOS 13/14, Windows 11
- Unaffected platforms: Ubuntu
Steps to reproduce
- Install or update to the latest Nightly build
- Create a new profile via Profile Manager or from about:profile
- Launch the newly created profile
- Attempt to interact with the browser
Expected result
- The browser should be functional and responsive
Actual result
- The browser appears grayed out and is unasable - the window is unresponsive to input
Regression range
- Will search for a regression ASAP
Additional notes
- Pressing the ESC key dismisses the gray overlay and restores functionality
- See the attached video
- Not reproducing if using an old profile
Reporter | ||
Updated•3 months ago
|
Component: about:memory → Startup and Profile System
Updated•3 months ago
|
Reporter | ||
Comment 1•3 months ago
|
||
I have performed the regression range and Mozregression points to bug 1963168.
Keywords: regression
Regressed by: 1963168
Updated•3 months ago
|
Flags: needinfo?(emilio)
Comment 2•3 months ago
|
||
Setting Fx140 to fixed, since the regressor Bug 1963168 was backed out of central
Updated•3 months ago
|
Status: NEW → RESOLVED
Closed: 3 months ago
Flags: needinfo?(emilio)
Resolution: --- → FIXED
Updated•3 months ago
|
Target Milestone: --- → 140 Branch
Reporter | ||
Comment 3•3 months ago
•
|
||
I can confirm that the issue is no longer reproducible using Firefox Nightly 140.0a1 (2025-05-15), on macOS 14 and Windows 11, after the fix for bug 1963168 was backed out.
Updated•3 months ago
|
QA Whiteboard: [qa-found-in-c140] → [qa-found-in-c140][qa-triage-done-c141/b140][qa-ver-needed-c141/b140]
Flags: qe-verify+
Reporter | ||
Comment 4•3 months ago
•
|
||
Verified as fixed using Firefox 140.0b2 and Firefox Nightly 141.0a1 (2025-05-28), on macOS 14 and Windows 11. The browser is responsive when launched with a new profile.
Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-found-in-c140][qa-triage-done-c141/b140][qa-ver-needed-c141/b140] → [qa-found-in-c140][qa-triage-done-c141/b140][qa-ver-done-c141/b140]
status-firefox141:
--- → verified
Flags: qe-verify+
QA Contact: bhidecuti
You need to log in
before you can comment on or make changes to this bug.
Description
•