Skip to content

Fix blur background for wallpaper paths with special characters - #169

Open
Lija321 wants to merge 1 commit into
icedman:mainfrom
Lija321:fix-blur-background-uri-decode
Open

Fix blur background for wallpaper paths with special characters#169
Lija321 wants to merge 1 commit into
icedman:mainfrom
Lija321:fix-blur-background-uri-decode

Conversation

@Lija321

@Lija321 Lija321 commented Jul 12, 2026

Copy link
Copy Markdown

Problem

The blur-background feature passes the raw picture-uri gsettings value directly to the convert command. When the wallpaper filename contains characters that get percent-encoded in the URI (e.g. a space encoded as %20), ImageMagick cannot open the file:

convert: unable to open image '/home/user/.local/share/backgrounds/Acrylic%205.png': No such file or directory @ error/blob.c/OpenBlob/3710.
convert: no images defined `/tmp/searchlight-user-bg-blurred.jpg' @ error/deprecate.c/ConvertImageCommand/3366.

The blurred background image is never generated, so enabling "Blur background" silently does nothing (gnome-shell then logs Failed to load file:///tmp/searchlight-user-bg-blurred.jpg).

Fix

Decode the URI with GLib.filename_from_uri() in _updateBlurredBackground() so convert receives the actual filesystem path. Falls back to the raw value if the URI isn't a file:// URI.

Tested on GNOME Shell (Wayland) with a wallpaper named 2024-10-27-18-35-47-Acrylic 5.png — the blurred background now generates and displays correctly.

The blur-background feature passes the raw picture-uri gsettings value
to the convert command. When the wallpaper filename contains characters
that are percent-encoded in the URI (e.g. spaces as %20), imagemagick
fails to open the file and the blurred background is never generated.

Decode the URI with GLib.filename_from_uri() so convert receives the
actual filesystem path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant