Mageia forum

I am using Ktorrent 22.12.3 as shipped with Mageia 9 beta 1. Most of the time it works fine.

However (and I've seen this happen several times, it just dies unexpectedly. It stops any downloads and then just seems to exit.

Could this be a problem with my VPN (NordVPN) and not Ktorrent? NordVPN seems to be working normally (I use Nordlynx...it has something to do with WireGuard)

Where would I even start looking?

Thank you.

Simply start ktorrent from a terminal and look for output when it crashes. Also have a look into journal....

OK, I've started ktorrent from a terminal. Do I need to add something to the command line so it will show an error?

Also, how do I look into a journal? I seem to have several in /var/log

Thank you.

You should be able to start it with --verbose to enable it to show logs to stdout again, as that was disabled some time ago because otherwise it would fillup your X session log pretty quickly.

lloyd wrote:Also, how do I look into a journal? I seem to have several in /var/log

As root

Code: Select all

journalctl -ab

shows the journal logs from current boot, you can simply search in there for ktorrent. It uses the default pager (less) so just /ktorrent and then n to search forward and N to search reverse.
You can also check the logs from previous boots where it may have crashed with

Code: Select all

journalctl -ab-N

where N is the number of boots. so journalctl -ab-1 would show the previous boot. That is, if you have persistent logs enabled, which should be the default IIRC.

I looked through the journal. I didn't find any mention of ktorrent. What do I do next?

This is what I got when starting ktorrent from Konsole.....

Code: Select all

ktorrent --verbose

When I closed ktorrent, this showed up in Konsole. Could this be the cause of the crashes?

Code: Select all

Sun. Apr. 2 06:22:40 2023: Saving list of peers to /home/lloyd/torrents/tor33/peer_list
Sun. Apr. 2 06:22:40 2023: Qt Warning: 0x28857e0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
Warning: 0x28857e0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.

In the old days it was possible to enable more debug logging for KDE components. This should still work via kdebugdialog5 - you would need to check if there is any specific logging for ktorrent or just enable all debug logging. Then try starting ktorrent again and check the logs.

You may also want to check the upstream reports: https://bugs.kde.org/buglist.cgi?quicks ... nt%20crash