V7.1.0 experimental release


#1

Hello everyone,

We have released the next experimental version of Tribler (version 7.1). The last few weeks, we have invested much time into the stability and performance of Tribler. We fixed dozens of bugs in this experimental version. In addition, our next release contains the following major new functionality:

  • a preview of our new mechanism to quickly synchronise real-time health of torrents. This mechanism makes healthy (well-seeded) torrents show up higher in the search results while suppressing dead torrents. It is our first step towards a functional and scalable content system.
  • an improved implementation of our blockchain (TrustChain). In previous version of Tribler, separate blockchain operations, like bandwidth accounting and trading, were performed on different, independent blockchains. We improved security and reliability of our blockchain by combining all functionality into a single ledger. Our aim is to release a public TrustChain explorer soon.

Download our new experimental release here:
Windows (64-bit)
Windows (32-bit)
Linux
MacOS

We hope you will have a much better experience with this release. We would really like you to install our experimental release and report to us if something does not work well for you.
To report any problem, please create a new issue on GitHub or post it on the forum, either in this thread or in a separate thread. If you wish to contribute to Tribler by fixing bugs or by adding new features, please check out this page which provides a basic pointers for developers to get started.

The source code can be found on our Github repository.

Enjoy!


#2

This version doesn’t get passed the rotating gear screen before it crashes on Win 10 (64bit version).


#3

Could you post the error you see?


#4

Here you go:

Traceback (most recent call last):
File "TriblerGUI\core_manager.py", line 114, in on_received_state
RuntimeError: Unhandled Error
Traceback (most recent call last):
File "lib\site-packages\twisted\internet\base.py", line 428, in  fireEvent

File "lib\site-packages\twisted\internet\defer.py", line 321, in addCallback

File "lib\site-packages\twisted\internet\defer.py", line 310, in addCallbacks

File "lib\site-packages\twisted\internet\defer.py", line 653, in _runCallbacks

--- <exception caught here> ---
File "lib\site-packages\twisted\internet\base.py", line 441, in _continueFiring

File "run_tribler.py", line 52, in start_tribler

File "Tribler\dispersy\util.py", line 46, in helper

File "Tribler\dispersy\util.py", line 225, in blockingCallFromThread

File "Tribler\Core\Session.py", line 463, in start

File "Tribler\Core\Upgrade\upgrade.py", line 57, in run

File "Tribler\Core\Upgrade\upgrade.py", line 67, in upgrade_to_tribler7

File "Tribler\Core\Upgrade\config_converter.py", line 42, in convert_config_to_tribler71

File "lib\ConfigParser.py", line 305, in read

File "lib\ConfigParser.py", line 512, in _read

ConfigParser.MissingSectionHeaderError: File contains no section headers.
file: C:\Users\User1\AppData\Roaming\.Tribler\dlcheckpoints\0542c87fb022939e9aad2ab3c39782ae58be9634.state, line: 1
'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00 etc. etc.

#5

@LesVerres thank you for posting this error. It should be fixed now. Could you please try out this build? https://jenkins.tribler.org/job/Build_Tribler_next/297/


#6

Tribler does start now and seems to work fine, although shutting it down takes ages. For that I have to use the orange button at the bottom that appears after a while.


#7

I’m not sure if it’s coincidence or not, but I used to have the problem of Tribler taking forever (literally–would not close on its own) to close, but seemed to finally stop on one of the most recent releases–after I completely uninstalled the program AND deleted anything Tribler in the AppData folder (Windows 10 x64 as well).

I’m not sure why to this day, Windows does not offer the option to completely uninstall something including saved data. Probably trying to get more “satisfied” users when they blunder and uninstall something accidentally, but don’t lose everything. Rant over.

So anyway, I’d be curious if doing that makes it go away, just a thought.


#8

We fixed an issue where Tribler would be stuck during the shutdown procedure in this experimental release so that might partially explain your observation. I will discuss tomorrow what we can do to increase the startup time and shutdown time of Tribler.

Removing the state directory might help to fix various issues, although you have to manually add your downloads again to Tribler after doing this. Also, when removing the state directory, all discovered content, including your own channel, will be lost. Please make sure to backup your state directory first before removing it.


#9

So, is libsodium still a dependency for the Linux installation of this build?


#10

Yes, libsodium is still a dependency.


#11

Thanks for the answer. Do you happen to know what its purpose is with regards to Tribler?

I suppose I may have to wait and see if the Linux distros I was using re-gain support for it in their repositories for the latest versions. :-/


#12

it is a requirement for libnacl, our main package to perform cryptographic tasks. Since we heavily rely on it, we cannot easily get rid of it. What operating system (Linux distro) are you using?


#13

I was using a fresh installation of Linux Lite (based on Ubuntu 18.04) while running into the issue of libsodium not being available.


#14

A quick search reveals that libsodium23 is in the Ubuntu 18.04 repositories: https://packages.ubuntu.com/search?keywords=libsodium23

