After the Firefox v147.0.3 update my Firefox Home is completely blank, both when I start on the page as my default or when I go to it. I tested it in Troubleshoot Mode but had the same issue.
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
People
(Reporter: mlocochrane, Assigned: mossop)
References
(Depends on 1 open bug)
Details
Attachments
(5 files)
|
18.62 KB,
image/png
|
Details | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr140+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0
Steps to reproduce:
Opened the about:home tab and it is blank.
Actual results:
Tab is blank.
Expected results:
Seeing my normal home screen with my pinned sites, recent visits and search bar.
Comment 1•3 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Sidebar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Reporter | ||
Updated•3 months ago
|
Updated•3 months ago
|
Comment 2•3 months ago
|
||
A similar report here: https://www.reddit.com/r/firefox/comments/1qwf8iz/ff_home_tab_is_empty_on_14703/
Comment 3•3 months ago
|
||
Originally reported here: https://www.reddit.com/r/firefox/comments/1qvtwmc/comment/o3moaiw/
Comment 4•3 months ago
|
||
Hi Morgan, thank you for reporting. I'm sorry that you're hitting this bug.
Thanks as well for the information you already provided in the Reddit post:
After this update my Firefox Home is completely blank, both when I start on the page as my default or when I go to it. I tested it in Troubleshoot Mode but had the same issue. Anyway ideas what happened and how to fix it. Thank you.
That's useful information to know that Troubleshoot Mode did not help fix this.
I have some diagnostic steps I'm hoping you can run that might help us understand what's happening here, if you have some time. This goes as well for anybody else experiencing this issue:
- Can you please visit about:config, find the
devtools.chrome.enabledpref, and toggle it totrue - Type Ctrl+Shift+J to bring up the "Browser Console" interface. This is a dialog box that will let us interrogate the browser for more information.
- In the text box at the bottom of the Browser Console, can you please type:
AboutNewTab.activityStream
and press enter? What does it show when you do that?
4. Next, what happens if you paste in:
{
let { ProfileAge } = ChromeUtils.importESModule("resource://gre/modules/ProfileAge.sys.mjs");
console.log("Got ProfileAge module");
let pa = await ProfileAge();
console.log("Got ProfileAge accessor");
let created = await pa.created;
console.log("Got profile creation time:", created);
}
and press enter? What does it show you when you do that?
- Finally, what happens if you paste in:
{
console.log("Waiting for newtabTrainhop to be ready");
await NimbusFeatures["newtabTrainhop"].ready()
console.log("newtabTrainhop is ready")
}
and press enter?
| Reporter | ||
Comment 5•3 months ago
|
||
Thank you the follow up. I am not able to do this step at this time but when I am back at my system I will provide the information requested.
Comment 6•3 months ago
|
||
Thank you so much! We really appreciate it. Re-requesting needinfo so it stays in the needinfo state.
Comment 7•3 months ago
|
||
I'm also very interested in any errors that might appear in the Browsing Console when you first open it after a browser start.
Comment 8•3 months ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #4)
Hi,
i'm from Comment #2.
AboutNewTab.activityStream
and press enter? What does it show when you do that?
it says null.
- Next, what happens if you paste in:
{ let { ProfileAge } = ChromeUtils.importESModule("resource://gre/modules/ProfileAge.sys.mjs"); console.log("Got ProfileAge module"); let pa = await ProfileAge(); console.log("Got ProfileAge accessor"); let created = await pa.created; console.log("Got profile creation time:", created); }and press enter? What does it show you when you do that?
**Got ProfileAge module debugger eval code:6:13
Got ProfileAge accessor debugger eval code:8:13
Got profile creation time: 1433963779951 debugger eval code:10:13
undefined **
- Finally, what happens if you paste in:
{ console.log("Waiting for newtabTrainhop to be ready"); await NimbusFeatures["newtabTrainhop"].ready() console.log("newtabTrainhop is ready") }and press enter?
Waiting for newtabTrainhop to be ready debugger eval code:3:13
nothing else happens if I open a new tab.
Comment 9•3 months ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #7)
I'm also very interested in any errors that might appear in the Browsing Console when you first open it after a browser start.
Sorry I just saw this.
This is what the console says:
1770309119864 addons.xpi WARN Checking C:\Program Files\Mozilla Firefox\distribution\extensions for addons A Window.fullScreen attribútum elavult, és a jövőben eltávolításra kerül. browser-customtitlebar.js:68:7 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367 TypeError: can't access property "executeTransaction", conn is null init resource://nimbus/lib/Enrollments.sys.mjs:223 SharedDataMap.sys.mjs:100:17 init resource://nimbus/lib/SharedDataMap.sys.mjs:100 ExperimentAPI: Failed to initialize ExperimentStore: TypeError: can't access property "execute", conn is null _reportStartupDatabaseConsistency resource://nimbus/lib/ExperimentStore.sys.mjs:582 ExperimentAPI.sys.mjs:254 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367
Comment 10•3 months ago
|
||
Waiting for newtabTrainhop to be ready debugger eval code:3:13
Okay, that's interesting - the newtabTrainhop is ready message never appears. I'd be interested in knowing if the same behaviour occurs for you, Morgan.
Comment 11•3 months ago
|
||
SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367 TypeError: can't access property "executeTransaction", conn is null init resource://nimbus/lib/Enrollments.sys.mjs:223 SharedDataMap.sys.mjs:100:17 init resource://nimbus/lib/SharedDataMap.sys.mjs:100 ExperimentAPI: Failed to initialize ExperimentStore: TypeError: can't access property "execute", conn is null _reportStartupDatabaseConsistency resource://nimbus/lib/ExperimentStore.sys.mjs:582 ExperimentAPI.sys.mjs:254 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367
This is interesting, and looks like the smoking gun for at least Janos: the profiles data store cannot be read, so the ExperimentAPI fails to initialize, so I believe this Promise never resolves:
Comment 12•3 months ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #11)
This is interesting, and looks like the smoking gun for at least Janos: the profiles data store cannot be read, so the ExperimentAPI fails to initialize, so I believe this Promise never resolves:
the reason is, that "Profile Groups" folder doesn't even exist. If it's something new, then the bug is that this doesn't get created on updates. I have also reinstalled FF (to go back to 147.0.2) several times and that folder doesn't exist. And I get the same error on 147.0.2 as well. And my profile isn't even at that location. So if that is something important, you need to make sure it gets created, or the correct profile path is used. (The file doesn't exist in my profile folder though.)
Comment 13•3 months ago
•
|
||
Hey beth, just putting this on your radar... have we seen this kind of behaviour before, where ExperimentAPI just kinda falls over due to an unwritten / unavailable profile shared data store? Also cc'ing Niklas, Mossop and jhirsch.
Comment 14•3 months ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #11)
This is interesting, and looks like the smoking gun for at least Janos: the profiles data store cannot be read, so the ExperimentAPI fails to initialize, so I believe this Promise never resolves:
just for reference, this is the console log on 147.0.2:
1770310250487 addons.xpi WARN Checking C:\Program Files\Mozilla Firefox\distribution\extensions for addons A Window.fullScreen attribútum elavult, és a jövőben eltávolításra kerül. browser-customtitlebar.js:68:7 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367 TypeError: can't access property "executeTransaction", conn is null init resource://nimbus/lib/Enrollments.sys.mjs:223 SharedDataMap.sys.mjs:100:17 init resource://nimbus/lib/SharedDataMap.sys.mjs:100 ExperimentAPI: Failed to initialize ExperimentStore: TypeError: can't access property "execute", conn is null _reportStartupDatabaseConsistency resource://nimbus/lib/ExperimentStore.sys.mjs:582 ExperimentAPI.sys.mjs:254 SQLite JSM (ConnectionOpener): Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 Sqlite.sys.mjs:1410:18 openConnection resource://gre/modules/Sqlite.sys.mjs:1410 NS_ERROR_FILE_ACCESS_DENIED: Could not open connection to C:\Users\bsh\AppData\Roaming\Mozilla\Firefox\Profile Groups\6d78ad12.sqlite: 2152857621 openConnection resource://gre/modules/Sqlite.sys.mjs:1411 ProfilesDatastoreService.sys.mjs:367:15 #init moz-src:///toolkit/profile/ProfilesDatastoreService.sys.mjs:367 A billentyűesemény nem érhető el egyes billentyűzetkiosztások esetén: key="z" modifiers="control,alt" id="toggleSidebarKb" browser.xhtml A billentyűesemény nem érhető el egyes billentyűzetkiosztások esetén: key="x" modifiers="accel,alt" id="viewGenaiChatSidebarKb" browser.xhtml A billentyűesemény nem érhető el egyes billentyűzetkiosztások esetén: key="i" modifiers="accel,alt,shift" id="key_browserToolbox" browser.xhtml can't access property "isAdoptingTab", this.window.gBrowserInit is undefined ext-browser.js:1203:9 get activeTab chrome://browser/content/parent/ext-browser.js:1203 candidates chrome://extensions/content/parent/ext-tabs-base.js:2109 InterpretGeneratorResume self-hosted:1312 next self-hosted:1233 query chrome://extensions/content/parent/ext-tabs-base.js:2131 next self-hosted:1233 from self-hosted:513 query chrome://browser/content/parent/ext-tabs.js:1059 result resource://gre/modules/ExtensionParent.sys.mjs:1223 withCallContextData resource://gre/modules/ExtensionParent.sys.mjs:666 result resource://gre/modules/ExtensionParent.sys.mjs:1222 withPendingBrowser resource://gre/modules/ExtensionParent.sys.mjs:676 result resource://gre/modules/ExtensionParent.sys.mjs:1221 callAndLog resource://gre/modules/ExtensionParent.sys.mjs:1172 recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1220 AsyncFunctionNext self-hosted:780
| Assignee | ||
Comment 15•3 months ago
|
||
The datastore only attempts to create the profile groups directory if there isn't already a storeID assigned. So if for example you copied a profile folder to a new device then it would have a storeID assigned in the preferences but the groups database would not be there. We should just always attempt to create that directory.
Comment 16•3 months ago
|
||
Interesting. Does that sound familiar, Janos or Morgan? Have you manually transferred the profile folder between devices?
Comment 17•3 months ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #16)
Interesting. Does that sound familiar, Janos or Morgan? Have you manually transferred the profile folder between devices?
yes of course.
Comment 18•3 months ago
|
||
Thanks, Jonas.
If you go to about:config, click past the warning, search for toolkit.profiles.storeID, does an entry show up? If so, make note of it separately, and then can you please click on the trash can icon to the right of it, and restart the browser? Does doing that, and then opening a few new newtab's fix the issue?
Comment 19•3 months ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #18)
Thanks, Jonas.
If you go to
about:config, click past the warning, search fortoolkit.profiles.storeID, does an entry show up? If so, make note of it separately, and then can you please click on the trash can icon to the right of it, and restart the browser? Does doing that, and then opening a few new newtab's fix the issue?
yes it does have the value above. and deleting it fixes the issue with the empty new tab. it also faciliates creating the missing "Profile Groups" folder.
and the console now has barely any errors or warnings:
1770318519427 addons.xpi WARN Checking C:\Program Files\Mozilla Firefox\distribution\extensions for addons A Window.fullScreen attribútum elavult, és a jövőben eltávolításra kerül. browser-customtitlebar.js:68:7 A billentyűesemény nem érhető el egyes billentyűzetkiosztások esetén: key="z" modifiers="control,alt" id="toggleSidebarKb" browser.xhtml A billentyűesemény nem érhető el egyes billentyűzetkiosztások esetén: key="x" modifiers="accel,alt" id="viewGenaiChatSidebarKb" browser.xhtml A billentyűesemény nem érhető el egyes billentyűzetkiosztások esetén: key="i" modifiers="accel,alt,shift" id="key_browserToolbox" browser.xhtml can't access property "isAdoptingTab", this.window.gBrowserInit is undefined ext-browser.js:1203:9 get activeTab chrome://browser/content/parent/ext-browser.js:1203 candidates chrome://extensions/content/parent/ext-tabs-base.js:2109 InterpretGeneratorResume self-hosted:1312 next self-hosted:1233 query chrome://extensions/content/parent/ext-tabs-base.js:2131 next self-hosted:1233 from self-hosted:513 query chrome://browser/content/parent/ext-tabs.js:1059 result resource://gre/modules/ExtensionParent.sys.mjs:1223 withCallContextData resource://gre/modules/ExtensionParent.sys.mjs:666 result resource://gre/modules/ExtensionParent.sys.mjs:1222 withPendingBrowser resource://gre/modules/ExtensionParent.sys.mjs:676 result resource://gre/modules/ExtensionParent.sys.mjs:1221 callAndLog resource://gre/modules/ExtensionParent.sys.mjs:1172 recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1220 InterpretGeneratorResume self-hosted:1312 AsyncFunctionNext self-hosted:780
is it safe to delete this, or more exactly: not to backup this thing in the Roaming folder? is it going to be recreated every time it's missing?
| Assignee | ||
Comment 20•3 months ago
|
||
Updated•3 months ago
|
| Assignee | ||
Comment 21•3 months ago
|
||
(In reply to Janos Kövari from comment #19)
is it safe to delete this, or more exactly: not to backup this thing in the Roaming folder? is it going to be recreated every time it's missing?
What thing are you referring to?
Comment 22•3 months ago
|
||
(In reply to Dave Townsend [:mossop] from comment #21)
(In reply to Janos Kövari from comment #19)
is it safe to delete this, or more exactly: not to backup this thing in the Roaming folder? is it going to be recreated every time it's missing?
What thing are you referring to?
those files and folders in the AppData/Roaming/, including the now new "Profile Groups". Because I'm not going to backup and restore that entire thing. Is it safe doing so? Gonna be recreated every time? With a new storeID? Does it have any effect for me?
| Assignee | ||
Comment 23•3 months ago
|
||
(In reply to Janos Kövari from comment #22)
(In reply to Dave Townsend [:mossop] from comment #21)
(In reply to Janos Kövari from comment #19)
is it safe to delete this, or more exactly: not to backup this thing in the Roaming folder? is it going to be recreated every time it's missing?
What thing are you referring to?
those files and folders in the AppData/Roaming/, including the now new "Profile Groups". Because I'm not going to backup and restore that entire thing. Is it safe doing so? Gonna be recreated every time? With a new storeID? Does it have any effect for me?
Firefox settings are stored there, deleting them may cause unexpected things to break.
Comment 24•3 months ago
|
||
Another report on Reddit: https://www.reddit.com/r/firefox/comments/1qwvj25/firefox_home_content_missing/
Comment 25•3 months ago
|
||
The original poster of the latest thread (comment 24) did remark that they'd manually renamed the "Profile Groups" folder, so while this wasn't a device move, it had the same overarching effect - the storeID existed in prefs, but the Profile Groups folder was missing.
Comment 26•3 months ago
|
||
More evidence of the pref clearing working: https://www.reddit.com/r/firefox/comments/1qwvj25/comment/o3sa7yq/
Updated•3 months ago
|
| Reporter | ||
Comment 27•3 months ago
|
||
Ask 1
17:23:28.968 AboutNewTab.activityStream
17:23:28.989 null
Ask 2
17:23:55.178 {
let { ProfileAge } = ChromeUtils.importESModule("resource://gre/modules/ProfileAge.sys.mjs");
console.log("Got ProfileAge module");
let pa = await ProfileAge();
console.log("Got ProfileAge accessor");…
17:23:55.201 Got ProfileAge module debugger eval code:6:13
17:23:55.201 Got ProfileAge accessor debugger eval code:8:13
17:23:55.201 Got profile creation time: 1543725629807 debugger eval code:10:13
17:23:55.202 undefined
Ask 3
17:24:11.777 {
console.log("Waiting for newtabTrainhop to be ready");
await NimbusFeatures["newtabTrainhop"].ready()
console.log("newtabTrainhop is ready")
}
17:24:11.798 Waiting for newtabTrainhop to be ready
Ask 4: errors in the Browsing Console when first open it after browser start
17:24:59.912 Unexpected non-empty DNRStore data. DNR startupCache data load dropped. ExtensionDNRStore.sys.mjs:1228
_ensureCacheLoaded resource://gre/modules/ExtensionDNRStore.sys.mjs:1228
InterpretGeneratorResume self-hosted:1312
AsyncFunctionNext self-hosted:780
17:25:00.686 SQLite JSM (Connection 651827ec.sqlite#0): Error during transaction requested by init@Enrollments.sys.mjs. Rolling back TypeError: can't access property "branches", recipe is null
processRow resource://nimbus/lib/Enrollments.sys.mjs:688
loadEnrollments resource://nimbus/lib/Enrollments.sys.mjs:734
Sqlite.sys.mjs:865:30
17:25:00.730 SQLite JSM (Connection 651827ec.sqlite#0): TypeError: can't access property "branches", recipe is null
processRow resource://nimbus/lib/Enrollments.sys.mjs:688
loadEnrollments resource://nimbus/lib/Enrollments.sys.mjs:734
Sqlite.sys.mjs:917:20
_transactionQueue resource://gre/modules/Sqlite.sys.mjs:917
17:25:00.730 TypeError: can't access property "branches", recipe is null
processRow resource://nimbus/lib/Enrollments.sys.mjs:688
loadEnrollments resource://nimbus/lib/Enrollments.sys.mjs:734
SharedDataMap.sys.mjs:100:17
init resource://nimbus/lib/SharedDataMap.sys.mjs:100
17:25:01.748 ExtensionError: No such native application mozillavpn ExtensionUtils.sys.mjs:48:5
17:25:07.359 can't access property "isAdoptingTab", this.window.gBrowserInit is undefined 4 ext-browser.js:1203:9
get activeTab chrome://browser/content/parent/ext-browser.js:1203
candidates chrome://extensions/content/parent/ext-tabs-base.js:2109
next self-hosted:1233
query chrome://extensions/content/parent/ext-tabs-base.js:2131
next self-hosted:1233
from self-hosted:513
query chrome://browser/content/parent/ext-tabs.js:1059
result resource://gre/modules/ExtensionParent.sys.mjs:1223
withCallContextData resource://gre/modules/ExtensionParent.sys.mjs:666
result resource://gre/modules/ExtensionParent.sys.mjs:1222
withPendingBrowser resource://gre/modules/ExtensionParent.sys.mjs:676
result resource://gre/modules/ExtensionParent.sys.mjs:1221
callAndLog resource://gre/modules/ExtensionParent.sys.mjs:1172
recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1220
AsyncFunctionNext self-hosted:780
17:25:07.380 Error: An unexpected error occurred
Question "Have you manually transferred the profile folder between devices?"
Not between devices, I did have an issue where the ESR profile overwrote the main profile so had to restore it from backup after uninstall.
Ask 5: Check storeID
toolkit.profiles.storeID = 651827ec
Deleted. Restarted browser. Is working as expected. (Note: wish I saw this last thing to do before I did the above).
Comment 28•3 months ago
|
||
Comment 29•3 months ago
|
||
Thank you Morgan and Janos - the information you provided helped us identify a nasty edge-case that we're landing a patch to fix. I'm glad the workarounds worked!
Comment 30•3 months ago
|
||
Comment 31•3 months ago
|
||
Backed out for causing multiple failures
Backout link: https://hg.mozilla.org/integration/autoland/rev/b9f6d2af8f8d888e3135f616cf43102e17b9931d
Updated•3 months ago
|
Updated•3 months ago
|
| Assignee | ||
Updated•3 months ago
|
Comment 32•3 months ago
|
||
Comment 33•3 months ago
|
||
| bugherder | ||
Comment 34•3 months ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 35•3 months ago
|
||
The patch landed in nightly and beta is affected.
:mossop, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox148towontfix.
For more information, please visit BugBot documentation.
Comment 36•3 months ago
|
||
This the final week of beta for Fx148. There is little time left for uplifts.
:mossop, do you plan on requesting uplift or letting this ride the train?
I'm not sure how risky the patch is.
| Assignee | ||
Comment 37•3 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D282027
Updated•3 months ago
|
Comment 38•3 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: A small number of users will be unable to open links from other applications while Firefox is running
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: The patch is a simple null check
- String changes made/needed: None
- Is Android affected?: no
| Assignee | ||
Comment 39•3 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D282027
Updated•3 months ago
|
Comment 40•3 months ago
|
||
firefox-esr140 Uplift Approval Request
- User impact if declined: A small number of users will be unable to open links from other applications while Firefox is running
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: The patch is a simple null check
- String changes made/needed: None
- Is Android affected?: no
| Assignee | ||
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Comment 41•3 months ago
|
||
| uplift | ||
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Comment 42•3 months ago
|
||
| uplift | ||
| Assignee | ||
Comment 43•3 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D282027
Updated•3 months ago
|
Comment 44•3 months ago
|
||
firefox-release Uplift Approval Request
- User impact if declined: A small number of users will be unable to open links from other applications while Firefox is running
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: The patch is a simple null check
- String changes made/needed: None
- Is Android affected?: no
Updated•3 months ago
|
Updated•3 months ago
|
Comment 45•3 months ago
|
||
| uplift | ||
Description
•