pywalfox: Update seems to have broken the plugin
I updated pywalfox with
pip3 --user --upgrade pywalfox
and ran git pull origin master in the directory I cloned pywalfox into.
When I open the plugin settings, it fails to fetch pywal colors, and the buttons for enabling the css files hang.
Every time I open Firefox, pywalfox prompts me for an update, even though I have already ran the steps above.
The url bar and drop down menu are no longer themed for me, suggesting the css is no longer working
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 42 (14 by maintainers)
Commits related to this issue
- Updated Installation section with temp fix to #31 — committed to Frewacom/pywalfox by Frewacom 4 years ago
- Nicer formatting in heads-up regarding Issue #31 — committed to Frewacom/pywalfox by johanengstrand 4 years ago
- Potential fix for Frewacom/pywalfox#34, Frewacom/pywalfox#33 and Frewacom/pywalfox#31 — committed to Frewacom/pywalfox-native by Frewacom 4 years ago
Hello again everyone, I had the same issue on my laptop when I updated it just now, and since I was able to solve it on my desktop, I kept track of exactly how I solved it on my laptop. Here’s what I came up with, that successfully fixed the issue on my laptop:
uninstall the pywalfox extension in Firefox uninstall Firefox uninstall the pip module for pywalfox
sudo tree -f / | grep pywalfoxand delete anything that shows up reboot (probably not necessary) install Firefox install pywalfox extension in FirefoxWITH FIREFOX OPEN:
pip install --upgrade pywalfoxandsudo pip install --upgrade pywalfox(did both with and without sudo cause i was curious, both of them installed with out saying it was already installed… I don’t know much about pip but maybe this is important)pywalfox setupclose Firefox open Firefox, click fetch colors on pywalfox settings pageedit: I’m sure most of this is not necessary, but one or two of these steps are certainly what solves the issue.
I have pushed an update to the native messaging application (version 2.6) that I hope should fix this issue. It no longer requires you to have
pywalfoxin yourPATH. Instead, it relies on having one ofpython/python3/python2.7in yourPATH, which a majority of you should have by default.@Paul-Houser can confirm that this fixed the issue on both my systems, and the second one worked without a reboot!