Hello, I am new to bazzite, and I see that bazzite should work with wallpaper engine, tried to install it using the links from documentation, but it failed since bazzite now uses plasma 6. Can someone teach me how to install wallpaper engine on bazzite now that it has plasma 6, thanks.
1 Like
Heyy, fellow new user here. Also recently tried to install wallpaper engine, and only found a COPR repository from kylegospo. Who seems to be a maintainer/contributor for os-Blue OS’s. Currently his COPR only has KDE 5 packages, but hopefully he updates it to KDE 6 at some point.
In the meantime, I managed to cook up a step by step install guide to building the RPM for yourself. After much hardship, trying to sleuth the repository/COPR’s for proper install instructions. Or you could simply download my RPM in the git repository. I wouldn’t recommend that, as I have no knowledge of setting up GPG keys/checksums, so it’s up to you if you trust my RPM file.
There are a number of steps, but nothing overly technical, given that me, a newbie was able to create it lol.
Repository link: GitHub - Broken-Void/wallpaper-engine-kde-personal: Steps to reproduce an rpm of the project wallpaper-engine-kde by Catsout.
DISCLAIMER: I installed it on Aurora (Bluefin’s KDE), but I’d imagine it should work on Bazzite. Same rpm-ostree shenanigans.
Using your method on bazzite doesn’t seem to work.
Getting a bunch of dependency conflict errors about qt6 packages, mesa, etc.
I was checking the creator’s Github, and this issue’s open: plasma 6 support ? · Issue #367 · catsout/wallpaper-engine-kde-plugin · GitHub
The manual build steps (then copying the /plugin folder to ~/.local/share/plasma/wallpapers/wallpaper-engine-kde-plugin/) might work, if done in distrobox. Will try that and report back.
Huh, that’s annoying! I guess if it’s dependency issues, then Bazzite must have custom package versions. As the only requirements should be the ones in the wek spec, which should be standard packages to install/get.
( plasma-workspace gstreamer1-libav mpv-libs lz4 python3-websockets qt6-qtwebchannel-devel qt6-qtwebsockets-devel)
I am on the DX version of Aurora, so I might’ve had the -devel packages preinstalled from the base image, and Bazzite might not include these packages. But it should still grab them, regardless of the fact.
Yeah, seems like it.
I was able to manually build it and install it, but it’s complaining about qt6-websockets not running now… and I can’t install the -devel version since that’s what’s causing the conflicts, see image. My OS is in French but errors are in English.
The devs are probably aware of that since bazzite 3.0 didn’t include the module by default.
I’m gonna try building the .rpm following your guide.
I onnly tried the prebuilt one I built from the Github source.
Yeah scanning through it, it seems like it’s trying to install multiple sources of the file dependencies, but each are failing because it cannot acquire mesa-libEGL/-devel. According to your log, Bazzite installs its own mesa file, which matches the Github description (Custom patched Mesa), but the dependency files cannot detect the change with the package name.
I’ve tinkered a little bit, and I believe there is a way to disable/overwrite a base file like the patched Mesa, but I do not know if you can re-enable it once you’ve installed the other files and still keep the installed dependencies. If you want to try, I’d try searching about the rpm-ostree override commands, and mess around with that.
I’m gonna try building the rpm followinng you guide, then I’ll see if I wanna try the rpm-ostree stuff.
[EDIT] Building my own rpm causes the same issue. I couldn’t find anything on their Discord either.
Figured out a solution. Though I haven’t tested if it actually works on a full OS. As I just installed a docker file (CLI), that contains the Bazzite OS and tested it on that, and managed to get the wallpaper-plugin.rpm file to install the dependencies and wallpaper-plugin.
All I did was in a container like so: podman run -it docker.io/library/fedora. In there, run: sudo dnf install rpmrebuild. Then get the mesa-libEGL-devel rpm using,
Then running, the command rpmrebuild -e -p mesa-libEGL-devel-24.0.8-1.fc40.x86_64.rpm
Then locate line 54 (bottom right of terminal) and delete that line. As that is the line that is telling us we need that pesky Mesa file, when we already have it. Once deleted, press Esc and type :wq!, enter, and y enter.
Then just take that file to our main OS, and dump it anywhere. Open the terminal in that location, and run rpm-ostree install mesa-libEGL-devel-24.0.8-1.fc40.x86_64.rpm.
Then just install the rpm for the wallpaper-plugin, and it SHOULD install the dependencies, without any errors!
Again, I only ran this in a docker container, so it might not work the same in the actual OS. But I might test it on a VM and report back.
Have a bazzite VM I can use to test this, let me try and I’ll let you know!
Note that I used your Github tutorial on an Aurora machine and it works perfectly even in Wayland, so it should work fine on Fedora Kinoite / Aurora using your guide, just that bazzite seems to use modified packages for mesa.
Did you delete the right line in the devel rpm file? This should be the line you need to remove: Requires: mesa-libEGL(x86-64) = 24.0.8-1.fc40
I’m currently trying to spin up a VM for bazzite to test myself.
Figured out my mistake, sorry! Was in the wrong container folder, it installed fine.
Now installing the wallpaper engine rpm.
[EDIT] It works! Not sure if it’ll cause issues to install the mesa .rpm alongside bazzite’s version in the longrun though, mine’s a VM so it doesn’t matter, but for new users.
1 Like
Nice! And I believe there should not be more than one Mesa file? The only we installed was the Devel file, which should not conflict with anything. Since the provided Mesa file from Bazzite is the non devel Mesa file, and I don’t think installing the mesa-devel file would pull the other non devel mesa file? As it would’ve just spit out an error like in the past.
1 Like
Very good. You’re right. Thank you for your help, i’ll be able to help my pals install it. 
The only issues with all these manual installs, is that this Mesa-devel file and the wallpaper-rpm file we manually changed/installed, will not be updated automatically. This shouldn’t be an issue, for the wallpaper-engine plugin at least, as it does not seem to be in active development. The Mesa-devel file will be periodically updated, so if any packages you install in the future which requires a newer version of this file, I am unsure how that would act. But I doubt you’ll be needing it, as you shouldn’t be layering packages too much onto your immutable/atomic OS, ideally.
And no worries, happy to help, and a good learning experience for me.
1 Like