Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webbookmarks is causing issues with Firefox #108

Open
jjgalvez opened this issue Oct 29, 2018 · 5 comments
Open

webbookmarks is causing issues with Firefox #108

jjgalvez opened this issue Oct 29, 2018 · 5 comments

Comments

@jjgalvez
Copy link

using the latest branch from git via AUR with arch. After the recent firefox update it looks like Gnomenu's opening of FFs places.sqllite file is causing issues with FF. Can this be turned off from within Gno-menu? although I am sure it is a valuable feature it is one I never use. Is there a setting I can set ?

Thanks in advance

@vantu5z
Copy link
Contributor

vantu5z commented Nov 1, 2018

Confirm this issue, I spend a lot of time to find out this.
It will be nice to have option to disable this feature.

@mabod
Copy link

mabod commented Jan 2, 2019

I can confirm. gno-menu is reading places.sqlite and creates a .parentlock file. when firefox is started afterwards it can not access its bookmarks. Very annoying.

@mabod
Copy link

mabod commented Jan 2, 2019

I found a work around for me: gno-menu is only locking the bookmarks for the firefox profile called "default". If I rename my default profile to something else, gno-menu and firefox have no issue.

I started firefox -ProfileManager, selected the default profile and renamed it to default-111.

@archont00
Copy link

Indeed, this is a show-stopper for the extension.

So far, the easiest is

$ killall -HUP gnome-shell & firefox

Firefox reads the places.sqlite before the extension gets involved :-)

@jjgalvez
Copy link
Author

jjgalvez commented Jan 7, 2019

I found a work around for me: gno-menu is only locking the bookmarks for the firefox profile called "default". If I rename my default profile to something else, gno-menu and firefox have no issue.

I started firefox -ProfileManager, selected the default profile and renamed it to default-111.

This workaround worked great for me, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants