linuxmint / linuxmint/cinnamon

screenshot-key regression in Cinnamon 6.4.14

Open
#13,938 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

BUG
Dominant language
JavaScript
Stars
5.6k
Forks
915
Avg merge
5d 22h
Merged PRs (30d)
3

Description

Distribution

Linux Mint 22.3 Cinnamon, 64-bit, X11 session

Package version

6.4.14

Graphics hardware in use

AMD Radeon 780M integrated graphics (AMD Phoenix3, amdgpu driver, X11)

Frequency

Always

Bug description

I am reporting a screenshot-key regression in Cinnamon 6.4.14. Before the update, I could use Shift+Print to launch the familiar GNOME Screenshot interface and select an area. After updating, Cinnamon began intercepting the Print Screen key and launching its own capture function instead.

System information:

Computer: GEEKOM A8

Desktop: Linux Mint Cinnamon

Cinnamon version: 6.4.14

Session type: X11

Screenshot application: gnome-screenshot

My update history shows that Cinnamon was upgraded from version 6.4.8 to 6.4.14 during the same update operation that installed a new kernel. I tested the previous kernel, but the problem remained, so this does not appear to be a kernel regression.

GNOME Screenshot itself works correctly when started from a terminal:

/usr/bin/gnome-screenshot --interactive

The problem occurs when attempting to assign that command to Shift+Print. Cinnamon continues to intercept the Print Screen key before the custom shortcut can run.

I performed the following troubleshooting:

Disabled Cinnamon’s built-in screenshot bindings, including screenshot, screenshot-clip, area-screenshot, and related window bindings.

Created a valid Cinnamon custom shortcut using custom3 with:

/usr/bin/gnome-screenshot --interactive

Confirmed that the custom shortcut was stored correctly in dconf.

Logged out and back in after changing the bindings.

Disabled and tested xbindkeys; it was not responsible.

Confirmed that only csd-media-keys was running as the media-key daemon.

Attached strace to both Cinnamon and csd-media-keys; no external screenshot executable was launched when Print was pressed.

Queried the owner of the screenshot D-Bus service with:

busctl --user status org.gnome.Shell.Screenshot

The result identified Cinnamon itself:

Comm=cinnamon
Exe=/usr/bin/cinnamon
CommandLine=cinnamon --replace

Even with all configurable Cinnamon screenshot bindings cleared, pressing Print still activates Cinnamon’s internal screen capture. Cinnamon’s shortcut editor also cannot reliably capture the Print key because the internal screenshot handler receives it first.

This behavior prevents users from assigning Print or Shift+Print to their preferred screenshot application. It also makes the shortcut settings misleading because the displayed configuration says the bindings are disabled while Cinnamon continues to act on them.

Please investigate Cinnamon 6.4.14’s internal handling of the Print Screen key. The desktop should respect disabled screenshot bindings and allow custom shortcuts to receive Print-key combinations. I would appreciate either a fix or clear instructions for disabling Cinnamon’s internal screenshot handler.

Steps to reproduce

Please see bug description.

Expected behavior

Please see bug description above.

Additional information

No response

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.

Research direction

Start by reproducing the issue on Cinnamon 6.4.14 with the reported Print and Shift+Print bindings, then inspect Cinnamon's internal screenshot-key handling. Compare the configured bindings with the behavior observed through dconf and the org.gnome.Shell.Screenshot D-Bus service. Done means disabled screenshot bindings no longer intercept the keys and custom shortcuts can receive them.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.