search

Frewacom / pywalfox

Dynamic theming of Firefox (and Thunderbird) using your Pywal colors
https://addons.mozilla.org/en-US/firefox/addon/pywalfox/
Mozilla Public License 2.0
582 stars 12 forks source link

Native messenger connection error on NixOS #82

Closed TripleK2004 closed 2 years ago

TripleK2004 commented 2 years ago

I have installed the latest version of pywalfox on PyPi on NixOS and the socket seem to work properly with the verbose mode enabled. And the socket is also active in /tmp , but the extension doesnt seem to find the binary or the socket ? I also had to remove the function which makes main.sh executable sincet nix uses an immutable file system. But i am later making the script executable later

The following error occured when trying to connect to the native messenger: None

pywalfox binary is in $PATH and the socket in /tmp , what else is required for pywalfox extension to function ?

image

and i am getting ERROR:root:Failed to connect to socket: Connection refused upon update

Frewacom commented 2 years ago

Firefox probably does not have the executable in its PATH when it is running (even though you have it correctly setup). You should be able to confirm this by looking at the Browser Console.

There is another version of the native messenger that is currently only available from the test repository of PyPi (see https://github.com/Frewacom/pywalfox/issues/68#issuecomment-873381669). This version starts the pywalfox executable directly using an absolute path, thus you should have no issues with main.sh. Hopefully, it should fix the connection error as well.

TripleK2004 commented 2 years ago

Firefox probably does not have the executable in its PATH when it is running (even though you have it correctly setup). You should be able to confirm this by looking at the Browser Console.

There is another version of the native messenger that is currently only available from the test repository of PyPi (see #68 (comment)). This version starts the pywalfox executable directly using an absolute path, thus you should have no issues with main.sh. Hopefully, it should fix the connection error as well.

Yep that works, thanks mate : ) Keep up the good work