Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

blur: toggling blur back on doesn't show until the window redraws

Open
  • Is something wrong?
#3,182 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
67/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
computer-graphics, desktop

Research direction

Start in plugins/blur/blur.cpp at the toggle callback and trace how adding a blur transformer updates the view; the report says removal takes effect immediately while addition waits for a redraw. Check how nearby code schedules repaint or damage after changing transformers. Done when toggling blur back on makes it visible immediately, with a regression test or reproducible check covering both toggle directions.

Written by the indexing model from the issue text.

Description

Wayfire version: 0.11.0 (Arch Linux package wayfire 0.11.0-1)
GPU: NVIDIA GeForce RTX 2060, nvidia-open-dkms 615.78.08, kernel 7.2

What happens

With blur enabled and a mouse-button toggle bound ([blur] toggle = <super> <alt> BTN_MIDDLE), toggling blur off on a translucent window takes effect immediately, but toggling it back on does not show until the window redraws. The window stays sharp until you type in it, move it, or something else repaints it; then the blur appears.

Steps to reproduce
  1. [blur] enabled with blur_by_default = type is "toplevel" and toggle = <super> <alt> BTN_MIDDLE.
  2. Open a translucent terminal (Alacritty with opacity < 1): the desktop behind it is blurred.
  3. Super+Alt + middle-click the terminal: the blur goes away at once (expected).
  4. Super+Alt + middle-click it again and leave the terminal idle: it stays sharp.
  5. Type a character in the terminal, or move the window a little: now the blur is back.
Expected

The blur shows right after step 4, the same way removing it shows right after step 3.

Notes

In plugins/blur/blur.cpp (v0.11.0) the toggle callback does the right thing (pop_transformer() when a blur_node_t is present, add_transformer() otherwise), so the blur node is added; it looks like adding the transformer does not schedule a repaint/damage of the view, while removing it does. Related but different from #1556 (that one was a keyboard binding on this button option).

Dominant language
C++
Stars
3.1k
Forks
247
Avg merge
8d 11h
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WayfireWM/wayfire

All issues in WayfireWM/wayfire

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.