Not all reported bugs are fixed yet but we had issues with the logging system and that made it hard to collect information about some of the bugs.
The most important fixes are for the logging system, the crypto lib issues for the tunnel community and some unicode path issues.
If this build still gives you trouble, please update your bug reports with a new log file.
Get RC4 here!
Regarding your comment in the older thread whirm ("> The next RC may work on XP as a side effect for some other fixes in case you want to try it."), I tried Tribler_6.5.0-rc4.exe with the exact same behaviour, unfortunately…
still stucked at “building circuits” if annom is chosen. But i untick annom by proxies…i am able to start the download.
to anyone,please check your download here…the site can identify torrent’s name and IP address.
http://ipmagnet.services.cbcdn.com/?hash=00f6077ddf09e72336f6ba07f0671c90f2f846fb#
I would try with “dependency walker” and see if you are missing any dll.
Here is tribler.exe.log file if developers finds something to fix (RC4 working fine for me)
ERROR 1441025489.41 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025489.41 dispersy:238 Unable to find our public interface!
ERROR 1441025490.93 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025490.93 dispersy:238 Unable to find our public interface!
ERROR 1441025502.69 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025502.69 dispersy:238 Unable to find our public interface!
ERROR 1441025506.70 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025506.70 dispersy:238 Unable to find our public interface!
ERROR 1441025550.83 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025550.83 dispersy:238 Unable to find our public interface!
ERROR 1441025605.84 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025605.84 dispersy:238 Unable to find our public interface!
ERROR 1441025834.37 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025834.37 dispersy:238 Unable to find our public interface!
ERROR 1441025970.67 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441025970.67 dispersy:238 Unable to find our public interface!
ERROR 1441026007.02 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441026007.02 dispersy:238 Unable to find our public interface!
ERROR 1441026045.98 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441026045.98 dispersy:238 Unable to find our public interface!
ERROR 1441026055.68 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441026055.68 dispersy:238 Unable to find our public interface!
ERROR 1441026115.80 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441026115.80 dispersy:238 Unable to find our public interface!
ERROR 1441026115.99 dispersy:214 failed to check network interfaces.
Traceback (most recent call last):
File “Tribler\dispersy\dispersy.pyo”, line 195, in _get_interface_addresses
OSError: Unable to obtain adapter information.
ERROR 1441026115.99 dispersy:238 Unable to find our public interface!
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File “atexit.pyo”, line 24, in _run_exitfuncs
UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\xf6’ in position 34: ordinal not in range(128)
Error in sys.exitfunc:
Traceback (most recent call last):
File “atexit.pyo”, line 24, in _run_exitfuncs
UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\xf6’ in position 34: ordinal not in range(128)
Thanks, we will have a look at this unicode error.
Thank you whirm for the hint; this is what Dependency Walker v2.2 indicates as missing files:
API-MS-WIN-DOWNLEVEL-ADVAPI32-L1-1-0.DLL
API-MS-WIN-DOWNLEVEL-OLE32-L1-1-0.DLL
API-MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL
API-MS-WIN-SECURITY-SDDL-L1-1-0.DLL
CRYPTSP.DLL
EFSADU.DLL
EFSUTIL.DLL
IESHIMS.DLL
SSPICLI.DLL
WER.DLL
WERUI.DLL
…so, it has to do with the Windows version I am running being unsupported, I guess.
Oh well…
I would google for the DLL names and see what do you need to install.
After installing every missing DLL that Dependency Walker complains about, I run a profiling session for “tribler.exe” and these are the last four lines from the log file:
DllMain(0x78520000, DLL_PROCESS_ATTACH, 0x0012FD30) in “MSVCR90.DLL” returned 0 (0x0) by thread 1.
First chance exception 0xC0000142 (DLL Initialization Failed) occurred in “NTDLL.DLL” at address 0x7C9673BE by thread 1.
Second chance exception 0xC0000142 (DLL Initialization Failed) occurred in “NTDLL.DLL” at address 0x7C9673BE by thread 1.
Exited “TRIBLER.EXE” (process 0x604) with code -1073741502 (0xC0000142) by thread 1.
Tribler cannot download IF Peerblock is active…any fix?
No idea about that one, sorry 
I assume peerblock works as a blacklisting firewall, i would check its logs and see what’s being blocked by it.
a temporary fix for the problem:
Start tribler 1st…wait till the downloading process has started first.
Then u can enable/start the peerblock.
67.215.246.10:6881 and 216.144.236.234:5353 = Secured Private Network
Are these related to Tribler? if so,i’d like to add it into allow list in Peerblock.
I don’t recognize this IP. Is Tribler trying to talk to it? Which port? Maybe for DHT?
My PC/Tribler (192.168.1.2:7760) to 67.215.246.10:6881. And have u got the cure to allow tribler to start building the circuit while using peerblock?
6881 is bittorrent traffic, so that’s probably a peer behind a VPN.
I don’t use peerblock (nor windows) so I don’t know what it is doing to break Tribler. As I said: What I would do is to check peerblock’s log to see what’s blocking from Tribler and decide if you want to add it to the whitelist.
Image of Peerblock
how do u want me to upload the log?
Here’s the log…
The good thing about tribler is…it does not allow the User’s IP and its torrent client’s name to leak out. It only not able to weed out the anti P2p.
The log file doesn’t seem to contain any traffic related data.
Just start Tribler and see what gets blocked (which is not bittorrent) on Peerblock.
