The old "The bookmarks and history system will not be functional because one of firefox's files is in use by another application" problem
As per the title, I have been experiencing this for a day. I am running:
firefox 62.0-1 on Debian Stretch (stable)
The two first pages of Google were of no use. The last measure used was to purge firefox and ~/.mozilla and ~/.cache/mozilla and reinstall to no avail.
I did find something about NFS systems, but I am running ext4.
Many thanks
Some more info
I downloaded the nightly build, and it runs fine. I wonder if I updated Firefox sometime and this happened?
Upravil(a) kabanus dňa
Všetky odpovede (8)
Thank you, but as per my question, I have attempted all solutions listed on the first page of Google. That was the first. To be clear I tried:
1. Regenerating places.sqlite 2. Creating a new profile 3. Completely removing all of Firefox, including ~/.mozilla completely, than reinstalling.
I have rebooted several times in between.
Thank you.
Upravil(a) kabanus dňa
When you remove ~/.mozilla and ~/.cache/mozilla then I would assume that this will be fixed.
Did you check the permissions and ownership of files and folders that Firefox creates when you start Firefox?
You can also try to start Firefox via a terminal window to see if that give more helpful messages.
I would have assumed that as well, but no luck.
I did try to run firefox from the terminal, but there were no special messages.
The nightly version creates the exact same folders there with no problem.
What if any clues/messages do you get on the 'other application' . This is often a complaint from a multi instance of something or a concurrent download or similar.
That error message is the only clue. I tried to use lsof to look at places.sqlite, but it could find nothing using it.
Is there someway to run Firefox in some kind of debug mode from the terminal so it spews out more informative errors?
Upravil(a) kabanus dňa
there is: ``` user@host $ firefox --headless OR firefox --start-debugger-server --jsconsole | --jsdebugger ```
Some context on the later switch:
``` --start-debugger-server [ws:][ <port> | <path> ] Start the debugger server on a TCP port or Unix domain socket path. Defaults to TCP port 6000. Use WebSocket protocol if ws: prefix is specified.
and the js switches launch the respective console and toolbox respectively.
```
Thanks, I ran the debugger with the jsconsole and finally got something, see below. Looks like it's not able to connect to the database, but I do not see why. I am using nightly all this while easily though.
Chrome.manifest:1 Bootstrapped manifest not allowed to use 'resource' directive. chrome.manifest:7 Bootstrapped manifest not allowed to use 'resource' directive. chrome.manifest:2 SyntaxError: "0"-prefixed octal literals and octal escape sequences are deprecated; for octal literals use the "0o" prefix instead[Learn More] addonsInfo.js:91:64 Contract ID '@mozilla.org/toolkit/addonsInfo-clh;1' was registered as a command line handler for entry 'a-addons-info', but could not be created. [Show/hide message details.] db is undefined Bookmarks.jsm:84 promiseTagsFolderId resource://gre/modules/Bookmarks.jsm:84:7 InterpretGeneratorResume self-hosted:1269:8 next self-hosted:1224:9 [Show/hide message details.] conn is undefined NewTabUtils.jsm:1239 executePlacesQuery resource://gre/modules/NewTabUtils.jsm:1239:5 InterpretGeneratorResume self-hosted:1269:8 next self-hosted:1224:9