"Open Destination Folder" stopped working with qBittorrent

Issues related to applications and software problems and general support
Post Reply
ek123
Posts: 10
Joined: 2019/10/22 15:25:54

"Open Destination Folder" stopped working with qBittorrent

Post by ek123 » 2020/10/21 16:23:08

So, not sure when this stopped, but it's been at least a month. I am running qbittorrent 4.3 on CentOS 8 and at some point the option to open destination folder has stopped working. I've been dealing with it, but recently decided to wipe the qbittorrent install, delete all associated files, and start over.

I'm still not able to get it working like it used to. I also tried setting the option to open the destination folder with double click completed torrents - still no dice. This isn't anything more than just terribly annoying, but I obviously use that option a lot and would like to get it working again.

The only changes I can think of aside from updating qbittorrent (note, this was not working on 4.2.5 and still isn't working on 4.3.0) and the OS is that I had recently moved my default save location away from my home directory to a mounted directory with a lot more space. I've got rwx permissions on the mount and qbittorrent is running under the same account that owns the mounted directory. I honestly don't know if it stopped working when I change to the mount, but I can't say it didn't; accepting the default locations on the clean install didn't change the behavior.

Also, after wiping the install on my CentOS box and still seeing it fail I installed v4.2.5 on one of my Fedora 32 systems - default settings - and Open Destination Folder works fine.

Any help would be greatly appreciated.

--ek

BShT
Posts: 370
Joined: 2019/10/09 12:31:40

Re: "Open Destination Folder" stopped working with qBittorrent

Post by BShT » 2020/10/21 17:27:31

any log?

when you wiped it, eventually you wiped .anything at your home directory?

ek123
Posts: 10
Joined: 2019/10/22 15:25:54

Re: "Open Destination Folder" stopped working with qBittorrent

Post by ek123 » 2020/10/21 17:58:06

Honestly, not sure what log would be of use here. Reproduced and captured output from journalctl and dmesg; if there is something specific I can grab let me know. I looked at the execution log in qbittorrent but it didn't show anything.

journalctl
Oct 21 10:44:51 mtolympus dbus-daemon[3130]: [session uid=1000 pid=3130] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.646' (uid=1000 pid=1035713 comm="/usr/libexec/flatpak-dbus-proxy --args=45 " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Oct 21 10:44:51 mtolympus systemd[1812]: Starting Portal service...
Oct 21 10:44:51 mtolympus dbus-daemon[3130]: [session uid=1000 pid=3130] Successfully activated service 'org.freedesktop.portal.Desktop'
Oct 21 10:44:51 mtolympus systemd[1812]: Started Portal service.
Oct 21 10:44:51 mtolympus kernel: pool[1322363]: segfault at 0 ip 00007f58ddb9a9e4 sp 00007f58d288a968 error 4 in libglib-2.0.so.0.5600.4[7f58ddb5e000+116000]
Oct 21 10:44:51 mtolympus kernel: Code: 84 00 00 00 00 00 f3 0f 1e fa 48 83 ec 08 e8 b3 f1 fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 66 0f 1f 44 00 00 f3 0f 1e fa <0f> be 17 b8 05 15 00 00 84 d2 74 18 89 c1 48 83 c7 01 c1 e1 05 01
Oct 21 10:44:51 mtolympus abrt-hook-ccpp[1322368]: Process 1322360 (xdg-desktop-portal) of user 1000 killed by SIGSEGV - dumping core
Oct 21 10:44:51 mtolympus systemd[1812]: xdg-desktop-portal.service: Main process exited, code=killed, status=11/SEGV
Oct 21 10:44:51 mtolympus systemd[1812]: xdg-desktop-portal.service: Failed with result 'signal'.
Oct 21 10:44:51 mtolympus abrt-server[1322372]: Deleting problem directory ccpp-2020-10-21-10:44:51-1322360 (dup of ccpp-2020-08-23-22:05:09-7762)
Oct 21 10:44:51 mtolympus dbus-daemon[1219]: [system] Activating service name='org.freedesktop.problems' requested by ':1.9375' (uid=0 pid=1322381 comm="/usr/libexec/platform-python /usr/bin/abrt-action-" label="system_u:system_r:abrt_t:s0-s0:c0.c1023") (using servicehelper)
Oct 21 10:44:51 mtolympus dbus-daemon[1322383]: [system] Failed to reset fd limit before activating service: org.freedesktop.DBus.Error.AccessDenied: Failed to restore old fd limit: Operation not permitted
Oct 21 10:44:51 mtolympus dbus-daemon[1219]: [system] Successfully activated service 'org.freedesktop.problems'
Oct 21 10:44:51 mtolympus abrt-server[1322372]: /bin/sh: reporter-systemd-journal: command not found

dmesg
[Oct21 10:52] pool[1323020]: segfault at 0 ip 00007fdc6b1069e4 sp 00007fdc5fffe968 error 4 in libglib-2.0.so.0.5600.4[7fdc6b0ca000+116000]
[ +0.000012] Code: 84 00 00 00 00 00 f3 0f 1e fa 48 83 ec 08 e8 b3 f1 fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 66 0f 1f 44 00 00 f3 0f 1e fa <0f> be 17 b8 05 15 00 00 84 d2 74 18 89 c1 48 83 c7 01 c1 e1 05 01

And, when I wiped I ran dnf erase for the app and then
rm -fr ~/.var/app/org.qbittorrent.qBittorrent

BShT
Posts: 370
Joined: 2019/10/09 12:31:40

Re: "Open Destination Folder" stopped working with qBittorrent

Post by BShT » 2020/10/21 18:56:11

you can run qbittorrent at console and see its output

look if there is a .qbittorrent at your home

ek123
Posts: 10
Joined: 2019/10/22 15:25:54

Re: "Open Destination Folder" stopped working with qBittorrent

Post by ek123 » 2020/10/21 21:50:10

Thanks, BShT
BShT wrote:
2020/10/21 18:56:11
you can run qbittorrent at console and see its output

look if there is a .qbittorrent at your home
This got me looking a bit more when I couldn't run qbittorrent directly and I was prompted to install. I verified my install, and it was from flatpak - the epel release was v4.2.5 (that version was also failing for me on flatpak before it was updated to 4.3.0)

Anyway, that was the path I explored and was able to get it working. It seems it was something with the flatpak install. In case anyone else runs into this and wants to make it a little less painful to deal with, this is what I did.

Install latest stable version from epel repo - v4.2.5
$ dnf install qbittorrent

Created backup of ~/.config/qBittorrent/ then copied relevant config files to cover most of what I was looking to maintain. This pulled over the config settings, saved rss feeds, and autodownloader rules to the repo install

$ cp ~/.var/app/org.qbittorrent.qBittorrent/config/qBittorrent/qBittorrent.conf ~/.config/qBittorrent/qBittorrent.conf
$ cp ~/.var/app/org.qbittorrent.qBittorrent/config/qBittorrent/rss/feeds.json ~/.config/qBittorrent/rss/feeds.json
$ cp ~/.var/app/org.qbittorrent.qBittorrent/config/qBittorrent/rss/download_rules.json ~/.config/qBittorrent/rss/download_rules.json

Uninstall flatpak install v4.3.0
flatpak remove org.qbittorrent.qBittorrent

Then remove leftovers from the flatpak install
$ rm -fr ~/.var/app/org.qbittorrent.qBittorrent

Launch qbittorrent, confirm settings/rss/rules and move on.

The part I missed in doing this was pulling over active seeding torrents, but I was able to add those back easily since I only had a few at the time. I didn't test to confirm, but it looks like I could have recovered the existing seeds with the following

$ cp ~/.var/app/org.qbittorrent.qBittorrent/data/data/qBittorrent/BT_backup ~/.local/share/data/qBittorrent/BT_backup

I appreciate the response @BShT, I wouldn't have looked at the install source if not for your comment. Hope this helps someone else.

--ek

Post Reply

Return to “CentOS 8 - General Support”