canonical/mir

`grimshot save output` captures all outputs, not just the active one

Open

#4,014 opened on Jun 13, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (137 forks)auto 404
Good first issue

Repository metrics

Stars
 (775 stars)
PR merge metrics
 (PR metrics pending)

Description

I encountered this in #4013, as you can see from the screenshot there. I would expect only the focused output to be captured in this case.

Contributor guide

Research direction
Investigate the output capture mechanism in grimshot and trace the logic that determines which output to capture. Look for where the 'active' output is selected and ensure that only that output's buffer is captured when the command is issued.
Tech stack
cpp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65