Tribler segfaults after a few minutes of running on Fedora Secureblue

[ElonSatoshi]

OS: Fedora Secureblue

Observations:

• When torrents show that DHT is disabled, I know that it's going to crash
• error in dmesg: [85442.655707] tribler[248302]: segfault at 28 ip 000067dfea97befe sp 000067dfe5bf0870 error 4 in __init__.cpython-310-x86_64-linux-gnu.so[37befe,67dfea723000+6e7000] likely on CPU 1 (core 1, socket 0)
• Running Tribler produces audit backlog errors in dmesg unless I increase the backlog limit with auditctl. Sometimes increasing the backlog limit fixes Tribler, but lately Tribler has been crashing despite increasing the backlog limit

[qstokkink]

Do you know of any repository with Secureblue ISO's (so I can spin up a VM to reproduce this)?

That said, looking at your error, it seems that our libtorrent library is causing the segfault. In the Tribler 8.2.0 this dependency was updated, so, the situation might resolve itself in our next version.

[ElonSatoshi]

Interesting. I just got the new version, trying it out after rebooting. I first observed DHT being disabled, but after I disabled debug mode, I noticed DHT is now working on torrents.

What do you mean a repository with secureblue ISOs? You can download the ISO here, but that's actually a new feature. The traditional way is to install Fedora Silverblue, then rebase it to Secureblue.

IF you meant repository for installing Tribler, I just used the flatpak.

I'll keep testing, maybe the issue is resolved by the update. If so, thanks!

[qstokkink]

Yes, the repository with secureblue ISOs is exactly what I was looking for¹: thanks!

If the new version is working correctly, I won't try to reproduce your issue just yet. Please let me know if your Tribler starts misbehaving again and I'll give that a go.

Footnotes

1. I try to mimic the OS for issues exactly, if I can. However, some distros are a royal pain to set up. If at all possible, I like doing the least amount of work using a pre-prepared ISO. ↩