wallpaper engine kde wallpaper picker not showing any wallpapers
I can no longer change my wallpaper engine wallpaper its just defaulting to my previously picked wallpaper

Solution:Jump to solution
figured it out it was my firewall/vpn software portmaster :mrpgSighFacePalm:
22 Replies
hmm seems like python websockets is missing even though i its installed on the image https://paste.centos.org/view/eb3127d3

pip install websockets?
tried that it just says i already have websockets installed on the system
hmm i tried rebasing to bazzite stable with no luck is wallpaper engine just broken right now?
it doesn't even see python installed .....

Looks like others have similar issues right now
I fought trying to get this to work for almost 4 solid hours lol 🙁
The weird thing is it works fine on my arch machine so it looks like it's a packing issue with bazzite
Guess I'll open an issue on the GitHub
https://github.com/ublue-os/bazzite/issues/3151
GitHub
KDE wallpaper engine wallpaper picker broken (works fine on Garuda)...
Describe the bug Wallpaper selector fails with a python error. This does not happen on my Garuda Linux install, suggesting a problem with bazzite's packaging of wallpaper engine What did you ex...
did you point it to your wallpaper engine folder
yup i pointed it to the same folder on both garuda and on bazzite
~.local/share/Steam
hmm looks like it might be something with my user as it doesnt happen on a fresh install on a vm not sure what though as i tried moving .config
to see if some config or env i set was the cause but no luck i also uninstalled ever pip package i had and i still get the error
Edit: same thing with .local
moving it and recreating it fresh does nothing
Is that it though?
Arnt all user configs and envs either in .config or .local?Solution
figured it out it was my firewall/vpn software portmaster :mrpgSighFacePalm:
I figured it out it wasn't port master it was homebrew! For some reason homebrew is braking system python packages
I reproduced this on a fresh install
Once I set up homebrew on my fresh install it broke wallpaper engine
@Kyle Gospo it's because of the python brew which is installed by the bling-cli just
The weird thing is this used to work I always had brew with python installed and it was working before
hmm i couldn't repoduce this in a vm and i noticed for some reason my
.bashrc
has these extra lines which the .bashrc in the vm don't have.
it looks like this is the culprit of the wallpaper engine issues though i have no clue where those lines came from and if there needed for something else
i tried running all the same ujust that i ran on my local install on the vm and i didn't get those lines in my .bashrc
and wallaper engine worked finehey guys, running into the same issue here
i dont run any firewall or vpn software

it also shows no items found somtiesm but assuming thats a separate bug

if you use hombrew it might be the same as what was happening to me
basically it was trying to use the hombrew python instead of the system one i deleted these lines from my
.bashrc
and it worked afterwords however I started getting issues with my brew installed cargo not being able to find its dependices but I rarely use it anyway and i guess i could use distrobox for thatt
brew is just cursed lolwait, so here's my bashrc
im assuming the last 3 exports are what's causing the issue
Specifically the Linuxbrew ones the other one is probably fine
wont that fuck up anything i installed via brew?
From what I understand.bashrc should NOT affect GUI apps though that's exactly what's happening for some reason
Bazzite already does all this in the /ect/profile.d files so it should be fine
so commenting out
theoretically shouldnt fuck shit up
cool
thank you
Yeah brew commands still work for me so like if I have python linked
python
still uses the brew one (in an interactive terminal) but for some reason brew programs can't see other brew programs unless I add the brew path in .bashrc that's why I had it I think and I forgot about it
So things like cargo that needed other brew libraries don't work now that I removed it from .bashrc but oh well
I guess of you really need the brew path in your bashrc you could unlink the brew python
brew unlink python
That should fix this particular issue with wallpaper engine but other issues may crop up I guess if brew overrides another system package like I remember one time having issues with systemd getting overridem by the. Brew one