Blur My Shell settings conflict with Dock mode (Option to separate panel blur from dock blur with blur my shell)

[kusaida]

When Simple Taskbar is used in Dock mode together with Blur My Shell, the Dock seems to use the blur settings from the Top Panel instead of its own Dock settings, because of this, the top panel with the option enabled in Blur My Shell, which causes the panel to lose transparency/blur when the window is approaching it, does not work when the simple taskbar Dock is enabled. This behavior only occurs when the Transparent background style is enabled.

[Sultech]

Thanks. The first part is right, and it isn't something Simple Taskbar controls, Blur My Shell blurs the Dock through its Panel component, which uses one shared set of Panel settings for every panel. There's no per-panel config in it, so the Dock inherits the top panel's settings by design.

The second part I tested and can't reproduce, the top panel still reacts normally with the Dock enabled.

Which of the two Override background dynamically modes do you have selected? The first blurs the panel when a window is near and leaves it transparent otherwise, so I want to be sure we mean the same thing. A short screen recording with the Dock on and off would help too.

Also if you want to disable the blur for the dock you can here :

[kusaida]

Screencast.From.2026-09-14.19-58-12.webm

Also if you want to disable the blur for the dock you can here :

I want to disable it for the top panel:(

[Sultech]

I’m running the latest Blur My Shell version directly from their GitHub repo, so I guess that issue doesn’t happen there.

For the other issue, I’ll need to make a PR to Blur My Shell so it can support blurring the Simple Taskbar Dock separately instead of treating it like the panel. I’ll look into doing that soon.

[kusaida]

Thanks btw! I'll try your solution. It would be very useful to have separate blur settings for the Dock. Your extension is awesome anyway.

[kusaida]

Maybe I found a way to solve this issue before you make a PR.

Right after opening this issue, I started using [Kiwi](https://github.com/kem-a/kiwi-kemma), and its panel transparency implementation seems to completely solve this problem. It dynamically applies the panel background and opacity, without relying on Blur My Shell to handle the panel's transparency.

In particular, apps/panelTransparency.js has an updatePanelStyle() function that calculates the panel background and applies the opacity directly to Main.panel, while also handling changes when windows touch the panel.

Maybe something similar could be implemented in Simple Taskbar, so the dock/panel transparency could be controlled independently and would not inherit or conflict with Blur My Shell's panel settings. It could also allow the panel's color and transparency to be controlled through Simple Taskbar's own built-in panel appearance settings, while Blur My Shell continues to handle the blur itself.

I don't know enough about GNOME Shell internals to say that this is the best approach, but I started using Kiwi specifically because of this issue, and in practice it solves it.

panel.webm

Also, maybe you could consider adding support for dock-related extensions, including Kiwi and Dynamic Music Pill. I could open a separate issue for this if you have plans to support something like that.

[Sultech]

We already have dynamic transparency available per mode in the extension, so I believe you should already be able to achieve this with the current settings.

[kusaida]

Nah, they’re not available while Blur My Shell is active.

[Sultech]

Yes, that’s true, although in the video it looks like you’re not using blur. Either way, I’ve already made a PR aunetx/blur-my-shell#1025 for Blur My Shell, and once that’s merged and released, Dock blur and panel blur will be handled separately.

[kusaida]

Yay, that’s good to hear!

What about support for other dock-related extensions like Kiwi and Dynamic Music Pill? Do they require the same kind of integration process, or would supporting one of them make it easier to support the others as well?

[Sultech]

They’d each require proper integration with the individual extension. Supporting one wouldn’t automatically make the others work, although some of the underlying approach might be reusable depending on how each extension is implemented.