Open Bug 2014616 Opened 17 hours ago Updated 10 minutes ago

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)

Firefox 147
Desktop
Windows 10
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mlocochrane, Unassigned, NeedInfo)

Details

Attachments

(1 file)

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.

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.

Component: Untriaged → Sidebar
Component: Sidebar → New Tab Page
OS: Unspecified → Windows 10
Hardware: Unspecified → Desktop
Flags: needinfo?(mconley)

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:

  1. Can you please visit about:config, find the devtools.chrome.enabled pref, and toggle it to true
  2. 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.
  3. 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?

  1. 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?

Flags: needinfo?(mconley) → needinfo?(mlocochrane)

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.

Flags: needinfo?(mlocochrane)

Thank you so much! We really appreciate it. Re-requesting needinfo so it stays in the needinfo state.

Flags: needinfo?(mlocochrane)

I'm also very interested in any errors that might appear in the Browsing Console when you first open it after a browser start.

(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.

  1. 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 **

  1. 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.

(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

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.

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:

https://searchfox.org/firefox-main/rev/81cd862538be1cf95842a2ddfb7a5dd22c11ab25/browser/modules/AboutNewTab.sys.mjs#180

(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:

https://searchfox.org/firefox-main/rev/81cd862538be1cf95842a2ddfb7a5dd22c11ab25/browser/modules/AboutNewTab.sys.mjs#180

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.)

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.

Flags: needinfo?(brennie)

(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:

https://searchfox.org/firefox-main/rev/81cd862538be1cf95842a2ddfb7a5dd22c11ab25/browser/modules/AboutNewTab.sys.mjs#180

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

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.

Interesting. Does that sound familiar, Janos or Morgan? Have you manually transferred the profile folder between devices?

Flags: needinfo?(algopirin2005ftw)

(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.

Flags: needinfo?(algopirin2005ftw)

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?

Flags: needinfo?(algopirin2005ftw)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: