-
Notifications
You must be signed in to change notification settings - Fork 139
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
Can't read QR-codes in wayland #773
Comments
In my testing I've found that yubico authenticator runs under xwayland, and so does chrome. Firefox runs under native wayland. QR code scanning doesnt work from either browser. Firefox is 97.0, Chrome is 98.0.4758.80, running ubuntu 21.10. |
Ah. so it's completely a wayland issue ;-) |
@traffic-light Is the issue solved by that reply? If so, can this be closed? |
I don't think it's really resolved. There is no solution ;-) But I think it's just a specific windowmanager issue... |
The app needs to be updated to use the new wayland screen capture api, something like this. Beyond my ken I'm afraid. |
I just hit this problem and used the following workaround on a site that only had the qr code and did not display the secret key:
|
Yubico Authenticator 6.0 has now been released and uses a new codebase. As such, this issue has been marked with the |
I don't believe this works under Yubico Authenticator 6. |
@schmitmd This should work in version 6 on Wayland, but it requires the |
gnome-screenshot i installed but didnt work still the error is: {"status":"invalid-command","message":"Invalid parameters: Unable to capture screenshot","body":{},"kind":"error"} im using the flatpak version of Yubico Autenticator: Yubico Authenticator com.yubico.yubioath 6.1.0 stable flathub system |
My guess would be that this is caused by the Flatpak sandbox and permissions required to run an external command (gnome-screenshot). The flatpack package of Yubico Authenticator is not maintained by Yubico, so I would suggest opening an issue here instead: https://github.com/flathub/com.yubico.yubioath |
It looks like a hack. You should use screenshot portal: https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.freedesktop.portal.Screenshot |
This still seems to be an issue on ArchLinux / Manjaro Linux using Sway window manager (as opposed to Gnome Shell running on Mutter). Tested with:
Symptoms:The $ ps auxww | grep -i gn
ome-screenshot
trinitr+ 752812 1.6 0.0 471492 49020 pts/2 Sl+ 19:20 0:00 gnome-screenshot -f /tmp/pyscreenshot3tco5mf3/screenshot.png
# gnome-screenshot processes get stuck running in background:
$ pstree -p 752812
gnome-screensho(752812)─┬─{gnome-screensho}(752813)
├─{gnome-screensho}(752814)
├─{gnome-screensho}(752815)
└─{gnome-screensho}(752817)
# Viewing parent processes, we can see that dart:flutter_to + `authenticator-helper` started them
## NOTE: The first 2 processes can be ignored ("foot" is the default terminal app on Manjaro Sway edition. SystemD inherits all processes b/c it's init PID 1.)
## This run was after testing out latest git app via flutter SDK + Dart launch method
## PID 752732 = authenticator-helper (output cuts off due to concatenation of output from pstree)
systemd(1)───foot(751953)───zsh(751954)───dart:flutter_to(752582)───authenticator(752732)───authenticator-h(752777)───gnome-screensho(752812)─┬─{gno+
├─{gno+
├─{gno+
└─{gno+ However, the following errors appear when running /usr/bin/gnome-screenshot -i INT ✘
** Message: 16:54:19.154: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11.
(gnome-screenshot:734865): Gdk-CRITICAL **: 16:54:19.155: gdk_pixbuf_get_from_surface: assertion 'width > 0 && height > 0' failed
(gnome-screenshot:734865): GdkPixbuf-CRITICAL **: 16:54:19.155: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(gnome-screenshot:734865): GdkPixbuf-CRITICAL **: 16:54:19.155: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
(gnome-screenshot:734865): GdkPixbuf-CRITICAL **: 16:54:19.155: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(gnome-screenshot:734865): GdkPixbuf-CRITICAL **: 16:54:19.155: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(gnome-screenshot:734865): Gtk-CRITICAL **: 16:54:19.155: gtk_window_resize: assertion 'width > 0' failed
** (gnome-screenshot:734865): CRITICAL **: 16:54:19.155: Unable to capture a screenshot of any window In any case, this seems to be a bug in EDIT: I've tested out PR #1053, and unfortunately it doesn't solve this issue. The problem lies in the |
Looking into this further, it appears that this was reported upstream: GNOME/gnome-screenshot#201 However, the GNOME developer closed it as effectively So that leaves the possibility of someone doing the work to detangle EDIT: Quoting the latest README commit log from
So it seems this could be a good option on any generic Wayland + The final option which looks promising is using |
It seems to me that this issue shouldn't be marked closed, given that scanning QR codes still doesn't work on any Wayland system that isn't GNOME? |
The application runs in wayland but firefox and chrome runs in Xwayland (X11 server of wayland)
I don't think there is an easy (if there is) fix for it. But I wanted to let you guys know.
(didn't find a dirty fix to force run it in Xwayland...)
JonnieCache did look further into it. His post:
The text was updated successfully, but these errors were encountered: