Tribler 7.3.0 RC2 is out!


#1

Dear Tribler Community,

Tribler 7.3.0-rc2 is available today. This version includes several fixes and improvement over the 7.3.0 RC1 release. For upgrade from stable version, everything should work fine. Since it is a pre-release version, we suggest keeping a backup of your state directory before trying out this release.

The binaries are available below or can be downloaded from the official release page at Github repository.
Windows(64-bit)
Windows (32-bit)
Linux
MacOS

If you encounter any problems using this release, feel free to report back to us. We’ll appreciate that. You can either create an issue ticket in Github (link here) or simply post it here in this forum.

For developers willing to contribute to Tribler with bug fixes or new features please check out this page which provides the basic pointers to get started.

And as always, the source code can be found on our Github repository but you can also download it directly here.

We hope you enjoy using this version.
Cheers!


#2

same as RC1

Traceback (most recent call last):
File “/usr/share/tribler/TriblerGUI/event_request_manager.py”, line 136, in
self.reply.error.connect(lambda error: self.on_error(error, reschedule_on_err=reschedule_on_err))
File “/usr/share/tribler/TriblerGUI/event_request_manager.py”, line 81, in on_error
raise RuntimeError(“Could not connect with the Tribler Core within 60 seconds”)
RuntimeError: Could not connect with the Tribler Core within 60 seconds

real 1m19,139s
user 0m10,405s
sys 0m1,864s

no hdd activity during this time


#3

This version has a problem with restoring the window to its original size after having been minimized when the trust graph was in view. In that case, it either displays a scaled down version of the GUI in the top left corner of the window, or just displays a white window. In both cases the window becomes unresponsive for a while.

Furthermore, the progress bar of the trust graph hangs at 0%.

Edit 06/08/2019

Eventually a trust graph will be displayed. However, it seems to take even longer than before.


#4

Hi, I have downloaded a file, added to “my chennel” and fas seeding to several peers, none of them running Tribler. No token mining at all.
I love the idea to share with the tribler community, but what can I do if nomody want my shares, while user with other torrents client are hungry of them?
How can I share files usefull to the tribler community? Still very confused on this.

Ciao


#5

I’ve encountered the following error:

Traceback (most recent call last):
  File "TriblerGUI\event_request_manager.py", line 114, in on_read_data
RuntimeError: [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'address'
lib\threading.py:801:__bootstrap_inner
lib\threading.py:754:run
lib\site-packages\twisted\_threads\_threadworker.py:46:work
lib\site-packages\twisted\_threads\_team.py:190:doWork
--- <exception caught here> ---
lib\site-packages\twisted\python\threadpool.py:250:inContext
lib\site-packages\twisted\python\threadpool.py:266:<lambda>
lib\site-packages\twisted\python\context.py:122:callWithContext
lib\site-packages\twisted\python\context.py:85:callWithContext
Tribler\Core\APIImplementation\LaunchManyCore.py:572:sesscb_states_callback
Tribler\community\triblertunnel\community.py:501:monitor_downloads
Tribler\community\triblertunnel\community.py:531:create_introduction_point
ipv8\messaging\anonymization\hidden_services.py:479:create_introduction_point
ipv8\messaging\anonymization\hidden_services.py:171:create_circuit_for_infohash
ipv8\messaging\anonymization\community.py:315:create_circuit