Closed vyrus714 closed 5 years ago
On kde the dbus is used to set the wallpaper so no wonder it's not set at all. Are you running the release binary or the script?
I just tested on my linux build machine and there I do have the SessionBus attribute in dbus as expected, so I have no idea what is going wrong on your end.
Running with the script version. I made a simple script to test the SessionBus value in the dbus module. When specifying to run with python2 the attribute was there, but when i use python3 it is not. Strange, since the superpaper is written for python 3. I tested superpaper with python 2, just to see what would happen, and it spits out this error:
File "superpaper.pyw", line 2507 SyntaxError: Non-ASCII character '\xc3' in file superpaper.pyw on line 2507, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
So it does seem to get further down, just eventually runs into something python2 doesn't like.
Yeah there are multiple things relying on Python 3.
Sounds like there's something funky going on with your python 3 bindings to dbus, can you check that they're installed correctly and up to date?
Sorry for the delay. Did a little digging and found that I had python2-dbus installed but not python-dbus. I did install this via an AUR snapshot someone put up, but had uninstalled & reinstalled when I switched to the script version as I remembered I needed those packages. So somewhere in there, I guess the python 3 version of the library didn't get installed. After I took care of that, I finally had no errors, and it did set the wallpaper! It only did that for the primary display though, and it had the wrong image, but I'll file another issue for that.
When applying a profile I get an exception and the wallpaper is never applied:
I do have temp images in the temp folder, however any offsets i put into the profile don't apply until I quit out and restart the whole program (possibly some relevant thread crashes due to the above exception?). Not sure if it's related.