On 06 sept. 2025 23:21, Xiyue Deng <[email protected]> wrote:

> Hi Christian,
>
> On Thu, 04 Sep 2025 08:16:48 +0200 Christian Marillat <[email protected]> 
> wrote:
>> On 03 sept. 2025 22:52, Xiyue Deng <[email protected]> wrote:
>> 
>> > Package: qbittorrent
>> > Version: 5.1.0-2
>> > Severity: important
>> >
>> > Dear Maintainer,
>> >
>> >> *** Reporter, please consider answering these questions, where 
>> >> appropriate ***
>> >
>> >>    * What led up to the situation?
>> >
>> > I use chrome-remote-desktop to connect to my box running KDE on Trixie,
>> > and run qbittorrent QT GUI.
>> 
>> Maybe first lines in the GDB log file can help ?
>> 
>> ,----
>> | [New Thread 0x7ffff10836c0 (LWP 881742)]
>> | qt.qpa.xcb: could not connect to display
>> | qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed
>> | to load the Qt xcb platform plugin.
>> | qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in ""
>> | even though it was found.
>> | This application failed to start because no Qt platform plugin
>> | could be initialized. Reinstalling the application may fix this
>> | problem.
>> | 
>> | Available platform plugins are: minimal, wayland-egl,
>> | vkkhrdisplay, offscreen, xcb, minimalegl, linuxfb, vnc, wayland,
>> | eglfs.
>> `----

[...]

> Also I notice that if I continue to launch the qbittorrent process, the crash
> might happen quite a few times and then it will stabilize eventually
> and run stably after, which is quite puzzling.

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) ?

Christian

Reply via email to