search

flathub / net.waterfox.waterfox

https://flathub.org/apps/details/net.waterfox.waterfox
4 stars 1 forks source link

"Waterfox is already running, but isn't responding." #5

Closed FloridaMan7588 closed 1 year ago

FloridaMan7588 commented 1 year ago

When opening a URL from another application using xdg-open, an error occurs stating

"Waterfox is already running, but is not responding. To use Waterfox, you must first close the existing Waterfox process, restart your device, or use a different profile."

When running xdg-open from the command line, the error "JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory." is thrown.

I believe this has something to do with the browser expecting the '.waterfox' directory to be in your home folder. I will look for a remedy through configuration, but as profile names are random ASCII spam, this may only be resolved by changing from using persist to filesystem in the finish args. This is what upstream is doing with the official Firefox package.

FloridaMan7588 commented 1 year ago

After some testing, I've found that switching from --persist to --filesystem does not help, or at least on my laptop running Fedora Silverblue 37. I will run some tests in a fresh VM on my Arch machine when I get some time later today. Otherwise, I haven't found a preference that will reliably set the ~/.waterfox directory to elsewhere.

soko7awen commented 1 year ago

When given full session bus access the error does not occur. I am currently attempting to find out which policy rule would be able to resolve the issue specifically.

FloridaMan7588 commented 1 year ago

Interesting, I thought this was a filesystem issue at first but the bus access issue would be interesting to look into. I'll do some testing as well.

FloridaMan7588 commented 1 year ago

I did some digging with bustle (Very useful program), and found that the problem is caused by an upstream issue, although it could possibly be fixed with a policy rule. It was caused by the application using a different name than what I assumed on the session bus. At build time it was set to use the session name of org.mozilla.waterfox as opposed to the net.waterfox.waterfox name that follows the reverse DNS formatting. I will submit a PR with the own-name changed in the manifest, but hopefully this can be resolved with a policy or preference change in about:config or similar. From the looks of it, it isn't in the config but it may be fixed in another way. Until then, I will change the manifest directly.

FloridaMan7588 commented 1 year ago

Issue is fixed by #10, please update to the latest version* :)

*When the build finishes lol