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

When trying to screenshot Taskmanager using Printscreen button, it takes a fullscreen screenshot and doesnt use flameshot selector #3644

Open
oMqngo opened this issue Jun 16, 2024 · 11 comments
Labels
Needs Investigation Reproduced The reported issue was reproduced in a clean VM Windows Windows specific issues

Comments

@oMqngo
Copy link

oMqngo commented Jun 16, 2024

Flameshot Version

Flameshot v12.1.0 (96c2c82)
Compiled with Qt 5.15.2
winnt: 10.0.19045
windows: 10

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)

Operating System type and version

Windows 10

Description

When you try to take a screenshot of the windows taskmanager (doesnt matter if its "always on top" or not) using the Printscreen button, it will take a fullscreen screenshot instead of opening flameshot's selector to specify what to screenshot.

Steps to reproduce

  1. run the windows taskmanager
  2. press the printscreen button to initiate flameshot's screenshot selector
  3. the screenshot selector won't show, instead it will take a fullscreen screenshot (seen in the windows clipboard)

Screenshots or screen recordings

No response

System Information

Windows 10 22H2
1920x1080 Laptop screen

@oMqngo oMqngo added the Unconfirmed Bug The bug is not confirmed by anyone else. label Jun 16, 2024
@mmahmoudian
Copy link
Member

It seems by pressing printscreen you are running SnippingTool (Windows' default screenshot tool) and not Flameshot. Apparently Windows every now and then overwrites your settings and you should change it again.

Follow these steps:

https://flameshot.org/docs/guide/windows-help/#how-to-disable-windows-snipping-tool-when-i-press-printscreen

@mmahmoudian mmahmoudian added question Windows Windows specific issues and removed Unconfirmed Bug The bug is not confirmed by anyone else. labels Jun 17, 2024
@oMqngo
Copy link
Author

oMqngo commented Jun 17, 2024

I disabled this feature but it only stopped taking fullscreen screenshots...

Ive found a small workaround without needing to do anything to the registry/add a shortcut:

  1. open taskmanager
  2. unfocus taskmanager
  3. open flameshot with the printscreen button
  4. take your screenshot without clicking on the taskmanager window (the screenshot tool wont be seen as soon as you go behind the taskmanager window but your mouse is still visible for reference)

@mmahmoudian
Copy link
Member

Are you implying that the Windows TaskManager is behaving differently compared to the rest of the system?

@oMqngo
Copy link
Author

oMqngo commented Jun 17, 2024

I guess you could say that. Its as if the TM has some kind of VIP rights that overrules the settings (unless you click out of it), because even though I have the setting to take screenshots with the print screen button disabled, it will still take a fullscreen screenshot when in TM.

@mmahmoudian
Copy link
Member

I don't have a Windows machine to test this, but I asked a friend to confirm this for me. Apparently you are absolutely right and Windows TaskManager behaves different!!

I will re-open this issue although I highly doubt that this can be solved by Flameshot as it seems to be a Windows thing.

@mmahmoudian mmahmoudian reopened this Jun 17, 2024
@mmahmoudian mmahmoudian added Needs Investigation Reproduced The reported issue was reproduced in a clean VM and removed question labels Jun 17, 2024
@oMqngo
Copy link
Author

oMqngo commented Jun 17, 2024

sounds good! If this isnt a fixable thing don't worry about it, I can always just use my method to work around it 👍

@oMqngo
Copy link
Author

oMqngo commented Jun 17, 2024

sorry for posting on this thread again, but I just found another program that has this same behavior (the game Genshin Impact to be precise).

Pressing the print screen button doesn't open flameshot but takes a fullscreen screenshot instead.

I tried it in 2 other fullscreen games but it seems to work fine there.
Maybe its an idea to give the user the ability to change the hotkey that launches the tool?

@mmahmoudian
Copy link
Member

mmahmoudian commented Jun 19, 2024

Thanks for keeping us updated and trying different approaches to identify the root cause of the issue.

sounds good! If this isnt a fixable thing don't worry about it, I can always just use my method to work around it 👍

If it is a Windows "security" thing, then it would be out of our hands.

Maybe its an idea to give the user the ability to change the hotkey that launches the tool?

That is already discussed in #1341 . Also the #2118 might help in some cases as well.

Pressing the print screen button doesn't open flameshot but takes a fullscreen screenshot instead.

Perhaps they hard-coded something in their game.

@liujustin604
Copy link

perhaps it's related to always on top?

@oMqngo
Copy link
Author

oMqngo commented Sep 29, 2024

perhaps it's related to always on top?

In the case of task manager, yes, but I don't think it's exclusively "always on top" since I have the same issue in Genshin impact (which I play in regular fullscreen). On the contrary, it works normally in trackmania2020 which I also run in regular fullscreen...

@JasonO99
Copy link

FWIW, I am unable to take screenshots of certain applications. Task manager included, but also a lot of control panel or similar. It doesn't work with Windows Snipping, Gyazo or Flameshot. I've been unable to find out what is different with these windows that make it block print screen attempts.

If the application lets you select what you want to screenshot, it ignores any mouse movement over those windows. If you try starting the selection on the app, it won't work. Soon as you move the mouse outside of the window, you have the option.

It's unlikely to be the case that the Windows snipping tool, Gyazo and Flameshot all have the same 'issue' within them and it's therefore likely consistent issue throughout Windows on these; but I am yet to find out why..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Investigation Reproduced The reported issue was reproduced in a clean VM Windows Windows specific issues
Projects
None yet
Development

No branches or pull requests

4 participants