Elektrine lite

← Feed

@akunohana@piefed.blahaj.zone

2026-11-13 19:55 UTC

Nice! I do wonder whether you initiated/sent this SIGTERM ("close") or if this is something out of the ordinary… Especially considering that it’s a few minutes after boot - perhaps when you start Proton and qBit? ```` – Boot BOOT-ID-09 – Nov 10 +0h 31:11 HOSTNAME qbittorrent[PID]: QFSFileEngine::open: No file name specified Nov 10 +0h 31:11 HOSTNAME qbittorrent[PID]: QFSFileEngine::open: No file name specified Nov 10 +0h 38:57 HOSTNAME qbittorrent[PID]: Catching signal: SIGTERM Nov 10 +0h 38:57 HOSTNAME qbittorrent[PID]: Exiting cleanly What's actually worrying (without me understanding its implications for qBit specifically) is the segmentation fault: Nov 01 +0h 47:18 HOSTNAME qbittorrent[PID]: Caught signal: SIGSEGV ``` I was looking for the corresponding timestamps for the above two entries of qBit within the logs of Proton, but Proton’s logs only show logs from the 13th. You can disregard the sudo dmesg -l err output for now, because this error pertains to something else. Unfortunately I don’t know much more, but maybe somebody with more experience and understands the logs better can help! What I would do is to do a fresh install of qBit to start with. Make sure to save your torrent cache so that you don’t lose your uploads/downloads! I’ll get back to you if anything else comes to mind. If you feel up for the task, you could try to find the above mentioned logs of Proton whose timestamps are close to the segfault that qBit reported!

Replies (3)

  • @crow@leminal.space 2026-11-13 20:06

    Nov 10 was three days ago and that’s more or less when this issue started happening. I’ll check the logs again and see if I remember something. I usually don’t close qBit as soon as I boot the system, routine is boot, launch PVPN, connect, launch qBit and I don’t close it ever. The Proton log is truncated because it was tens of thousands of lines lol so I had the journalctl print only the last few lines, but, yeah, I can fetch its logs for Nov 10 and Nov 01, I’ll add them asap. I was just thinking that I did not try to reinstall qBit and maybe I should do that! Thanks again

    Open ##5530606

  • @akunohana@piefed.blahaj.zone 2026-11-13 20:08

    It also could be worth dumping the whole log to see if there are other things at work here, even if you suspect foul play between qBit and Proton specifically. In that case you would just hit journalctl.

    Open ##5530642

  • @crow@leminal.space 2026-11-13 20:38

    So, journalctl for the VPN shows nothing for Nov 01 around that time (only what I suppose is normal networking, “sending request - receiving response”). I remember that the qBit client froze at some point and I had to xkill it, though I’m not sure it was so long ago, I think it was less than a week ago. Anyway this is the journalctl for that day, around that time: pastebin.com/Y9eXqbgL in a few minutes I’ll add the VPN log matching the Nov 10 qBit SIGTERM

    Open ##5530969