[Bug] Blocky / pixelated backdrop blur in Control Center and UI layers
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, rust
Research direction
Start by tracing how backdrop blur surfaces are resolved through NVMTL, especially the CABackdropLayer filtering and texture downsampling path mentioned in the report. Reproduce by opening Control Center and inspect whether the same pixelation appears in Spotlight or menu drop-downs; done means those blur surfaces render smoothly without the coarse pixel blocks.
Written by the indexing model from the issue text.
Description
Send logs report ID
NM-NO
Environment
OS: macOS 15.8.1 (Build 24H32)
Driver Version: 2.5.3 (NVAccel / NVRMFB / NVRMAGDC)
CPU: AMD Ryzen 7 3800X
GPU: NVIDIA GeForce RTX 3080 10GB (Device ID: 10DE:2206)
Boot-args: keepsyms=1 debug.nvrmfb_flip_latch=2 (tested with and without -nvkmsnosmooth)
What happens
Noticed visual corruption on UI surfaces that use backdrop blur (most obvious in Control Center, spotlight and menu drop-downs).
Instead of a smooth Gaussian blur gradient, the background breaks down into large pixelated blocks / coarse dithering tiles. Looks like an issue with texture downsampling or improper filter pass in CABackdropLayer when resolving through NVMTL.
Reproduces consistently on desktop:
- Open Control Center from the menu bar.
- The background behind the modules (Wi-Fi, Bluetooth, sound/display sliders) renders as a chunky pixel grid instead of smooth glass blur.
Written by you
- I wrote this report myself. AI-written issues are closed without review (see CONTRIBUTING.md).
App or game (if it is one)
No response
Did you change anything yourself?
No response
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- Avg merge
- 21h 20m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nullmoth/nvidia-macos-driver
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nullmoth/nvidia-macos-driver#141 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nullmoth/nvidia-macos-driver#28 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
nullmoth/nvidia-macos-driver#375 · 1 reaction ·
Maintainers usually reply within 2 days
-
bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
nullmoth/nvidia-macos-driver#374 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nullmoth/nvidia-macos-driver#373 ·
Maintainers usually reply within 2 days
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
bug: workspace access hint suggests a --subject command that fails for hyphen-leading OIDC subjectsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
A-FFI C-Testing D-Straightforward S-Ready
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
docs priority:P3 size:XS
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Appimage ConventionsOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day