-
Notifications
You must be signed in to change notification settings - Fork 1.7k
The error sound plays when I try to take a screenshot #1666
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
Comments
I very much doubt that this is Flameshot issue as it is triggered by your OS and window manager. There is only one scenario that this might happen as far as I can think of, which is you are always killing Flameshot process and every time you want to make the screenshot, you are running the Flameshot again which pushes one notification. Perhaps @borgmanJeremy can weigh in and give us his thoughts on this. Apart from what I mentioned above, I would be thankful if you completely provide all the requested information in the bug report. Some of the things you have failed to mentioned:
|
I use kde and latest git flameshot from aur. |
And I assume you are still on Wayland. Can you also confirm that? Also the latest git as you know is prune to change very frequently. At the moment I'm working on a way to create more accurate versioning system for users how use AUR. P.s: I'm on Manjaro KDE (Xorg) and don't have this issue you are reporting (ie. cannot reproduce this). Maybe other devs can find a way to reproduce this and subsequently address it. |
Yes I am still on wayland. |
I tested this on v0.10.0 and don;t seem to hear the error sound. I do hear the notification sound. This is because by default KDE Notification service plays a sound, this can be disabled if you want. |
Flameshot version
Latest git version.
Describe the bug
When I try to make a screenshot,then I get the error sound,but everything works.
To Reproduce
press your shortcut to take a screenshot.
Expected behavior
That I don't get an error sound
System Information
Arch
The text was updated successfully, but these errors were encountered: