Cannot take screenshot on gnome 41 + wayland #1910
Comments
tim-hm
changed the title
|
same story on fedora 35, gnome 41 and wayland |
|
Ok, since we have two people with the same issue on two different distro, let's do some testing. I would appreciate if both of you file the steps and report back the output here:
pkill flameshot
flameshot
flameshot guiAccording to your posts nothing should happen, but you will see some output in the first terminal. Please provide us that output. Additionally, @pashtet422 please provide the following:
|
mmahmoudian
added
the
Waiting For Info
|
Was about to add a "+1" on this, but executed your procedure above, and it worked. So, it's my understanding that, on order to Using latest stable Snap version, BTW. |
|
@ivocavalcante all |
|
Does it have anything to do with the dbus changes mentioned in this kooha issue? |
|
1st terminal: pkill flameshot
flameshot
QSettings::value: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed2nd terminal: Flameshot v0.10.1 |
|
@pashtet422 Can you confirm that you are using Gnome and Wayland? |
|
Yes, i'm using Fedora 35 with gnome 41.0 and wayland. Flameshot has been crashed after update from Fedora 34 to 35. |
|
Upd: i've tried to recompile from source again and a problem still exists |
|
@mmahmoudian I reproduced this issue today on Fedora35, but it works on Fedora34. Given the other report about Gnome41 on arch, I think we should conclude Gnome41/ mutter made a change to the screenshot API. Edit: I cant reproduce this on Arch with gnome 41.... From fedora: I can reproduce this independent of flameshot: |
|
Okay, I posted the details on the upstream package: https://bugzilla.redhat.com/show_bug.cgi?id=2009460 |
mmahmoudian
added
Bug
|
Same issue as OttoAllmendinger/gnome-shell-screenshot#158 Current workaround: https://extensions.gnome.org/extension/4517/unsafe-mode/ |
|
@saboya Thanks, I added this to the README. @mmahmoudian What are your thoughts on this. We have essentially two options.
|
Hello, I'm the author of said extension. Basically, that extension works by enabling unsafe_mode from Mutter global context (which you can always do from LG or from your own extension, just see the source code itself). The problem is this mode is (surprise!) unsafe for end users, since this enable arbitrary code executions (just like ol' GNOME 3 days) by abusing Since security is a big issue, and nobody wants some rogue apps, scripts or extensions running malicious codes on their machine because an extension just open up the possibility to, I've since inactivated the extension, but you can still install the extension from the source code. |
|
Thank you @ramottamado and @saboya for your input. @borgmanJeremy This is indeed a dilemma which MacOS, iOS and Android have solved ages ago by asking user for certain permissions once and white listing that software for that permission. Tbh, to me it seems we are facing a monopoly that only the softwares Gnome wants can work without interruption and annoyance and all other softwares should face all sorts of challenge. Their excuse for changing DBus seems legit and I mostly agree, but due to bad implementation or their shortsightedness they immediately created a monopoly for their own applications which are hardcoded in the allow list (as Florian Müllner mentioned in the Gnome's gitlab repo. Regardless, considering that the extension is inactivated, we have no choice but to go with the flow. I suggest that we implement a part that detects this situation, then we open a window for the user with enough text and link so that they know the faulty party is not Flameshot. I really don't know if we should point the finger to Gnome or Wayland, but nonetheless imho it is crucial that the user knows why they are getting spammed with popups and to know it is not bad design by us, but rather bad design by merge-request 1970 of gnome shell. |
|
Hi, Thanks for this tool it help a lot. I really missed it after I've upgraded from Fedora 34 to 35. I still can't use it even with the version ❯ flameshot --version
Flameshot v0.10.2
Compiled with Qt 5.15.2OS: OS: Fedora release 35 (Thirty Five) x86_64
Host: NBLB-WAX9N M1230
Kernel: 5.15.10-200.fc35.x86_64
Resolution: 1920x1080
DE: GNOME 41.2
WM: Mutter
WM Theme: Adwaita
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i5-10210U (8) @ 4.200GHz
GPU: Intel CometLake-U GT2 [UHD Graphics]
Memory: 11916MiB / 15732MiB |
|
Hi @mmahmoudian, thanks for the working on this tool. It's a great tool. I just installed the pre-release, but the same error still occurred. I can help test this release until the issue is resolved, just ping me! |
|
@yaayes thanks for treating the new pre-release. Let's then get some more information from you to better understand the situation. Please tell us the following:
|
|
I installed https://github.com/flameshot-org/flameshot/releases/download/v11.0.rc1/org.flameshot.Flameshot-11.0.rc1.x86_64.flatpak directly. I ran your commands. In 1st term: > flatpak run org.flameshot.Flameshot
Qt: Session management error: None of the authentication protocols specified are supported2nd terminal: > flatpak run org.flameshot.Flameshot gui
Qt: Session management error: None of the authentication protocols specified are supported
flameshot: error: Unable to capture screen
flameshot: error: Unable to capture screen
flameshot: info: Screenshot aborted.What happens under Wayland: Captura.del.escritorio.de.27-12-21.09.25.59.mp4 |
|
Do you have xdg-desktop-portal installed? |
|
El lun, 27 de dic de 2021 a las 04:58:19 AM, borgmanJeremy
***@***.***> escribió:
Do you have xdg-desktop-portal installed?
Yes:
/usr/libexec/xdg-desktop-portal --version
xdg-desktop-portal 1.10.1
|
|
And what about
|
|
Also there: |
|
Not affected. |
You lost me. What is not affected? Please add a sentence or two to clarify your point. |
|
|
I've tried to run a few other screenshot utilities, like: Shutter, maim and xfce4-screenshooter, and can confirm this is a Gnome issue and not flameshot issue. |
|
TL;DR, this is a complex topic regarding modern Gnome-shell, no one did a good job so far at reducing the complexity for the audience. Can you please dear Flameshot developers try to sum up what is the issue with flameshot on gnome 41 wayland? I read this thread and it is still not quite clear, even if @mmahmoudian post helps: P.S. reading a bit more in this issue at Gnome-shell and this subsequent one at flatpak/xdg-desktop-portal, cannot you store in a gnome-keyring session the DBus authorization from a public gnome-shell API? |
|
@Maxzor I think I have explained it well enough: And if you want to read some the Gnome people's response on our repo: |
|
A workaround for the permission prompt is by forking xdg-desktop-portal-gnome and simply removing the dialog. Here's a fork which does this. Disclaimer: I maintain the above fork, and this solution likely won't work with sandboxing software such as Flatpak. |
|
@TestingPlant |
|
Please read this: https://flameshot.org/docs/installation/installation-linux/ |
If you're asking about my fork, I don't support Ubuntu because it'd take a lot of time to backport and test my patch on all of the GNOME versions Ubuntu supports. If you have any more questions, make sure to ask on this issue tracker, not here. |
and others
Flameshot version
Flameshot v0.10.1 (d142888)
Compiled with Qt 5.15.2
Describe the bug
When running
flameshot guion gnome 41 + wayland nothing happens.Output from running
dbus-monitor --session sender=org.flameshot.Flameshotis hereTo Reproduce
Install gnome 41 + wayland + Arch + flameshot, and then run
flameshot guiin terminalExpected behavior
The on screen gui should launch to take a screenshot
System Information
The text was updated successfully, but these errors were encountered: