flameshot
flameshot copied to clipboard
Keyboard not Working
Flameshot Version
Flameshot v12.1.0 () Compiled with Qt 5.15.3
Installation Type
Using the ready-made package from Github Releases
Operating System type and version
Ubuntu 22.04.2 LTS (Jammy Jellyfish) OS w/ Linux kernel 5.19.0-46-generic w/ GNOME 42.9 DE w/ Wayland window server
Description
About half the time I use flameshot
, the keyboard isn't captured by the application & so I can only control it w/ the mouse, which severely limits the intended functionality. Frustratingly, this was raised by issues https://github.com/flameshot-org/flameshot/issues/1897 & https://github.com/flameshot-org/flameshot/issues/2031 & eventually closed as 'resolved', but I can guarantee it persists for me across multiple machines. What's going on?
This happens w/ both version 11.0.0-2 500 (the version supplied via Canonical's jammy universe repos by default & I installed w/ apt
) as well as the latest version 12.1.0-1 100 (via the .deb release on this very GitHub repo). I haven't tried the Flatpak or Snap versions, but I'd rather not use those if I can help it.
Steps to reproduce
-
Take Screenshot w/
flameshot gui
- Select Share in pop-up dialog
- Find oneself unable to use any keyboard shortcuts, move the screenshot selection w/ any arrow keys, etc.
Screenshots or screen recordings
No response
System Information
- Ubuntu 22.04.2 LTS (Jammy Jellyfish)
- 1920 × 1080p (16:9) @ 60.01 Hz in landscape orientation, 100% scale
- GNOME 42.9 w/ Wayland window server
Thanks for opening the issue and filling the bug report form.
For start, it seems the info you provided is wrong. Flameshot 12.1.0 did not exist at the release date of Ubuntu 22.04 and it does not exist in their repo. So I would be thankfuk if you can edit your original post and clarify exacly how you have instakled Flameshot 12.1.0
What's going on?
Well, the only reasons I can think of that Flameshot is not responding to the keyboard shortcuts is:
- Flameshot have lost focus (in this case it should give you a message)
- Your window manager is capturing the keybinding and not sending it to Flameshot.
Does this happens for all the shortcuts or only few of them?
Would you please provide your config file (~/.config/flameshot/flameshot.ini
)
Thank you for responding @mmahmoudian!
For start, it seems the info you provided is wrong. Flameshot 12.1.0 did not exist at the release date of Ubuntu 22.04 and it does not exist in their repo. So I would be thankfuk if you can edit your original post and clarify exacly how you have instakled Flameshot 12.1.0
Absolutely not, the info I provided is correct, if you review it, in parentheses I put (via the .deb release on this very GitHub repo), the .deb which I acquired after being suggested to update to it by flameshot
11.0.0 itself. My point is the issue occurs w/ both 11.0.0 & 12.1.0, but I am currently using the latter.
Does this happens for all the shortcuts or only few of them?
All of them.
Would you please provide your config file (
~/.config/flameshot/flameshot.ini
)
Doesn't look like I can attach a .ini, but here's a .zip of it.
I updated Installation Type w/ the category that reflects my current installation @mmahmoudian, but again, this happens w/ both 11.0.0 & 12.1.0 & I only got the .deb to update to 12.1.0 to try to fix it (it didn't fix it). So let's please remove the 'invalid' label & proceed w/ troubleshooting. If there's anything else you need from me, logs etc., I'm happy to supply!
Would you please provide your config file (
~/.config/flameshot/flameshot.ini
)Doesn't look like I can attach a .ini, but here's a .zip of it.
Hello @mmahmoudian, was the config file you asked for of any use? This is still an ongoing issue for me, about half the time I use flameshot
I can't use the keyboard at all.
Any update on this?
No. I personally cannot reproduce this. So I'm waiting to see if anyone else can reproduce it.
Seems like a bad criteria, I have a lot of packages & extensions installed, it's possible an external variable is causing flameshot
to not work correctly, but does that really mean my issue isn't worth investigating? If there are any logs I could/should provide I'm more than happy to if given a direction.
Seems like a bad criteria, I have a lot of packages & extensions installed
Good or bad, it is the only rational thing. Otherwise how can it be investigated if we cannot have an environment to investigate it in?!
but does that really mean my issue isn't worth investigating?
Did I ever say such thing? Wouldn't it be easier for me to just label this with invalid and not reproduced, and then close the issue? Instead what did I do? I asked you to fill the gaps, I kept the issue open (despite not being able to reproduce it myself), and I stay responsive.
Now that I was typing this it occurred to me:
How many languages do you have on your computer? I mean how many keyboard layouts? Is it possible that those times that Flameshot does not work, your keyboard layout is in another language?
Thank you for your response.
How many languages do you have on your computer? I mean how many keyboard layouts? Is it possible that those times that Flameshot does not work, your keyboard layout is in another language?
I have 3, but it definitely happens to me on my default en
layout, which is English (Australian) specifically.
This still happens.
I use Ubuntu 22.04.4 w/ Linux kernel LTS 6.5.0-26-generic And i'm having the same error as you. But only some of my keys don't work like: 1, 2, 3 and hotkeys
This is still happening btw, & I am going to be really miffed if I upgrade to 24.04 LTS later this month & it's still happening even then.
I'm on Debian 12 6.1.0-18-amd64 using Wayland.
Keyboard not working for me when i run with command:
QT_QPA_PLATFORM=xcb flameshot gui
Working fine with command:
flameshot gui
But i need QT_QPA_PLATFORM=xcb for my multiple-screen setup. So yea, still a problem.
I'm on Debian 12 6.1.0-18-amd64 using Wayland.
Keyboard not working for me when i run with command:
QT_QPA_PLATFORM=xcb flameshot gui
Working fine with command:
flameshot gui
But i need QT_QPA_PLATFORM=xcb for my multiple-screen setup. So yea, still a problem.
I bet my money that the issue is Gnome and not Debian. Gnome has changed things again. 🤦♂️
I'm on Debian 12 6.1.0-18-amd64 using Wayland.
Keyboard not working for me when i run with command:
QT_QPA_PLATFORM=xcb flameshot gui
Working fine with command:
flameshot gui
But i need QT_QPA_PLATFORM=xcb for my multiple-screen setup. So yea, still a problem.
Same problem for me using the flatpak package with arch linux and Plasma 6
Adding the env variable QT_QPA_PLATFORM=xcb
renders all inputs from keyboard impossible