Blur my Shell now blurs popups, requires corner radius

[DarkGhostHunter]

Describe the bug

Blur my Shell was updated on April to version 72. Just landed the update now on latest.

The problem is that Blur my Shell activates Popup blur, which seems as an incomplete implementation (broken round corners require bash script, sub-menus are laggy, transparency stacks, etc). For this reason, it should be disabled by default until behavior and performance is fixed.

What did you expect to happen?

To be disabled by default.

Output of bootc status

Staged image: ghcr.io/ublue-os/bluefin-dx:latest
        Digest: sha256:de4aebc3039b8ac00f6bc761d663197a56b8bb0953cb7c8c6fe16e5e92a4d7f3 (amd64)
       Version: latest-44.20260704.1 (2026-07-04T05:41:40Z)

● Booted image: ghcr.io/ublue-os/bluefin-dx:latest
        Digest: sha256:e4e3550e3493090d6782306adccff524342148687da5ee287871bd686c31b9ab (amd64)
       Version: latest-44.20260703.1 (2026-07-03T11:44:29Z)
 UpdateVersion: latest-44.20260704.1 (2026-07-04T05:41:40Z)
  UpdateDigest: sha256:de4aebc3039b8ac00f6bc761d663197a56b8bb0953cb7c8c6fe16e5e92a4d7f3

  Rollback image: ghcr.io/ublue-os/bluefin-dx:latest
          Digest: sha256:a67945377903f412c8d97cbd205bb9b9cc3b31f3ac8a551d312d7c0e93bac9be (amd64)
         Version: latest-44.20260701 (2026-07-01T05:32:19Z)
   UpdateVersion: latest-44.20260702.1 (2026-07-02T08:03:48Z)
    UpdateDigest: sha256:35f8bcc7d9b618a6e598b398ffbff1d496e4e26075f2dbd29267a095565a6826

Output of groups

developer wheel docker incus-admin lxd libvirt

Extra information or context

Isn't supposed for system extension to be up-to-date? Weird that the latest release took ~3 months to and on the image.

[DarkGhostHunter]

Related ublue-os/bazzite#5070

[IvanVeloz]

This is an upstream bug. To fix, it, a library has to be built against your exact Gnome version, per the author's guide.

This sounds like the perfect use case for an immutable OS. I'm going to try building it in CI for my private Bluefin image, and see how it goes. Will report back if I get it to work.

[IvanVeloz]

For folks using the image template, you can use the attached script during your build.sh. Just one thing, the script modifies /usr/lib/os-release to work around a bug in the upstream build script.

build-blurmyshell.sh

I actually did it as its own separate build stage:

Edit: this is horribly space-inefficient. But it works and proves the concept. In the next comment I show a better way of doing it. It's what I am running now.

Containerfile

# Allow build scripts to be referenced without being copied into the final image
FROM scratch AS ctx
COPY build_files /

FROM ghcr.io/ublue-os/bluefin-dx:latest AS blurmyshellbuilder
RUN --mount=type=bind,from=ctx,source=/,target=/ctx \
    --mount=type=cache,dst=/var/cache \
    --mount=type=cache,dst=/var/log \
    --mount=type=tmpfs,dst=/tmp \
    /ctx/build-blurmyshell.sh

# Base Image
FROM ghcr.io/ublue-os/bluefin-dx:latest

# [...]

RUN --mount=type=bind,from=ctx,source=/,target=/ctx \
    --mount=type=cache,dst=/var/cache \
    --mount=type=cache,dst=/var/log \
    --mount=type=tmpfs,dst=/tmp \
    /ctx/build.sh

COPY --from=blurmyshellbuilder --exclude=/usr/lib/os-release /usr/ /usr/

# [...]

### LINTING
## Verify final image and contents are correct.
RUN bootc container lint

Running it on a VM shows promising results:

[IvanVeloz]

Here it is optimized so it doesn't duplicate /usr. Takes half the space now, as it should.
Please note that I do a little hack with /opt on the Containerfile, totally unrelated to this, so don't copy that. The rest can be copied over. License is Apache 2.0 like the original template.

build-blurmyshell.sh
Containerfile_remove_txt.txt

[DarkGhostHunter]

I'm more inclined to just disable it by default, given the cumbersome/incomplete implementation rather than trying to get around it and maintain a script.

[castrojo]

What is the version supposed to be set at?

[castrojo]

We'll set this:

[org.gnome.shell.extensions.blur-my-shell.popup] 
blur=false 

[IvanVeloz]

That works too!!!

I thought this setting was enabled all along. Only noticed it when it broke.

[castrojo]

Nice thing about people volunteering for a latest branch is we were able to catch this before it got out to the stable releases ....

Smooooooooth ....

[DarkGhostHunter]

Nice thing about people volunteering for a latest branch is we were able to catch this before it got out to the stable releases ....

Smooooooooth ....

Wait what? Is this not stable? 😆

BTW, this extension was released in April. Does this mean that extension versions are no updating instantly?

[castrojo]

No clue, if no one reports things I'm not sure.

[castrojo]

#4830

Alright one let's see if this does the trick.

[castrojo]

ok this is pushing out on latest now, lmk if that fixes it and I'll push out new stable builds.