Replies (1)

• @akunohana@piefed.blahaj.zone 2026-11-13 19:55

  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!

  Open ##5530488