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

[Feature Request] Do not hardcode "gnome-screenshot" for screenshots

Open
  • Is something wrong?
#360 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
desktop

Research direction

Start at plugins/media-keys/csd-media-keys-manager.c, especially the hardcoded screenshot handling around lines 1853-1869. Then inspect the System Settings > Keyboard > Shortcuts UI described in the issue to determine where each screenshot action's callback command is configured. Done means each screenshot entry exposes a configurable command while preserving the existing shortcut actions.

Written by the indexing model from the issue text.

Description

 * csd version: 5.2.0+una
 * Distribution: Linux Mint 20.3 Una
 * Graphics hardware *and* driver used: Intel integrated
 * 64 bit

Feature Request

Do not force usage of gnome-screenshot for the screenshot media keys. Instead, have a setting which contains the program to be used for each of the screenshot actions.

Not all actions will be applicable to all screenshot programs. For example, window capture is something that gnome-screenshot can do, but Flameshot cannot. In those cases, given that it's the user the one who wants to change this setting, it seems reasonable that choosing a more limited software falls on their responsibility.

In any case, it doesn't look too user friendly to force usage of gnome-screenshot like now (see it hardcoded in source here). Thus this feature request to allow modification.

Steps to reproduce

  • Open "System Settings" on Cinnamon.

  • Under "Hardware", open "Keyboard".

  • Under "Shortcuts", find "Take a screenshot".

  • Become frustrated as changing the screenshot program seems like a reasonable thing to allow, but there is no hint about how to do that in the GUI. Until one finds out that what seemed counterintuitive turns out to be the expected thing right now: that the only method to change hardcoded values from csd is to disable all existing shortcuts and manually recreate them, one by one.

    It is counter-intuitive for several reasons:

    • User doesn't really want to change the actual keys needed to trigger the shortcut. So looking in that part of the settings is already confusing.
    • Still, if one reaches this GUI, it is also confusing that a default action, with a perfectly fine Name and Description, should be removed/disabled in order to manually create an identical one but with a different command.

Expected behaviour

  • ... (same initial steps)
  • Under "Shortcuts", find "Take a screenshot".
  • For each entry, have a GUI field that allows to set a different callback command.
Dominant language
C
Stars
70
Forks
78
No merged PRs in 30d

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

  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/cinnamon-settings-daemon

All issues in linuxmint/cinnamon-settings-daemon

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.