Make Flameshot Feel Native on Your Linux Desktop

Flameshot clicked for me the first time I needed to explain a layout bug without writing a paragraph around it. Draw a box, add one arrow, blur the customer name, copy—and the screenshot becomes useful evidence rather than a mystery attachment. The awkward part on Linux is rarely drawing; it is making the desktop shortcut and capture permissions behave.

Choose one installation source

Distribution packages integrate naturally with system updates, though their version may trail upstream. Prefer one packaging method at a time; parallel APT, Flatpak, and Snap installations can leave you launching a different binary than the one you configured.

$ sudo apt update
sudo apt install flameshot

What the APT transaction changes

• apt update refreshes package metadata; it does not upgrade every installed package.

• apt install flameshot installs Flameshot and any required dependencies from configured repositories.

• sudo grants package-management privileges, so inspect the proposed additions and removals before accepting.

• This workspace exposes Ubuntu 24.04’s Flameshot 12.1.0 candidate, but Flameshot itself is not installed here.

$ sudo dnf install flameshot
sudo pacman -S flameshot

Why the commands are alternatives

• dnf install resolves the Fedora package and dependencies from enabled repositories.

• pacman -S synchronizes the named Arch package into the local system.

• Both modify system packages and require administrative authorization.

• Do not paste both commands: a normal installation has one distribution package manager.

Confirm which Flameshot you will launch

$ command -v flameshot
flameshot --version
flameshot --help

What these checks reveal

• command -v reports the executable selected by the current shell search path.

• --version makes bug reports and Wayland troubleshooting reproducible.

• --help reflects the installed build, which is more reliable than assuming every online option exists locally.

• A missing command means installation or PATH selection failed; it is not a screenshot-permission problem yet.

Take and annotate the first capture

$ flameshot gui

A capture workflow that stays quick

• Drag over the region, then use arrows, rectangles, marker, text, pixelation, or the color picker as needed.

• Ctrl+C copies the selected capture, while Ctrl+S saves it as a file in the default bindings.

• Ctrl+Z undoes an annotation; Escape leaves capture mode.

• Pixelation is useful for casual redaction, but inspect the final image closely before sharing sensitive data.

Bind Print Screen to Flameshot on GNOME

1. Open Settings and find Keyboard or Keyboard Shortcuts; labels differ by GNOME version.

1. Find the existing screenshot action and remove or replace its Print Screen binding.

1. Create a custom shortcut named Flameshot with command flameshot gui.

1. Press Print Screen when asked for the key combination and save the shortcut.

1. Test it while a normal desktop application has focus.

If Flameshot came from Flatpak, the shortcut command is commonly flatpak run org.flameshot.Flameshot gui. Use the launcher that matches the installation you chose. KDE users should remove any conflicting Spectacle binding and create the equivalent custom command in System Settings.

Useful CLI captures for repeatable work

$ mkdir -p "$HOME/Pictures/Screenshots"
flameshot gui --path "$HOME/Pictures/Screenshots"
flameshot gui --delay 2000
flameshot full --path "$HOME/Pictures/Screenshots" --delay 5000

What the options control

• mkdir -p creates the directory and succeeds harmlessly if it already exists.

• gui --path opens region selection and supplies an existing directory as the save destination.

• --delay is measured in milliseconds: 2000 is two seconds and 5000 is five.

• full captures the full desktop across monitors; review all visible content before saving or sharing it.

When Wayland says it cannot capture the screen

Wayland deliberately prevents arbitrary applications from reading the screen. Flameshot normally depends on the desktop’s xdg-desktop-portal screenshot flow, which can show a permission dialog. A command that works in a terminal but fails from a shortcut often points to a different environment, packaging sandbox, or portal interaction—not a need to run Flameshot as root.

$ printf '%s
' "$XDG_SESSION_TYPE"
flameshot config --check
QT_QPA_PLATFORM=wayland flameshot gui

How to interpret the test

• XDG_SESSION_TYPE commonly reports wayland or x11; an empty value means the launch context lacks that session variable.

• config --check inspects Flameshot configuration for errors without taking a screenshot.

• QT_QPA_PLATFORM=wayland affects only that invocation and helps distinguish native Wayland from XWayland behavior.

• If the test succeeds, use the same environment in the shortcut and consult Flameshot’s Wayland guidance for the installed package and desktop.

Fast diagnosis by symptom

• Print Screen opens another tool: remove the GNOME Screenshot or Spectacle binding, then bind flameshot gui.

• Shortcut does nothing: use an absolute executable path or the correct Flatpak command and verify it works in a terminal.

• Unable to capture on Wayland: check portal packages and permission prompts, then test the native Wayland invocation above.

• No tray icon: start Flameshot at login and, on GNOME, confirm tray/AppIndicator support; the shortcut can still launch GUI mode directly.

• Clipboard paste fails: verify a clipboard manager or target application is not discarding image MIME data; save a PNG to separate capture from clipboard behavior.

• Wrong monitor or scale: record desktop, display server, monitor scale, and Flameshot version before checking upstream issues.

Related desktop workflows

• Repair Ubuntu APT and dpkg dependency errors if package installation fails.

• Prevent screenshots in an Android application when the problem is app privacy rather than desktop capture.

• Install OBS Studio on Ubuntu when you need screen recording instead of annotated still images.