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 aborts screenshots when switching tools from text #2429

Closed
karlyeurl opened this issue Feb 15, 2022 · 9 comments
Closed

flameshot aborts screenshots when switching tools from text #2429

karlyeurl opened this issue Feb 15, 2022 · 9 comments
Labels
Bug It's a bug Duplicate This issue/PR is duplicated and the duplicated issue/PR is commented.

Comments

@karlyeurl
Copy link

Flameshot Version

$ flameshot --version
Flameshot v11.0.0 (-)
Compiled with Qt 5.15.2

Installation Type

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

Operating System type and version

Linux

Description

When running flameshot gui and selecting an area, if we are writing text with the text tool, switching tools causes flameshot to abort and a notification to pop: "Flameshot Info Screenshot Aborted".

This does not happen if we deselect the text tool first.

I believe this is a bug, as it was not happening in the prior version of flameshot.

Steps to reproduce

  1. run flameshot gui
  2. select an area
  3. select the text tool
  4. click in the area and start writing text
  5. without unselecting the text tool, pick another tool (I used the "circle" paint tool, but most other tools trigger this too)
  6. flameshot gui exits with return code 0, a system notification is sent with "Flameshot Info Screenshot Aborted".

Screenshots or screen recordings

No response

System Information

  1. linux 5.16.9-arch1-1
  2. two screens
  3. awesome-wm with xorg
@karlyeurl karlyeurl added the Unconfirmed Bug The bug is not confirmed by anyone else. label Feb 15, 2022
@mmahmoudian
Copy link
Member

mmahmoudian commented Feb 15, 2022

Isn't this duplicate of all the following?

Considering that they have been resolved with #2369, you can get the fix either by installing from AUR or compiling from source. If you are willing to wait until the next release, will be included in that one.

@karlyeurl
Copy link
Author

Oh for the love of God, I'm an idiot. I searched in open issues.

Sorry! Closing.

@dogunbound
Copy link

dogunbound commented May 17, 2022

Has this bug been fixed? I'm still having it.

[dogunbound@DogBigRig ~]$ flameshot --version
Flameshot v11.0.0 (-)
Compiled with Qt 5.15.3

@mmahmoudian
Copy link
Member

mmahmoudian commented May 17, 2022

@dogunbound read my last comment (the one before this one). All the info you need is there.

@dogunbound
Copy link

@mmahmoudian oh lol. Thanks.

@mo
Copy link

mo commented Jun 8, 2022

I just upgraded to ubuntu 22.04 and now I have this bug.

@mmahmoudian
Copy link
Member

@mo read the last line of my comment in this thread that is posted 22 days ago 😉 :

image

@mo
Copy link

mo commented Jun 9, 2022

Yes I saw it. I think it makes sense to fix it in Ubuntu 22.04 as well, many people are upgrading to it right now and on aug 4th they will turn on automatic upgrade of all LTS users to this new Ubuntu version. I installed the latest dev version now, so it works well for me.

@mmahmoudian
Copy link
Member

mmahmoudian commented Jun 9, 2022

@mo We do not maintain the Ubuntu software repos. We only maintain the packages on our Github release page, Snap, Flathub, and the flameshot-git on Arch User Repository. Also, this will be included in the next release. If someone doesn't want to wait, they can install from our nightly builds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug It's a bug Duplicate This issue/PR is duplicated and the duplicated issue/PR is commented.
Projects
None yet
Development

No branches or pull requests

4 participants