#1113916 qbittorrent: crashes unpredictably

Package:
qbittorrent
Source:
qbittorrent
Description:
bittorrent client based on libtorrent-rasterbar with a Qt5 GUI
Submitter:
Xiyue Deng
Date:
2025-09-20 06:15:03 UTC
Severity:
normal
#1113916#5
Date:
2025-09-04 05:52:05 UTC
From:
To:
Dear Maintainer,

I use chrome-remote-desktop to connect to my box running KDE on Trixie,
and run qbittorrent QT GUI.

Nothing in particular, just run it normally.

qbittorrent crashes randomly.  Sometimes it will run just fine, and
sometimes it will crash after around 15-30 seconds.

I hope it can run just fine.  When my box was still on Bookworm the
qbittorrent had been running mostly stable, but this started to happen
after upgrading to Trixie.

I also have grabbed a backtrace following the suggestions on the
wiki[1].  The output is attached which I hope can be helpful for
debugging.

[1] https://wiki.debian.org/HowToGetABacktrace

#1113916#10
Date:
2025-09-04 06:16:48 UTC
From:
To:
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.
`----



Christian

#1113916#15
Date:
2025-09-07 06:21:14 UTC
From:
To:
Hi Christian,

Thanks for replying.  In fact, I have libxcb-cursor0 installed as well which
was not picked up by reportbug:

,----
| $ dpkg -l | grep xcb-cursor0
| ii  libxcb-cursor0:amd64                                0.1.5-1                              amd64        utility libraries for X C Binding -- cursor
`----

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.

#1113916#20
Date:
2025-09-07 06:44:39 UTC
From:
To:
[...]

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

#1113916#25
Date:
2025-09-07 07:09:08 UTC
From:
To:
Hi Christian,
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.

#1113916#30
Date:
2025-09-07 09:24:08 UTC
From:
To:
On 07 sept. 2025 00:09, Xiyue Deng <manphiz@gmail.com> wrote:


[...]

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 ?

Christian

#1113916#35
Date:
2025-09-07 21:00:52 UTC
From:
To:
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.

[1] https://support.google.com/chrome/answer/1649523

#1113916#40
Date:
2025-09-10 18:12:58 UTC
From:
To:
On 07 sept. 2025 14:00, Xiyue Deng <manphiz@gmail.com> wrote:


[...]

Are you aware that you can access a running qbitorrent with a browser at
this address http://localost:9000/  when qbitorrent is running ?

And if qbitorrent crash with Qt errors you install the qbitorrent-nox
package and do the same at port 8080 http://localost:808/

Christian

#1113916#45
Date:
2025-09-11 06:31:40 UTC
From:
To:
Hi Christian,

Yes, I have used qbittorrent-nox, though I miss using the QT file dialog
which makes it easy for me to choose a local path.

I also checked upstream issues, and the general advice is to upgrade to
5.1.2 and check again.  Can I request a backport of 5.1.2-1 for further
testing, which has already entered Forky?

Thanks!

P.S. Also, actually I'm having issue to receive your email from BTS, and
was not able to receive any of your previous email directly.  I had to
use the reply link in BTS to avoid breaking the thread.  I also filed
bug#1114649 for tracking.  From the discussion there, it seems that
using the NNNNNNN-submitter@bugs.debian.org address can be a workaround.
Can you reply using that forwarder email address to help test whether I
can receive the email directly?

#1113916#50
Date:
2025-09-18 07:18:52 UTC
From:
To:
Xiyue Deng <manphiz@gmail.com> writes:

So I manually backported 5.1.2-1 to Trixie and has been running it for
the past few days and I have not experienced the same issue again, so
apparently this is fixed in 5.1.2.

Can I request a backport so that other people experiencing the same
issue can upgrade to resolve this?  Or should I open a separate wishlist
bug for the backport?

#1113916#55
Date:
2025-09-18 08:08:44 UTC
From:
To:
On 18 sept. 2025 00:18, Xiyue Deng <manphiz@gmail.com> wrote:


[...]

I'll do a backport package. Here I'm talking about stable-backport and
not stable

Christian

#1113916#60
Date:
2025-09-18 09:14:20 UTC
From:
To:
On 18 sept. 2025 00:18, Xiyue Deng <manphiz@gmail.com> wrote:


[...]

Pakcages uploaded to trixie-backports

Christian

#1113916#61
Date:
2025-09-19 02:18:40 UTC
From:
To:
"Debian Bug Tracking System" <owner@bugs.debian.org> writes:

Thanks a lot!  I saw that qbittorrent is in the backports new.  Hope it
will graduate soon!

#1113916#66
Date:
2025-09-20 06:12:52 UTC
From:
To:
Another attempt to set a fixed version number.