1873324 - Library content is empty when managing history in Firefox on Ubuntu 20

Status: RESOLVED WORKSFORME

(Core :: SQLite and Embedded Database Bindings, defect)

Description

[Jury.Lysenko]

Attachment: FF121Library-empty(.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0

Steps to reproduce:

Open Manage History from History menu and observe appeared Library content

Actual results:

Library content is empty, see attached screenshot and console errors

Expected results:

Library content should display history

Comment 1

[Jury.Lysenko]

Attachment: console-export-2024-1-6_4-8-58.txt

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Bookmarks & History' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Mark Banner (:standard8)]

Thank you for attaching the console log as well. From the log, it appears the issue is not only related to bookmarks & history, but a lot of other databases that are in your profile appear to be inaccessible as well.

Have you checked that your profile is not read-only, and that you don't have any disk corruption?

Comment 4

[Jury.Lysenko]

(In reply to Mark Banner (:standard8) from comment #3)

Thank you for attaching the console log as well. From the log, it appears the issue is not only related to bookmarks & history, but a lot of other databases that are in your profile appear to be inaccessible as well.

Have you checked that your profile is not read-only, and that you don't have any disk corruption?

There was low space issue but I cleaned temporary files using Stacer app and now there is enough space.
Should I reinstall Firefox app to resolve issues?

Comment 5

[Mark Banner (:standard8)]

Restarting Firefox should be enough.

Comment 6

[Jury.Lysenko]

(In reply to Mark Banner (:standard8) from comment #5)

Restarting Firefox should be enough.

it seems did not helped, see attachment

Comment 7

[Jury.Lysenko]

Attachment: console-export-2024-1-8_7-14-39.txt

Comment 8

[Mark Banner (:standard8)]

I don't know the best route forward from here, I'm going to move it across to our storage component and hopefully someone there will be able to help.

Comment 9

[Alex Cornestean]

Hello,

Webextensions QA here. The bug report ended up in our triage as we monitor the “Toolkit” product, as well, more precisely the "Add-ons Manager" component.

Since no extensions or add-ons manager is involved, I’ll let my more knowledgeable colleagues on the matter handle this issue.

Thank you !

Comment 10

[Monica Chiorean]

Mark Banner, can we mark the issue as new since you already looked at the logs? Thank you.

Comment 11

[Mark Banner (:standard8)]

(In reply to Monica Chiorean from comment #10)

Mark Banner, can we mark the issue as new since you already looked at the logs? Thank you.

It is probably an issue on the user's system (or was caused by one), but I don't know enough about this to be certain. Hence why I moved this to storage so the relevant people can take a look.

Comment 12

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mak, could you have a look please?

For more information, please visit BugBot documentation.

Comment 13

[Andrew Sutherland [:asuth] (he/him)]

The NS_ERROR_STORAGE_BUSY errors are surprising. And given our default behavior of trying to acquire exclusive locks initially might suggest that the previous Firefox session is still running, holding exclusive locks, and that we then fell back to non-exclusive locks which then allowed us to manifest the busy errors.

Reporter:

• Can you confirm your Ubuntu version? The subject just says "Ubuntu 20"; does that mean 20.04 or 20.10? At least on recent versions of Ubuntu (I'm on 23.10), pressing the windows key and typing "about" will provide a deep link to the settings app's "about" page which lists the "Operating System". Also on most Ubuntu releases cat /etc/lsb-release from the terminal should list the DISTRIB_RELEASE. (Also lsb_release -r should work.)
• Have you restarted your system since addressing the disk space problem? As per the above, I'm wondering if Firefox is still running but the .parentlock / lock mechanism failed to prevent the profile from being opened multiple times.

Comment 14

[Jury.Lysenko]

lsb_release -r
Release: 20.04

Comment 15

[Mark Banner (:standard8)]

(In reply to Andrew Sutherland [:asuth] (he/him) from comment #13)

• Have you restarted your system since addressing the disk space problem? As per the above, I'm wondering if Firefox is still running but the .parentlock / lock mechanism failed to prevent the profile from being opened multiple times.

Please can you answer this part as well?

Comment 16

[Jury.Lysenko]

(In reply to Mark Banner (:standard8) from comment #15)

(In reply to Andrew Sutherland [:asuth] (he/him) from comment #13)

• Have you restarted your system since addressing the disk space problem? As per the above, I'm wondering if Firefox is still running but the .parentlock / lock mechanism failed to prevent the profile from being opened multiple times.

Please can you answer this part as well?

Library content is filled in Firefox after restart Ubuntu Linux and I was able to login Firefox account.

Comment 17

[Marco Bonardo [:mak]]

It sounds like the problem was caused by the missing disk space and a ghost process.
It's unclear if everything is now working normally, or are you still noticing problems?

Comment 18

[Jury.Lysenko]

(In reply to Marco Bonardo [:mak] from comment #17)

It sounds like the problem was caused by the missing disk space and a ghost process.
It's unclear if everything is now working normally, or are you still noticing problems?

everything is now working normally, waiting next update)

Comment 19

[Marco Bonardo [:mak]]

Ok, I'm resolving the bug then, but if the issue returns you can reopen it.