On Sun, 07 Sep 2025 11:24:08 +0200 Christian Marillat <[email protected]> wrote: > On 07 sept. 2025 00:09, Xiyue Deng <[email protected]> wrote: > > > [...] > > >> This bug isn't related to qbittorrent. > >> > >> qt.qpa.xcb: could not connect to display > >> > >> Which display is installed on teh remote machine (x11, wayland) ? > >> > > > > It's x11 (as a matter of fact chrome-remote-desktop doesn't support > > wayland yet.) > > > > Also, I probably didn't make it clear: qbittorrent was able to show it's > > GUI fine - and you can actually interact with it like clicking menus, > > item list, details, etc. - before it crashes. So it's not obvious to me > > what the "could not connect to display" part it is referring to. > > qbittorrent is working as expected in a "normal" environment. > I'm unable to do tests in a remote desktop. > > chrome-remote-desktop come from which package ?
It is provided by Google. I think this page[1] should have enough info for setting it up. It does require a Google account though. > > Christian [1] https://support.google.com/chrome/answer/1649523 -- Regards, Xiyue Deng
signature.asc
Description: PGP signature
