bonsai
December 29, 2025, 8:08am
1
The Issue is known for at least 2 years on other distros:
https://www.reddit.com/r/Fedora/comments/17vdusg/in_f39_flameshot_doesnt_launch_from_a_keyboard/
Problem:
If you try to configure a custom keyboard-shortcut for the Print -Button to execute the /usr/bin/flameshot gui command, nothing happens if the Print-Button is pressed.
I had the same problems and here are my two solutions:
Solution #01 - Recommended
Create a script with only this command in it:
/usr/bin/flameshot gui
Make the script executable
Create a custom keyboard-shortcut that executes the script
Thats how the shortcut looks then for me:
Solution Source: https://www.reddit.com/r/Fedora/comments/17vdusg/comment/kvp6rij/
Solution #02 - NOT Recommended
Switching back to X11 instead Wayland.
I have a suspicion, that many other problems appear, if you switch back to X11 so keep that in mind.
run this command:
sudo nano /etc/gdm3/custom.conf
Change the line
# WaylandEnable=false
into
WaylandEnable=false
Press ctrl+o, then enter, then ctrl+x
Reboot
Forpli
December 29, 2025, 9:17am
2
With this command it works to set up a custom shortcut for flameshot in Wayland and you don´t need a script:
sh -c -- "QT_QPA_PLATFORM=wayland flameshot gui"
2 Likes
I would like to confirm this as the solution, this worked instantly for me. ZOS Pro 18.
Flameshot version: flameshot/now 13.3.0-1 amd64 [installed,local]
I opted to install the .deb from the Github, as the version in the apt repo is a few versions behind.
I use Flameshoot v13.3.0
Your example command was very helpful.
Unfortunately, flameshoot is behaving very strangely.
I only want to take a screenshot of a rectangle using the print key. But the system takes photos of one of my three monitors almost at random. What could be causing this?
Unless you have followed the thread above.
Have you tried launching Flameshot app using right click?
Also, are you on Wayland or X11?
Forpli
January 6, 2026, 9:53am
7
Flameshot seems to be difficult to use with multiple monitors because the monitor to take the screenshot from can not be selected and there is taken the screenshot first and then selected the area.
opened 01:08PM - 02 Aug 25 UTC
closed 09:07PM - 03 Aug 25 UTC
Unconfirmed Bug
### Flameshot Version
### Environment:
• Flameshot Version: 13.0.0
• OS: Windo… ws 11 24H2
• Build: 26100.4770
• Setup: Dual monitors
Primary: 2160p (main display)
Secondary: 1080p signature pad (used for input only)
> ### Priority: Medium (important for all users with multi-monitor setups)
### Installation Type
Using the ready-made package from Github Releases
### Operating System type and version
Windows 11 24H2 Build 26100.4770
### Description
### Issue Summary:
Flameshot v13.0.0 currently **`CAPTURES ALL DISPLAYS AS A SINGLE EXTENDED VIRTUAL SCREEN ON WINDOWS`**, with no way to restrict screenshots to only a specific monitor (e.g., the primary display).
This causes a usability problem in multi-monitor setups, particularly when one of the screens is a small secondary device (like a signature pad), which skews the screenshot dimensions and scale, making region selection difficult and less accurate.
### Steps to reproduce
### Expected Behavior:
Add a feature or setting that allows the user to:
• Choose which monitor to capture from.
• Always default to capturing only the primary display.
• Alternatively, support specifying monitor bounds via CLI (e.g., --region or --screen options that work on Windows).
---------
### Current Behavior:
• Flameshot launches the selection tool across all screens, combining them into one large canvas.
• It reduces the effective resolution when using a high-DPI main monitor with a small second monitor (such as a signature pad).
• There's no built-in workaround to exclude the secondary screen unless it's manually disabled in display settings.
### Screenshots or screen recordings

