We’re thrilled to introduce Tribler 7.13.1-RC1.
We are excited to announce Tribler 7.13.1-RC1, a bugfix release that notably enhances the stability of Tribler, especially during startup. This update addresses several critical issues, including problems related to Tribler startup, database corruption, and various other bugs. Our team has worked diligently to ensure a smoother and more reliable experience for our users.
- Use the
filelocklibrary to determine the primary process
- Fix Core crash caused by
TimeoutErrorwhen the REST HTTP server is starting
StartDownloadDialogduring Tribler UI startup
- Handle the database corruption error by regenerating the corrupted database on the fly
- Fix race condition in
- Handle exceptions in
- Use the
safe_reprfunction to display alert reprs
RESTResponseerror for timed out metainfo request
- Removed circuit from peer_info
TypeErrorwhen the translated string does not have the correct number of positional parameters
- Add the reason for the
OperationalError: unable to open database filewhen opening
- Add Tribler Config to the sentry event
- Show correct stack trace for CoreCrashedError
The binaries are available below, or you can download them from the official release page at the GitHub repository:
Note: Some antivirus software falsely flags the Windows 32-bit version of Tribler. When investigating the issue, we found that the Python builder we use (PyInstaller) is being flagged even for a simple Hello World program. So, your antivirus might flag Tribler as malware if you’re using the 32-bit version. Therefore, we suggest you use the 64-bit version if you can.
If you encounter any problems using this release, you can create an issue ticket on GitHub or post it here in this forum.
For developers willing to contribute to Tribler with bug fixes or new features, please check out the Tribler contributing page, which provides the basic guidelines.
We hope you’ll enjoy using this version.