Lorenzo Frydrich Rodrigues

Have got my Android client to work, both in the GitHub latest release (which has a random song disconnection issue that probably isn't tied to my broadband) and in the...

Package upgrade on Arch has brought me this issue, now the container can't start.

> Hi, I also installed waydroid from AUR, but I'm unamble to run it because of `python-gbinder` error. The package is installed, reinstalled and rebuilt multiple times, also I checked...

Thanks for the hasty response. Let me stress my workflow, in case it helps you and really anyone to understand my hinder: * SDDM starts Wayland for me. * I...

> Isn't it a docker container where you run clip_share inside it? No, I'm running clip_share from the host. Does that make things more difficult?

> No. It should make it easier. Does the host have Wayland? and does it have XWayland? (usually it should have). Also does the host has real display hardware? Yep,...

> If you are not using the container having X11 for anything other than clip_share, can you try to stop that container and re-run clip_share on the host without the...

> What is the DISPLAY variable on the host? Does that variable (on the host) change when you switch between containers? If that changes with the foreground container, things may...

> You don't need the *-dev packages to run the compiled binaries. Anyway that will install libunistring. But If there's a mismatch in the version of it, this error may...

> I guess this focus issue is arising with the containers. If the `DISPLAY` variable (on the host) change when you switch between containers, it might make issues with clip_share....