### Why This Matters:
• Users with multiple monitors (especially pen/tablets, Wacom pads, or other non-standard displays) find Flameshot difficult to use.
• Disabling/enabling monitors repeatedly is not practical.
• Competing tools (like ShareX, Greenshot, Windows Snip & Sketch) handle this better by letting users restrict to one screen.
-----------
### Suggestions:
1. Implement a setting in the UI or CLI to select a target monitor (e.g., --monitor 1).
2. Recognize the primary screen and offer to default to it.
3. Add support for region-based captures on Windows (currently --region CLI flag doesn't work reliably on Windows).
### System Information
### Environment:
• Flameshot Version: 13.0.0
• OS: Windows 11 24H2
• Build: 26100.4770
• Setup: Dual monitors
Primary: 2160p (main display)
Secondary: 1080p signature pad (used for input only)
> ### Priority: Medium (important for all users with multi-monitor setups)
Screenshot tools where you first select the area are probably better suitable for a multi monitor setup. You can use the built-in tool or install gnome-screenshot
sudo apt install gnome-screenshot
which offers a time delay.
Ksnip is also a tool to take screenshots where you can select the area first but you need to switch to Xorg to use it.
Maybe you get some ideas here to find a solution for flameshot with multiple monitors:
opened 06:48PM - 14 Dec 20 UTC
closed 01:48AM - 06 Feb 21 UTC
Wayland
**Flameshot version**
Flameshot v0.8.5
Compiled with Qt 5.14.2
**Describe t… he bug**
When I invoke flameshot, whether via DM or the commandline, it only allows me to screen cap from my primary monitor. If I open the launcher and move to the other monitor, same thing (i.e., the prompting for a region to select goes over to the primary monitor).
**To Reproduce**
Really? Launch flameshot on a multiple monitor workstation, running with Fedora 32/Wayland, and take in the sadness caused by your soon-to-be ex-favorite-tool, flameshot.
**Expected behavior**
I would expect to screen cap across all active monitors/visible workspaces.
**System Information**
Fedora 32, and Wayland. Any other information?
opened 04:43PM - 04 Feb 22 UTC
Bug
Wayland
## Initial report
### Flameshot Version
```
Flameshot v11.0.0 ()
Compile… d with Qt 5.15.2
linux: 5.16.5-arch1-1
arch: unknown
```
### Installation Type
Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)
### Operating System type and version
`Linux 5.16.5-arch1-1 #1 SMP PREEMPT Tue, 01 Feb 2022 21:42:50 +0000 x86_64 GNU/Linux`
### Description
#### Summary
While using multiple screens on Plasma Wayland, Flameshot seems unable to detect all of them properly, and instead takes a screenshot of the left-most screen through KWin, and prompts the user to edit it via the editor.
Additionally, Flameshot seems unable to copy the selected screenshot to the clipboard, but no error is shown and I'm unsure it's related to this bug.
#### Logs
```console
steffo@nitro:~$ flameshot gui
Unable to get current screen, starting to use primary screen. It may be a cause of logical error and working with a wrong screen.
Unable to get current screen, starting to use primary screen. It may be a cause of logical error and working with a wrong screen.
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Unable to get current screen, starting to use primary screen. It may be a cause of logical error and working with a wrong screen.
Unable to get current screen, starting to use primary screen. It may be a cause of logical error and working with a wrong screen.
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
```
### Steps to reproduce
With a Wayland session with multiple monitors, using Plasma Desktop:
1. Run `flameshot gui`
### Screenshots or screen recordings
Will provide a screen recording _as soon as OBS Studio finishes compiling_ 🥲
### System Information
#### `uname`
```console
steffo@nitro:~$ uname -a
Linux nitro 5.16.5-arch1-1 #1 SMP PREEMPT Tue, 01 Feb 2022 21:42:50 +0000 x86_64 GNU/Linux
```
#### Plasma
Plasma Desktop installed from the [`plasma-desktop` 5.23.5-1 Arch Linux package](https://archlinux.org/packages/extra/x86_64/plasma-desktop/).