
Plasma 5 Windows Blur
Source (link to git-repo or to original if based on someone elses unmodified work):
Description:
This is my first upload on this site.
To apply this theme you need to:
Have OpenGL enabled
Import the "BlurRule" to kwin's rules
Download and make executable "Enable Blur.sh"
put "Enable Blur.sh" at startup.
This theme is like Oxygen-transparent but it works on all themes
Thanks to Cyelis1224 (https://www.pling.com/u/cyelis1224) for improving my script!! Last changelog:
To apply this theme you need to:
Have OpenGL enabled
Import the "BlurRule" to kwin's rules
Download and make executable "Enable Blur.sh"
put "Enable Blur.sh" at startup.
This theme is like Oxygen-transparent but it works on all themes
Thanks to Cyelis1224 (https://www.pling.com/u/cyelis1224) for improving my script!!
Version 2.0.0
• Fixed the bug of the two rules instead of one
• Updated the script code to work now with almost all windows
Thanks to Refused (https://www.pling.com/u/refused) for improving my script.
Ratings & Comments
51 Comments
8 Instant magic, makes your system look super modern.
Sorry for sounding rude, but how to I disable the effect? I don't like really like the effect and can't figure out how to disable it. Could someone please help me with this? Sorry for sounding rude.
Is it possible to configure the noise level of the blur effect? I would like to make the windows more blurry, the default blur is very subtle!
You can change the opacity of windows by changing the kwin rule in settings! (:
Am I freaking out and seeing things, or is transparency actually applied to SVG icons and file thumbnails as well?
it's applied to the entire window!
Updates to Plasma seem to no longer work for this. but i have made an updated blur.sh file that you can use to get this same effect while still using the window rules available in this post. see below for updated blur.sh script! just past in a text editor and name blur.sh and then set the script to autostart at login to be able to always have blur enabled. #!/bin/bash while true; sleep 0.5 wid=$(xdotool getactivewindow); do xprop -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 -id $wid; done
Wow! Thank you. I updated the code and I gave you credits on description!
you could simplify the whole process and fix your old bug where certain apps like chrome dont blue by installing xdotool and doing this #! /bin/bash while true; do sleep 0.5 a=$(xdotool getactivewindow) xprop -id "$a" -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 set -u done just a thought
blur* not blue
How to enable this only for tltebar?
The easiest way to blur only the titlebar is to install a different window decoration. If you're using the default Breeze window decoration I recommend just installing BreezeEnhanced. It has transparency and blur features as well as a bunch of other useful customization options.
I want something that follows the system blur effect
Yep, BreezeEnhanced just uses the in-built desktop blur effect. It has a setting in it's options to set whatever opacity you want. And if blur is turned on in your system settings, then it will automatically take effect.
Man, thanks too much, I wasn't finding it in the KDE System Settings "Get New" dialog. I will try this BreezeEnhanced right now
https://github.com/tsujan/BreezeEnhanced Here's the window decoration. Note that you don't have to use the 'MacOS buttons' like in the screenshot. If you just leave that option unchecked it will look exactly like your normal Breeze titlebar. It will also respect your color scheme just like the normal Breeze.
Thank you! It works fine with standard kde windows (dolphin ,settings, etc) but I see an error with chrome (and, consequently, chrome is not being blurred): xprop: error: No window with name Plasma 5 Windows Blur - KDE Store - Google Chrome exists! This is due to the window name which changes according to the current tab: WM_NAME(UTF8_STRING) = "Plasma 5 Windows Blur - KDE Store - Google Chrome" _NET_WM_NAME(UTF8_STRING) = "Plasma 5 Windows Blur - KDE Store - Google Chrome" Bu maybe WM_CLASS should be used? WM_CLASS(STRING) = "google-chrome", "Google-chrome"
I found out that using the window id retrieved through xdotool is better, and it seems to make errors disappear. Furthermore, it is working with chrome as well. while true; do sleep 0.5 a=$(xprop -id $(xprop -root _NET_ACTIVE_WINDOW | cut -d ' ' -f 5) WM_NAME | sed -e 's/.*"\(.*\)".*/\1/') # can have more ids for the same window name! ids=$(xdotool search -name "$a") id_arr=($(echo $ids | tr " " "\n")) for id in "${id_arr[@]}" do xprop -id "$id" -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 done set -u done
Hey, thank you for this suggestion, that's the best suggestion I've ever seen. Soon I will try this and update the script to download. Let me now if you want credits!(:
You are welcome, and so are the credits ;) I am experiencing another issue with windows having strange characters on the name. For instance, sublimetext with unsaved documents has a title such as: Untitled • - Sublime Text (UNREGISTERED) That dot 'breaks' the name string. It would be nice to find all these corner-cases :D
why would you not just download xdotool and then simply the script by doing it like this? #! /bin/bash while true; do sleep 0.5 a=$(xdotool getactivewindow) xprop -id "$a" -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 set -u done
9 +
9 +
Thank you for this!!! screenshot - https://imgur.com/a/eWIsDF0
(: