You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XDG_CURRENT_DESKTOP=Wayfire should be set on PiOS in order for programs relying on xdg-desktop-portal-wlr to work properly.
Currently, this var is unset.
This is discussed on the wayfire repo here: WayfireWM/wayfire#1995
Similar problem encountered here, with a similar solution: emersion/xdg-desktop-portal-wlr#193
I have confirmed this affects RustDesk (an open source teamviewer/anydesk/realvnc alternative)
It likely affects all other applications that make use of xdg-desktop-portal-wlr, including other remote desktop software and screensharing on other web browsers.
To keep all info on one place, this has already been reported on the bookworm feedback forum here with no response so far, and was mentioned on this pi-apps issue
Tagging @theofficialgman
The text was updated successfully, but these errors were encountered:
Asking the Pi devs: at what place in the boot sequence would be the most acceptable place to set an appropriate value of XDG_CURRENT_DESKTOP, ensuring that it detects X11, Wayland, and other compositors reliably?
XDG_CURRENT_DESKTOP=Wayfire
should be set on PiOS in order for programs relying on xdg-desktop-portal-wlr to work properly.Currently, this var is unset.
This is discussed on the wayfire repo here: WayfireWM/wayfire#1995
Similar problem encountered here, with a similar solution: emersion/xdg-desktop-portal-wlr#193
I have confirmed this affects RustDesk (an open source teamviewer/anydesk/realvnc alternative)
It likely affects all other applications that make use of xdg-desktop-portal-wlr, including other remote desktop software and screensharing on other web browsers.
To keep all info on one place, this has already been reported on the bookworm feedback forum here with no response so far, and was mentioned on this pi-apps issue
Tagging @theofficialgman
The text was updated successfully, but these errors were encountered: