Github messages for voidlinux
 help / color / mirror / Atom feed
From: chloris-pale-green <chloris-pale-green@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] `qbittorrent-4.4.3.1_1` crashes on `libtorrent-rasterbar` update to 1.2.14_4
Date: Sat, 03 Sep 2022 07:02:05 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39078@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2624 bytes --]

New issue by chloris-pale-green on void-packages repository

https://github.com/void-linux/void-packages/issues/39078

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.19_1 x86_64 GenuineIntel uptodate rFFFFFFFFFFFF

### Package(s) Affected

qbittorrent-4.4.3.1_1, libtorrent-rasterbar-1.2.14_4

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

qBittorrent should launch without crashing.

### Actual behaviour

qBittorrent launches immediately after the splash screen  is shown (if it is enabled).

Here is the console output:
```
*** stack smashing detected ***: terminated


*************************************************************
Please file a bug report at http://bug.qbittorrent.org and provide the following information:

qBittorrent version: v4.4.3.1

Caught signal: SIGABRT
Stack trace:
  /usr/lib/libc.so.6 : gsignal()+0x141  [0x7fc2a3876f81]
  /usr/lib/libc.so.6 : abort()+0x112  [0x7fc2a3860536]
  /usr/lib/libc.so.6 : ()+0x7e4f8  [0x7fc2a38b84f8]
  /usr/lib/libc.so.6 : __fortify_fail()+0x22  [0x7fc2a39475f2]
  /usr/lib/libc.so.6 : __fortify_fail()+0  [0x7fc2a39475d0]
  qbittorrent : NativeTorrentExtension::NativeTorrentExtension(libtorrent::torrent_handle const&)+0xac  [0x558d3d1127dc]
  qbittorrent : NativeSessionExtension::new_torrent(libtorrent::torrent_handle const&, void*)+0x49  [0x558d3d1124c9]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0x2228b6  [0x7fc2a5c228b6]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0x234543  [0x7fc2a5c34543]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0x234b1b  [0x7fc2a5c34b1b]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0x1fde16  [0x7fc2a5bfde16]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0x204eb5  [0x7fc2a5c04eb5]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0xcffbf  [0x7fc2a5acffbf]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0x1f2dc1  [0x7fc2a5bf2dc1]
  /usr/lib/libtorrent-rasterbar.so.10 : ()+0x1f02d3  [0x7fc2a5bf02d3]
  /usr/lib/libstdc++.so.6 : ()+0xfbdcf  [0x7fc2a3afbdcf]
  /usr/lib/libpthread.so.0 : ()+0x8eae  [0x7fc2a5ff3eae]
  /usr/lib/libc.so.6 : clone()+0x3f  [0x7fc2a39382ff]
fish: Job 1, 'qbittorrent' terminated by signal SIGABRT (Abort)
```

### Steps to reproduce

1. Update `libtorrent-rasterbar` to 1.2.14_4.
2. Try to run qBittorrent from terminal and observe the crash.
3. Downgrade `libtorrent-rasterbar` to 1.2.14_2. I used the following:
```shell
sudo xdowngrade /var/cache/xbps/libtorrent-rasterbar-1.2.14_2.x86_64.xbps
```
4. Try to run qBittorrent again. It should produce no errors.

             reply	other threads:[~2022-09-03  5:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03  5:02 chloris-pale-green [this message]
2022-09-03  9:18 ` sgn
2022-09-03  9:24 ` sgn
2022-09-03 10:50 ` [ISSUE] [CLOSED] " sgn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39078@inbox.vuxu.org \
    --to=chloris-pale-green@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).