Open jjgalvez opened 5 years ago
Confirm this issue, I spend a lot of time to find out this. It will be nice to have option to disable this feature.
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.
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
.
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 :-)
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 thedefault
profile and renamed it todefault-111
.
This workaround worked great for me, thanks
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