-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Cannot take a screenshot Fedora 35 (gnome 41.2) - wayland (non Latin characters in XDG path) #2211
Comments
This is really confusing to me because it works fine for me in a clean VM. Have you tried rebooting after installing all the portals? |
Yes, ofcourse. I restarted the system multiple times. I upgraded the system from fedora 34. The flameshot doesn't work after the distro upgrade. :/ Is it possible to debug the problem (somehow)? |
Then look for an error in the diagram and report what the error is. I also just noticed you are using the flatpak and not the native build. I thought you were using the native build so thats what I tried in the VM. I will try the flatpak later. Perhaps use Flatseal and make sure Flameshot has DBus permissions? |
In the gif you ran it with flatpak which is why I am confused. You may need to file this as a bug with fedora35 since it works fine on a clean install |
Apologize, the gif / or video file is from the previous comment (I refer to) (Originally posted by @yajo in #1910 ) - just for the describtion of the same behaviour. But in my machine is installed by Have the flameshot app some cache or config (thats its not removed by |
FWIW I use Fedora Silverblue 35, not just Fedora 35. I guess it shouldn't matter, but just in case... |
As a Fedora maintainer, I can't do anything with this in downstream. It works fine on my VM with Gnome after installing the You should ask GNOME upstream, I think. |
I filed the bug here: https://bugzilla.redhat.com/show_bug.cgi?id=2036411 and answer is to resolve the problem with Flameshot and Gnome upstream :/ Where can I ask Gnome upstream? |
Sorry, but I will close it as this is not a packaging issue and can't be fixed in downstream. It should be reported directly to GNOME/mutter.
|
Ubuntu has the same problem: #2199. |
No that user simply didn't have the portals installed. I have no idea what's going on here. It works fine in a vm so until someone can explain to to make it occur there really is nothing I can do. |
I've also try to
|
I opened the issue also here: https://gitlab.gnome.org/GNOME/mutter/-/issues/2072 |
Aaaaand they closed it for you without even reading the basis of your report. Thanks for taking the time to do this and report it upstream. Let's stay hopeful that they read your comment which you posted after they closed the ticket. |
Ok, (probably due to my laziness) to use the other's video to preview similar behaviour. I didn't notice that output on the preview video is little bit different than in my case. Next time, I'll be better with filling the bug. My video with the problem is here: |
Could be a trouble here? https://gitlab.gnome.org/GNOME/mutter/-/issues/2072#note_1344961 Good point is that I have the screenshot files in path |
@vanheck Can you try another directory with only Latin characters? |
I'm not sure if I'm able to change this behaviour - the screenshot is saved into folder |
Yes, confirm, Flameshot works well if I change the default path for Pictures with Latin characters only ( |
Thanks for persisting and finding the root cause, that's something we can can fix. |
@borgmanJeremy you’re welcome. Please, let me know when will be the fix released. |
Another behaviour of Flameshot is: After |
Can confirm its not a Gnome issue. Only today i switched from Arch Gnome to Fedora Gnome, and just like you I'm getting same issues on my fedora machine. |
Weird, I did the change from #2211 (comment) and log out, log in under Wayland. It works also! I can also see #2211 (comment), before doing that. What makes all this even more weird is that I configured a different save path that happens to not have non-ascii characters: But flameshot still writes those temporary files into XDG_PICTURES_DIR. My guess is that temporary files should go into XDG_CACHE_DIR (besides supporting non-English use cases 😋 for XDG_PICTURES_DIR). |
@gormih |
@vanheck |
@yajo But there is a question: xdg capture the screen before I allow that (by clickcing on the Share button in gnome dialog) - is it the right behaviour? guess not... but it is another issue. |
@gormih please check #2211 (comment) and #2211 (comment) If you have in |
@vanheck may be rename a title of issue with this fact? |
Just to clarify my comments from the gnome issue: the problem simply is that https://github.com/flameshot-org/flameshot/blob/master/src/utils/screengrabber.cpp#L53 does The screenshot being stored to the XDG pictures folder is something that |
Thanks for summing it up nicely. We are going to ensure this is fixed before version 11 is released (currently in beta). |
@borgmanJeremy |
Great! I'll merge it. Thanks again for the deep dive. I often have a hard time finding these unicode bugs on my own. |
@borgmanJeremy Do you think I should backport this PR to 0.10.2 for Fedora or just wait for the 0.11 release? |
I'm going to wait for v11. There's a couple of minor issues left but should be done by the weekend. |
Flameshot Version
flameshot.x86_64 0.10.2-3.fc35
Installation Type
Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)
Operating System type and version
Fedora 35
Description
Hi, I have the same problem as @yajo here: #1910 (comment) - the issue is closed, but the problem remains.
Captura.del.escritorio.de.27-12-21.09.25.59.mp4
Originally posted by @yajo in #1910 (comment)
I use:
Fedora 35 with Gnome 41.2 (wayland),
xdg-desktop-portal
andxdg-desktop-portal-gnome
are also installed.Steps to reproduce
flameshot gui
and get error pop-up "Unable to capture screenshot"
Screenshots or screen recordings
No response
System Information
Wayland,
xdg-desktop-portal
andxdg-desktop-portal-gnome
are also installed.The text was updated successfully, but these errors were encountered: