Flameshot still doesn't work under gnome 41.3 #2351
Comments
|
Do you by any chance have unicode characters in your |
|
Yes, i thought you would ask but no i didn't have it. Sorry, i missed to mentioned it in my issue. My path: /home/lxwulf/Pictures I didn't changed anything so this should be the standard path as i know. |
|
I'm not 100% sure if you would need them but just in case, can you check if you have the |
|
Yes, i have it. Sorry for the late answer.
|
|
The best way you can help resolve this issue is to find a way to reproduce it in a clean VM (or clean install). The problem is it works for all the dev's so there really isnt anything we can do to assist. |
|
I agree. I tried it out – it worked fine. But I also did a reinstallation of flameshot in my machine, which didn't help. Are there some configuration files left over which I could delete? |
These are what I got fd --exclude "tmp/" --exclude ".local/" --exclude "Pictures/" --exclude ".mozilla/" --hidden flameshot
.cache/flameshot
.cache/tldr/pages/linux/flameshot.md
.cache/paru/clone/flameshot-git
.config/flameshotrc
.config/flameshot
.config/flameshot/flameshot.iniYou can safely ignore whatever in my |
|
Sadly, this didn't work. Is there any function to output verbose debugging messages from flameshot? |
|
We don't have a good logging or verbosity implemented unfortunately. However, you can try killing all instances of Flameshot, then open two terminals, in one run Anyways, I would also like to suggest you to try the AppImage as well and see if that works. It can points to the direction of missing some sort of dependency. |
|
Im going to close this until more details on how to reproduce it can be added. |
|
@borgmanJeremy okay, why not but it is hardly to debug there are no error message which can help even with @mmahmoudian tip with the two window... I tried to reinstall it several times, deleted configs - nothing helped... I dont know how to deliver more infos; i would but yah... |
|
Update: Also, the flatpak version doesn't work anymore at my system, at least. Would be there any difference when I build the application from source? Greets LxWulf |
I don't think building from source would help, but trying it out would only take about 2 minutes, so nothing to lose there. You can find instructions here: https://flameshot.org/docs/installation/source-code/ Also try the AppImage. This issue is peculiar. We don't know under what circumstances it didn't work on your computer and we cannot replicate it. |
|
Somehow that didn't work either. By chance, I had to reinstall my Fedora system anyway, and still I don't want to have to do it without flameshot. So on which should I install it? What is the best method? Flatpak? DNF? Appimage?… Greets LxWulf PS: Yes, after that, you will never be heard from me on that specific ticket.😉 |
|
I at least can't tell. You can try Flatpak. The thing is Wayland support is not fully there yet. |
|
Ah okay so then I would wait for the fully wayland support. I try the flatpak version I think that one is the "secured" package which should not make that much problem with possible dependency or something else. I do like to report again when I find something. 😊✌️ Greets LxWulf |
Flameshot Version
Flameshot v11.0.0 (-)
Compiled with Qt 5.15.2
linux: 5.15.18-200.fc35.x86_64
fedora: 35
Installation Type
Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)
Operating System type and version
Fedora 35
Description
If I execute
flameshot guiit takes just a screenshot from my full desktop and then a notification pop-up appears which saysflameshot error: unable to capture screen....Steps to reproduce
flameshot guiover package manager, in my casednfScreenshots or screen recordings
System Information
Using Wayland
The text was updated successfully, but these errors were encountered: