You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Blur my Shell CPU/rendering complaint; update Utah to latest upstream fixes #992
A user reports Blur my Shell is buggy on their Utah machine. The machine runs GNOME Shell 51.1 and Blur my Shell v76 is enabled. I measured GNOME Shell intermittently at about 100% of one logical CPU; this does not establish Blur as the cause. The host journal also records errors from user-installed extensions, so attribution remains open.
Fix in progress
Utah main pins v76. Upstream master is b973ec8f (v77), beyond the v76 release, and includes popup first-open handling, modal blur, look-alike dock handling, and reduced painting allocations. The Utah branch updates Blur to that exact upstream commit.
Acceptance
Build and boot the updated Utah image on GNOME 51.1, verify Blur loads and renders, and measure the reported CPU behavior. Keep the ticket open until the runtime complaint is verified resolved or attributed elsewhere.
The reported machine is on GNOME Shell 51.1 with Blur my Shell v76 enabled. I updated the Utah pin to upstream master v77 (b973ec8f), which includes post-v76 fixes including reduced allocation while painting blur. The machine-side runtime behavior is not yet proven fixed; awaiting an image build and session verification.
changed the title [-]Blur my Shell is reported buggy; Utah pins upstream v72[/-][+]Blur my Shell CPU/rendering complaint; update Utah to latest upstream fixes[/+]on Oct 28, 2026
Prepared local commit 2404c01 on branch fix/blur-my-shell-latest-fixes: Blur My Shell now points to upstream v77 commit b973ec8f. It is not merged or deployed; the reported machine still runs v76. Source check, full just check (1233 tests), and pre-commit pass. Leave open until the updated image is booted and CPU/rendering behavior is checked.
Prepared extension refresh in local branch fix/blur-my-shell-latest-fixes, commit 71ca681 (not pushed or deployed): Blur my Shell v77. just check, pre-commit run --all-files, and the GNOME 51 source verifier passed. A package-build smoke attempt against the GNOME 51.1 host could not connect over SSH, so this pin is not runtime-verified there. The earlier host evidence did not establish Blur as the source of CPU usage; no extension settings were changed on the machine. Keeping this open pending image/runtime validation.
Update: PR #998 is open at cc55708a909cfe21c3c69ec67ef7544c8e3d3bae; CI contract is pending. The GNOME 51.1 host was unreachable over SSH during an isolated temporary package-build smoke attempt, so the updated pin is not yet runtime-verified on that machine. No extension settings were changed.
Activity
github-actions commentedon Oct 28, 2026
To accept this issue, comment
/triage accepted. To categorize, comment/area <area>or/kind <kind>.hanthor commentedon Oct 28, 2026
/kind bug
hanthor commentedon Oct 28, 2026
The reported machine is on GNOME Shell 51.1 with Blur my Shell v76 enabled. I updated the Utah pin to upstream master v77 (
b973ec8f), which includes post-v76 fixes including reduced allocation while painting blur. The machine-side runtime behavior is not yet proven fixed; awaiting an image build and session verification.[-]Blur my Shell is reported buggy; Utah pins upstream v72[/-][+]Blur my Shell CPU/rendering complaint; update Utah to latest upstream fixes[/+]hanthor commentedon Oct 28, 2026
Prepared local commit
2404c01on branchfix/blur-my-shell-latest-fixes: Blur My Shell now points to upstream v77 commitb973ec8f. It is not merged or deployed; the reported machine still runs v76. Source check, fulljust check(1233 tests), and pre-commit pass. Leave open until the updated image is booted and CPU/rendering behavior is checked.hanthor commentedon Oct 28, 2026
Update: this change is now in PR #998. Its required workflows are still pending; the machine has not received the updated image yet.
hanthor commentedon Oct 28, 2026
Prepared extension refresh in local branch
fix/blur-my-shell-latest-fixes, commit71ca681(not pushed or deployed): Blur my Shell v77.just check,pre-commit run --all-files, and the GNOME 51 source verifier passed. A package-build smoke attempt against the GNOME 51.1 host could not connect over SSH, so this pin is not runtime-verified there. The earlier host evidence did not establish Blur as the source of CPU usage; no extension settings were changed on the machine. Keeping this open pending image/runtime validation.hanthor commentedon Oct 28, 2026
Update: PR #998 is open at
cc55708a909cfe21c3c69ec67ef7544c8e3d3bae; CIcontractis pending. The GNOME 51.1 host was unreachable over SSH during an isolated temporary package-build smoke attempt, so the updated pin is not yet runtime-verified on that machine. No extension settings were changed.feat: document acceptance-evidence classification for CI/VMs vs physi…
hanthor commentedon Nov 7, 2026
Closing into #997. Blur my Shell was updated to upstream v77 in #998; GNOME Shell CPU attribution continues in #997.