Could you do an apt-get search libsodium* and see whether there’s any libsodium version in your Linux installation?


#15

I will do so when I get a chance. I’m beginning to think I just had bad luck and grabbed an ISO for 18.04 so soon after release that not all the repositories had a chance to catch up, and I was stuck with libsodium18 being available only in 16.04 and 17.10, but nothing available for 18.04 at that point in time. Thanks! :slight_smile:


#16

Yay! Got Tribler 7.1.0 installed. Thanks, devos


#17

Another problem, torrents added via magnet links disappear once the program is closed and re-opened.


#18

This thing is still randomly grabbing the better part of a processor core after running for an extended period. I’m not sure what causese it:

Here’s some terminal puke:

0x0000000006BB1D68>, [‘Invalid signature’], (Block af74a45b from …b01cf24d:116 links …a37f51a5:20666 for {‘down’: 0, ‘total_down’: 2995043, ‘up’: 6578204, ‘total_up’: 2258210033L} type tribler_bandwidth)
INFO 1533702318.59 community:304 (TrustChainCommunity) Block validation result <function partial_next at 0x0000000006BB1C18>, [], (Block f6f7caef from …a37f51a5:20666 links …b01cf24d:0 for {‘down’: 6578204, ‘total_down’: 243687627083L, ‘up’: 0, ‘total_up’: 6319814120L} type tribler_bandwidth)
WARNING 1533702319.80 community:498 (SearchCommunity) message from <Candidate 78.237.197.174:7759> cannot be found in the request cache, skipping it
INFO 1533702319.83 community:833 (TriblerTunnelCommunity) TunnelCommunity: we joined circuit 1782446495 with neighbour (‘92.255.112.3’, 59992)
WARNING 1533702319.84 community:498 (SearchCommunity) message from {192.168.0.109:7759 73.175.189.204:7759} cannot be found in the request cache, skipping it
WARNING 1533702319.84 community:1895 (DiscoveryCommunity) drop a 945 byte packet invalid identifier [similarity-response] from {192.168.1.15:7759 83.23.207.230:7759}
WARNING 1533702319.84 community:1895 (DiscoveryCommunity) drop a 945 byte packet invalid identifier [similarity-response] from {192.168.1.15:7759 83.23.207.230:7759}
WARNING 1533702319.85 community:498 (SearchCommunity) message from {192.168.0.14:7759 190.24.27.221:7759} cannot be found in the request cache, skipping it
INFO 1533702319.86 dispersy:1152 (Dispersy) estimate someones WAN address is (‘47.185.113.106’, 7759) (WAN was (‘10.3.134.229’, 7759), LAN stays (‘10.3.134.229’, 7759))
WARNING 1533702320.03 community:1895 (DiscoveryCommunity) drop a 793 byte packet invalid identifier [similarity-response] from <Candidate 131.180.27.155:6423>
WARNING 1533702320.03 community:1895 (DiscoveryCommunity) drop a 793 byte packet invalid identifier [similarity-response] from <Candidate 131.180.27.155:6423>
INFO 1533702321.32 CreditMiningManager:296 (CreditMiningManager) 0 active download(s), 0 bytes uploaded
WARNING 1533702321.32 community:1895 (DiscoveryCommunity) drop a 989 byte packet invalid identifier [similarity-response] from {192.168.1.158:7759 108.39.116.148:7759}
WARNING 1533702321.32 community:1895 (DiscoveryCommunity) drop a 989 byte packet invalid identifier [similarity-response] from {192.168.1.158:7759 108.39.116.148:7759}
WARNING 1533702321.32 community:1895 (DiscoveryCommunity) drop a 33 byte packet invalid ping identifier [pong] from <Candidate 27.35.23.16:7759>
INFO 1533702322.76 community:389 (TriblerTunnelCommunity) Removing relay 102689521 Got destroy
INFO 1533702322.77 community:389 (TriblerTunnelCommunity) Removing relay 1320612392 Got destroy
INFO 1533702322.77 community:281 (PopularityCommunity) Content to publish: 0
ERROR 1533702322.77 community:288 (PopularityCommunity) Nothing to publish

It’s not an obscene amount of processing power, but most of the time it does not do this, and right now, it’s barely doing any work. Just a couple of completed downloads, barely any seeding action.


#19

Since yesterday, Tribler is broken again. It mentions that it is building circuits, but no circuits will be discovered. The terminal keeps repeating:

“Could not create circuit, no available exit nodes.”


#20

@LesVerres We made an update to our infrastructure and the code base. As a result, we changed the protocol for downloading. We understand this is inconvenient but we use these experimental releases to test our ideas and make (breaking) changes in order to improve stability and performance.

To make it work again, please download and install the latest development version of Tribler. You can download them from here: https://jenkins-ci.tribler.org/job/Build_Tribler_next/ (under latest successful artefacts).

Please let me know whether this fixes the issue for you :+1: