Closed kawazoe closed 3 months ago
Works for me on Plasma 6.0.2. Does the stock blur effect also not show up when you exclude unsupported effects?
No, the stock blur is supported and works as expected.
I have no idea what could be the cause. I tested it on a fresh Arch installation in a VM and it worked. Maybe there's an issue with the KWin config? Rename ~/.config/kwinrc
to something else and log out.
If that doesn't work, try building the develop
branch. I made it so that BlurEffect::supported() always returns true.
EDIT: What happens if you just enable the effect even though it's unsupported? Does it work?
EDIT: What happens if you just enable the effect even though it's unsupported? Does it work?
Nah, nothing happens, though I can go into the config panel and change settings.
The dev build works just fine too. I wanted to check into the supported function. I'm not setup to debug C++ so I tried to use qCWarning
to log the return value of the three function calls you do in the supported()
method, but I can't see them in journalctl. Where do I need to go to check those logs?
EDIT: Scratch that... It looks like my new build isn't getting loaded without restaring the plasma workspace. I'll get back to you once I get that working.
EDIT2: Ok, I did not expect that:
kwin_wayland[7626]: kwin_effect_forceblur: GLFramebuffer::blitSupported() -> true
kwin_wayland[7626]: kwin_effect_forceblur: GLFramebuffer::supported() -> true
kwin_wayland[7626]: kwin_effect_forceblur: effects->isOpenGLCompositing() -> true
And that build works.
Could there be an issue with the AUR package?
Try the AUR package again, maybe it was just necessary to rebuild the effect due to some package updates (if you updated the system after installing it). Make sure to force a rebuild, otherwise the package manager may just install the already built version.
Welp... Ok, I just learned a few things <_<
I'm on Garuda, which uses chaotic-aur. I don't know why I never noticed, by I was installing your package from the chaotic-aur repo instead of building it locally. Forcing paru to use the AUR package with paru -Sa kwin-effects-forceblur
gives me a build error:
==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.
error: failed to build 'kwin-effects-forceblur-1.1.1-2':
error: packages failed to build: kwin-effects-forceblur-1.1.1-2
Obviously I have all of the dependencies listed in the PKGBUILD, and I can build it manually. My best guess is that there's something wrong with the PKGBUILD, maybe some missing dependency that chaotic has by default on an older version in the container image they use to build packages. This could explain why they have a valid build, but it doesn't actually work when you install it.
Installing debugedit makes the AUR build pass, and the resulting package is working as expected.
@kawazoe It is an issue on your side. You need to have base-devel
installed to build packages
Also if you don't know this: You have to rebuild any compiled package (for example with paru -S --rebuild
) if you update a dependency from the repos. That's just how Arch works.
A way to get notified of this is to use https://github.com/maximbaz/rebuild-detector
Looks like the Chaotic-AUR package was built for Plasma 6.0.1, so that's probably why it doesn't work. https://builds.garudalinux.org/repos/chaotic-aur/logs/kwin-effects-forceblur.log
I tried installing the AUR package and it doesn't appear in the Desktop Effects even after a reboot.
It looks like the files are in the right location, and I'm getting this warning in journalctl so I'm assuming the plugin is getting loaded:
EDIT: I just noticed it is showing up in the list of "unsuported effects". I'm running KDE 6.0.2 on wayland. Here's the output from the infocenter wayland Window Manager section: