Skip to content

Releases: aunetx/blur-my-shell

Version 36

18 May 07:57
Compare
Choose a tag to compare

What's Changed

  • Fix bug where blur rectangle is too big by @io12 in #240
  • Add color and noise to the blur effect by @aunetx, @JugadK and @RichardLuo0 in #246
  • Change the preferences layout (some preferences will be reset for all users, sorry :/ )

Full Changelog: v35...v36

Version 35

09 May 21:31
Compare
Choose a tag to compare

What's changed

  • fixed an issue with icons not adapting themselves to dark mode anymore

Full Changelog: v34...v35

Version 34

09 May 20:56
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v33...v34

Version 33

01 May 17:19
Compare
Choose a tag to compare

What's Changed

  • Fix error loading extension after locking screen by @pesader in #226
  • Fix error introduced by screenshot blur disable

New Contributors

Full Changelog: v32...v33

Version 32

14 Apr 11:54
Compare
Choose a tag to compare

What's Changed

  • added an option to select the theme to apply to overview elements (light or dark), which permits to better use the extension with a light background
  • fixed a bug with washed-out blur on the panel when changing the sigma, or changing between static or dynamic blur

Full Changelog: v31...v32

Version 31

11 Apr 12:18
Compare
Choose a tag to compare

What's Changed

  • corrected some inconsistencies
  • corrected problems with extensions.gnome.org rules regarding timeouts

Full Changelog: v30...v31

Version 30

07 Apr 16:05
Compare
Choose a tag to compare

What's Changed

  • Rewrite the preferences to a more modern look, and add options by @aunetx in #180

Full Changelog: v29...v30

Version 29

07 Apr 16:01
Compare
Choose a tag to compare

What's Changed

Full Changelog: v28...v29

Version 28

21 Feb 16:51
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v27...v28

Version 27

14 Jan 21:29
Compare
Choose a tag to compare

This release is intended for gnome 40/41 users, and just fixes bug #168 introduced by last release.

The issue was fixed by @CodedOre :)