Bug: Maximized always-on-top window is incorrectly stacked below another monitor's window

Open
#855 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
50/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c
Domain
desktop

Research direction

Start by reproducing the issue on Linux Mint 21.3 with Muffin 6.0.1 using the listed Firefox and PhpStorm multi-monitor steps. Trace the relevant window-stacking behavior in libmuffin and the sample WM binary, muffin, then verify that a maximized _NET_WM_STATE_ABOVE window remains above focused windows on another monitor.

Written by the indexing model from the issue text.

Description

Distribution

Mint 21.3

Package version

6.0.5

Graphics hardware in use

Radeon RX 5600 OEM/5600 XT / 5700/5700 XT

Frequency

Always

Bug description

On Linux Mint 21.3 (Virginia), Cinnamon with Muffin 6.0.1, a maximized Firefox window with _NET_WM_STATE_ABOVE can be incorrectly covered by a PhpStorm window on another monitor when that window receives focus.

The _NET_WM_STATE_ABOVE property remains set, but Muffin nevertheless places the PhpStorm window above Firefox in the stacking order.

The bug does not occur if _NET_WM_STATE_ABOVE is enabled while Firefox is not maximized and Firefox is maximized afterwards.

Steps to reproduce
  • Open Firefox on one monitor and maximize it.
  • Enable "Always on Top".
  • Open PhpStorm with windows on both monitors.
  • Focus a PhpStorm window on the other monitor.
  • Observe that PhpStorm is stacked above the Firefox window despite Firefox having _NET_WM_STATE_ABOVE.
Expected behavior

Always on top

Additional information

No response

Dominant language
C
Stars
245
Forks
127
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 linuxmint/muffin

All issues in linuxmint/muffin

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.