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

prt scr keybinding does not work in Flameshot on Windows 11 24H2 #3783

Open
TESTER-sec opened this issue Nov 17, 2024 · 3 comments
Open

prt scr keybinding does not work in Flameshot on Windows 11 24H2 #3783

TESTER-sec opened this issue Nov 17, 2024 · 3 comments
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@TESTER-sec
Copy link

Flameshot Version

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

Installation Type

Using the ready-made package from Github Releases

Operating System type and version

Windows 11 24H2

Description

prt scr does not work for Flameshot on Windows 11 24H2

Steps to reproduce

  1. Install Flameshot
  2. Run Flameshot
  3. Attempt to launch Flameshot screenshot using prt scr key
  4. Flameshot does nothing

Screenshots or screen recordings

No response

System Information

Edition Windows 11 Pro
Version 24H2
Installed on ‎9/‎6/‎2024
OS build 26100.2314
Experience Windows Feature Experience Pack 1000.26100.32.0

@TESTER-sec TESTER-sec added the Unconfirmed Bug The bug is not confirmed by anyone else. label Nov 17, 2024
@FelixJochems
Copy link

I think windows now automatically forces the snipping tool.
See: https://flameshot.org/docs/guide/windows-help/ to change that

@TESTER-sec
Copy link
Author

TESTER-sec commented Nov 17, 2024

I think windows now automatically forces the snipping tool. See: https://flameshot.org/docs/guide/windows-help/ to change that

It does associate prt scr button with snippingtool, but that is not the issue.

ShareX and Greenshot (abandonware from 2017) disassociates snippingtool from the prt scr key on behalf of the user. The developers do not direct Windows users "Hey, you have to figure this out and do all this stuff to make it work for you as a Windows user."

What I am seeing in this project is this "If you install Flameshot on Windows then you as the user need to jump through these hoops because us Flameshot developers are not going to do it for you on Windows."

So tell me "Flameshot is a Linux tool\utility and not really meant for Windows without saying Flameshot is a Linux tool\utility and not really meant for Windows."

I think Flameshot is superior to other screenshot software, but its usability is fatally flawed on Windows until the project developers drop the Plugin way of doing things (which has been discussed for years but no action taken), and figure out how to deliver simple usability for Windows users such as how to trigger Flameshot screenshot via key combo and timestamps.

Other projects can do it. So it is not as if it is not possible. What I am talking about is a Flameshot project developer issue. I go back to one thing - the project developers are focused on Linux and Windows is an afterthought.

@noidesserts
Copy link

Also got this
Reinstalled once. Redownloaded the installer. Tried again. Something is wrong. (Also 24h2 btw)

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

3 participants