It is written in Python and used the cross-platform widget toolkit wxPython which made it possible to support a wide range of platforms and operating systems. The first public version of TorChat was released in November 2007 by Bernd Kreuss (prof7bit). Since onion services can receive incoming connections even if they are behind a router doing network address translation (NAT), TorChat does not need any port forwarding to work. ![]() TorChat clients communicate with each other by using Tor to contact the other's onion service (derived from their ID) and exchanging status information, chat messages and other data over this connection. This ID will be randomly created by Tor when the client is started the first time, it is basically the. WARNING: If you have 32bit qTox installed, do not install the new repository! It contains a 32bit qtox package with higher version number than the last one available, so apt-get upgrade will install it and replace your current qTox installation with that one, as soon as you run updates.In TorChat every user has a unique alphanumeric ID consisting of 16 characters. Unfortunately, the new repository does only contain 64bit builds of qTox yet, so I will have to live with that package being hold back for a while, until they also compile it for 32bit machines! I executed those lines and now all problems with apt-get update are gone! Sudo sh -c 'echo "deb nightly main" > /etc/apt//tox.list'Įcho "Tox Repository Installed. On their new wiki, they gave the following (slightly modified) script to install the actualized repository: #!/bin/bash That's why the old URL is not alive any more and why apt-get update is timing out. I checked their main page and found out, that the whole infrastructure including repositories, wiki and main site moved to a different domain. So what can be the problem with that repository and how may I fix it?Īfter having waited for the command to complete for hours, I saw that it hangs on all tox repositories. They have been ignored, or old ones used instead.Īfter this, the process terminates correctly without having to interrupt it. W: Failed to fetch Connection timed out after 120000 millisecondsĮ: Some index files failed to download. Here what appears after loooong times of waiting between each line: Ign nightly InReleaseĬonnection timed out after 120000 milliseconds UPDATEĪfter letting it run for hours, it actually finishes! The repositories that cause the problem are various lines. PS: The full output of apt-get update recorded with script that also shows those dynamic lines may be found on pastebin. What might be the problem here and how can I fix it? It just does not finish the apt-get update task…Ī reinstall of apt with sudo aptitude reinstall apt and a reboot afterwards did not change my situation either. However, it seems to have successfully updated the package index files after running sudo apt-get update and interrupting it when it gets stuck, as I still can run apt-get upgrade and receive new updates, or apt-get install. When I do sudo aptitude update instead, it also hangs at the same position.Īfter deleting the cache with sudo rm -rf /var/lib/apt/lists and running sudo apt-get update again, I still get the same results. Then it gets stuck and won't continue until I interrupt it with Ctrl+ C. ![]() Hit vivid-proposed/universe Translation-de Hit vivid-proposed/universe Translation-en When I run sudo apt-get update on Ubuntu 15.04, I get the following (shortened) output: $ LANG=C sudo apt-get update
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |