Background tasks with a persistent profile can display a visible error dialog if Firefox is downgraded
Categories
(Toolkit :: Background Tasks, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox105 | --- | wontfix |
firefox106 | --- | wontfix |
firefox107 | --- | wontfix |
firefox108 | --- | fix-optional |
People
(Reporter: bytesized, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fidedi-ope])
Attachments
(1 file)
23.64 KB,
image/png
|
Details |
I'm guessing a little at these STR. I haven't actually tried to reproduce this "from scratch". I'm also guessing a bit at the regression bug number. But I think that I might understand what is happening here.
STR:
- Install version 105 Release Firefox on Windows.
- Open the Windows Task Scheduler and run the "Background Update" task for the new installation.
- Pave over the install with version 104 Release Firefox.
- Once again run the "Background Update" task for the installation.
Expected results:
Background Update will work, or at least fail silently.
Actual results:
An error message is displayed: "This profile was last used with a newer version of this application. Please create a new profile."
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1775132
:nalexander, since you are the author of the regressor, bug 1775132, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 2•2 years ago
•
|
||
There's a few things happening here:
- this is expected behaviour: there's a legitimate profile downgrade
- background tasks shouldn't pop a
MessageBox
at all, but there are clearly some paths unaccounted for
We might want to:
- add telemetry and monitoring for background task profile downgrades
- avoid the
MessageBox
in background task mode - ignore profile downgrades in the background task
- figure out how to recover from downgraded profiles: can we blow the profile away entirely?
Reporter | ||
Comment 3•2 years ago
|
||
Just going to post this link to where (I believe) this message comes from in case it is useful when we go to fix this:
Comment 4•2 years ago
|
||
The severity field is not set for this bug.
:Amir, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 5•2 years ago
|
||
P3 'cuz we should fix this, S4 'cuz it's unlikely to impact many users and there is a work-around: delete the contents of the offending Background Tasks Profiles/<...>
profile directory.
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Set release status flags based on info from the regressing bug 1775132
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•