v7.13.1

Overview

We are excited to announce Tribler 7.13.1, 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.

Startup stability fixes

• #7603: Use the filelock library to determine the primary process by @kozlovsky in #7660
• Use dedicated exit codes when another primary GUI/Core process is running by @kozlovsky in #7746
• #7592: Fix Core crash caused by TimeoutError when REST HTTP server is starting by @kozlovsky in #7617
• #7641: Fix TypeError in StartDownloadDialog during Tribler UI startup by @drew2a in #7662

Database Integrity

• #5252: Handle the database corruption error by regenerating the corrupted database on the fly by @kozlovsky in #7628

General stability fixes

• Use the default event loop on Windows by @qstokkink in #7677
• Reconnect to the Core in case of EventReqestManager disconnection by @kozlovsky in #7747
• #7602 Fix race condition in SlowCoroWatchingThread by @kozlovsky in #7613
• #7600: Handle exceptions in task.print_stack() by @kozlovsky in #7614
• #7598: Use safe_repr function to display alert reprs by @kozlovsky in #7616
• #7056: Return RESTResponse error for timed out metainfo request by @drew2a in #7627
• #7670: Removed circuit from peer_info by @egbertbouman in #7700

Localization robustness

• #7599: Fix TypeError when the translated string does not have the correct number of positional parameters by @kozlovsky in #7615

Enhanced error reporting

• Add the reason for the OperationalError: unable to open database file when opening processes.sqlite by @kozlovsky in #7612
• Add Tribler Config to the sentry event by @drew2a in #7665
• Show correct stack trace for CoreCrashedError. by @drew2a #7713 (Implemented in #7722)

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.

Full Changelog: v7.13.0...v7.13.1