Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flameshot only takes a screenshot of non-primary monitor and a bit of primary monitor #3811

Open
Yannick138 opened this issue Jan 9, 2025 · 3 comments
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@Yannick138
Copy link

Yannick138 commented Jan 9, 2025

Flameshot Version

Flameshot v12.1.0 (-)
Compiled with Qt 5.15.14

Installation Type

pacman

Operating System type and version

Arch Linux (kernel 6.12.8-arch1-1), KDE Plasma 6.2.5

Description

When I run flameshot gui the app will only show a selection on my primary monitor (no matter which screen I run it on) for my second monitor and a portion of my primary monitor, alongside an error message:

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.
flameshot: info: Screenshot aborted.

Steps to reproduce

No response

Screenshots or screen recordings

image
image
What my screenshot selection looks like (this is a photo on my primary monitor) image

System Information

Arch Linux (kernel 6.12.8-arch1-1)
KDE Plasma 6.2.5
Wayland
See the attached screenshot of my monitor setup

@Yannick138 Yannick138 added the Unconfirmed Bug The bug is not confirmed by anyone else. label Jan 9, 2025
@aidendotgg
Copy link

I'm also on KDE wayland and have this exact issue

@YvesCB
Copy link

YvesCB commented Jan 22, 2025

So I had the same issue and this KWin Rule fixes it for me:

[Flameshot workaround (#2364)]
Description=Flameshot workaround (#2364)
above=true
aboverule=2
fullscreenrule=2
position=0,0
positionrule=2
title=flameshot
titlematch=1
types=1
wmclass=flameshot flameshot
wmclasscomplete=true
wmclassmatch=1

I do not remember where I found it and you can use it at your own risk (though I think there's very little risk here).
It has the #2364 in the comment but I don't think it refers to an issue on this repo even though #2364 does reference the same issue.
Hope it works for you.

@matdave
Copy link

matdave commented Jan 22, 2025

@YvesCB That worked for me! Thanks!

After the rule, I had to set Kronkhite to ignore flameshot as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.
Projects
None yet
Development

No branches or pull requests

4 participants