Tor browser download error 404

I’m on Ubuntu 22.04, latest update. Installed the torbrowser-launcher from the official repo.

Doing this changes should make the torbrowser-launcher works as expected. But before you do, you must remove this directories ~/.cache/torbrowser, ~/.local/share/torbrowser, ~/.config/torbrowser as they save information for the launcher and the fix won’t work using those.

Be aware that if you have a working Tor Browser installation, you will lose your settings and working installations. Using this fix for the torbrowser-launcher doesn’t take into account existing installations, but gives an idea on why the launcher fails to download the current version.

First change this line on /usr/lib/python3/dist-packages/torbrowser_launcher/common.py on line 171, you will need root access to make changes to this file:

if hasattr(self, 'settings') and self.settings['force_en-US']:
    language = 'en-US'
else:
    #language = self.language
    language = "ALL"

Commented out the variable language and set it again with the value "ALL", that way the launcher will look for the correct signatures and tarballs files in the mirror.

Also made a change in line 277 of the same file, this time when setting up the variables to the install location, the launcher will refer to the language setting and set it as part of the directory installation, but the actual package downloaded by the launcher will refer to the directory as tor-browser and not by tor-browser_ALL as the launcher would expect it to do:

"tbb": {
    "changelog": tbb_local
    + "/tbb/"
    + self.architecture
    + "/tor-browser"
    #+ "/tor-browser_"
    #+ language
    + "/Browser/TorBrowser/Docs/ChangeLog.txt",
    "dir": tbb_local + "/tbb/" + self.architecture,
    "dir_tbb": tbb_local
    + "/tbb/"
    + self.architecture
    + "/tor-browser",
    #+ "/tor-browser_"
    #+ language,
    "start": tbb_local
    + "/tbb/"
    + self.architecture
    + "/tor-browser"
    #+ "/tor-browser_"
    #+ language
    + "/start-tor-browser.desktop",
},

Here there are three entries that must be changed. All of them refers to /tor-browser_ + language as part of the installation directory. It must be changed to /tor-browser and attention on the second entry as it must end with ,.

This fix is terrible, it doesn’t remove the language setting at all, just fixes it in order to make it work with what is available in the mirror. I guess we need to wait for the devs to make this fix on the repo package, by that time those changes will be rewritten and hopefully still works.

Hope this helps.

Как исправить ошибку Tor 404

Оценка «Tor 404 Error»

Как правило, практикующие ПК и сотрудники службы поддержки знают «Tor 404 Error» как форму «ошибки во время выполнения». Разработчики программного обеспечения, такие как SoftwareDeveloper, обычно работают через несколько этапов отладки, чтобы предотвратить и исправить ошибки, обнаруженные в конечном продукте до выпуска программного обеспечения для общественности. Поскольку разработчики программного обеспечения пытаются предотвратить это, некоторые незначительные ошибки, такие как ошибка 404, возможно, не были найдены на этом этапе.

Некоторые пользователи могут столкнуться с сообщением «Tor 404 Error» при использовании Tor. Сообщение об этой ошибке 404 позволит разработчикам обновить свое приложение и исправить любые ошибки, которые могут вызвать его. Затем Tor Project может исправить эти ошибки в исходном коде и подготовить обновление для загрузки. Поэтому, когда вы сталкиваетесь с запросом на обновление Tor, это обычно связано с тем, что это решение для исправления ошибки 404 и других ошибок.

Что вызывает ошибку времени выполнения 404?

Наиболее распространенные вхождения «Tor 404 Error» проблемы при загрузке Tor. Вот три наиболее распространенные причины, по которым происходят ошибки во время выполнения ошибки 404:

Ошибка 404 Crash — программа обнаружила ошибку 404 из-за указанной задачи и завершила работу программы. Эти ошибки обычно возникают, когда входы Tor не могут быть правильно обработаны, или они смущены тем, что должно быть выведено.

«Tor 404 Error» Утечка памяти — Ошибка 404 утечка памяти происходит и предоставляет Tor в качестве виновника, перетаскивая производительность вашего ПК. Это может быть вызвано неправильной конфигурацией программного обеспечения Tor Project или когда одна команда запускает цикл, который не может быть завершен.

Ошибка 404 Logic Error — логическая ошибка возникает, когда компьютер производит неправильный вывод, даже если вход правильный. Он материализуется, когда исходный код Tor Project ошибочен из-за неисправного дизайна.

В большинстве случаев проблемы с файлами Tor 404 Error связаны с отсутствием или повреждением файла связанного Tor вредоносным ПО или вирусом. Для устранения неполадок, связанных с файлом Tor Project, большинство профессионалов ПК заменят файл на соответствующую версию. Запуск сканирования реестра после замены файла, из-за которого возникает проблема, позволит очистить все недействительные файлы Tor 404 Error, расширения файлов или другие ссылки на файлы, которые могли быть повреждены в результате заражения вредоносным ПО.

Типичные ошибки Tor 404 Error

Эти проблемы Tor, связанные с Tor 404 Error, включают в себя:

• «Ошибка программы Tor 404 Error. «
• «Недопустимая программа Win32: Tor 404 Error»
• «Tor 404 Error должен быть закрыт. «
• «Не удается найти Tor 404 Error»
• «Tor 404 Error не найден.»
• «Проблема при запуске приложения: Tor 404 Error. «
• «Файл Tor 404 Error не запущен.»
• «Ошибка Tor 404 Error. «
• «Ошибка пути программного обеспечения: Tor 404 Error. «

Эти сообщения об ошибках Tor Project могут появляться во время установки программы, в то время как программа, связанная с Tor 404 Error (например, Tor) работает, во время запуска или завершения работы Windows, или даже во время установки операционной системы Windows. Выделение при возникновении ошибок Tor 404 Error имеет первостепенное значение для поиска причины проблем Tor и сообщения о них вTor Project за помощью.

Истоки проблем Tor 404 Error

Заражение вредоносными программами, недопустимые записи реестра Tor или отсутствующие или поврежденные файлы Tor 404 Error могут создать эти ошибки Tor 404 Error.

Особенно ошибки Tor 404 Error проистекают из:

• Недопустимые разделы реестра Tor 404 Error/повреждены.
• Вредоносные программы заразили Tor 404 Error, создавая повреждение.
• Tor 404 Error ошибочно удален или злонамеренно программным обеспечением, не связанным с приложением Tor.
• Tor 404 Error конфликтует с другой программой (общим файлом).
• Неполный или поврежденный Tor (Tor 404 Error) из загрузки или установки.

Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11

Источник

How to fix the Runtime Code 404 Tor 404 Error

This article features error number Code 404, commonly known as Tor 404 Error described as Error 404: Tor has encountered a problem and needs to close. We are sorry for the inconvenience.

Error Information

Error name: Tor 404 Error
Error number: Code 404
Description: Error 404: Tor has encountered a problem and needs to close. We are sorry for the inconvenience.
Software: Tor
Developer: Tor Project

This repair tool can fix common computer errors like BSODs, system freezes and crashes. It can replace missing operating system files and DLLs, remove malware and fix the damage caused by it, as well as optimize your PC for maximum performance.

About Runtime Code 404

Runtime Code 404 happens when Tor fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.

Definitions (Beta)

Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!

• Tor — Tor is a free open-source application used for internet anonymity and anti-censorship.
• 404 — The HTTP status code 404 or «Not Found» indicates the server could not find the requested file or resource.

Symptoms of Code 404 — Tor 404 Error

Runtime errors happen without warning. The error message can come up the screen anytime Tor is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(Tor 404 Error) Repair Tool»/>
(For illustrative purposes only)

Causes of Tor 404 Error — Code 404

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Источник

tor-browser-bundle-bin: download error #108954

Describe the bug
The download for tor-browser-bundle-bin fails with a 404 error.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
Tor installs

Additional context

Metadata
Please run nix-shell -p nix-info —run «nix-info -m» and paste the result.

• system: «x86_64-linux»
• host os: Linux 5.4.87, NixOS, 21.03.20210107.f211631 (Okapi)
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.4pre20201205_a5d85d0
• channels(root): «nixos-21.03pre257339.83cbad92d73»
• channels(pinpox): «home-manager»
• nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

The text was updated successfully, but these errors were encountered:

Can you update your channel please? 83cbad9 is 5 weeks old and as a result, TBB 10.0.5 is out-of-date. This should be fixed in e924c5d.

Likely duplicate of #107141.

Huh, that’s strange. I just did:

Is that not enought to update a flake-enabled system config?

@pinpox are you using nixflk?

EDIT: nvm, I found your https://github.com/pinpox/nixos. If you don’t mind we can go discuss the out-of-date channel thing there, and keep this thread about whether there’s something wrong with tor-browser-bundle-bin. (most likely not but we’ll confirm)

can you try nix shell nixpkgs#tor-browser-bundle-bin real quick? I’ll help you out with the legacy commands right after.

@lourkeur Sorry, I just ran:

and now it builds fine with nix-shell -p pkgs.tor-browser-bundle-bin . But I’m a quite confused, I thought updating channels was nothing I should be doing at all with flakes?

nix shell nixpkgs#tor-browser-bundle-bin also works, btw.

and now it builds fine with nix shell nixpkgs#tor-browser-bundle-bin . But I’m a quite confused, I thought updating channels was nothing I should be doing at all with flakes?

The general advice is more along the line of not mixing flakes and channels if possible. In your case what happens is your $NIX_PATH probably contains a reference to /nix/var/nix/profiles/per-user/root/channels/nixos , which is an out-of-date channel (installed by default because flakes are still experimental). What I do and what you might want to do is nuke root’s channels, and set nix.nixPath = [ «nixpkgs=$» ] to keep hyphenated commands up-to-date and happy during the transition period. (example)

@lourkeur Huge thanks, that works. For reference in case anyone finds this:

I removed the nixos channel for root and for my user

Then added to the configuration of all my machines

After rebuilding the configuration (or deploying) I had to logout and in again for $NIX_PATH to be set. It is now

for my user: /home/pinpox/.nix-defexpr/channels:nixpkgs=/nix/store/02bj12ja21vibib3c1k065568x1d17ds-source
for root: /root/.nix-defexpr/channels:nixpkgs=/nix/store/02bj12ja21vibib3c1k065568x1d17ds-source

and I can run commands like nix-shell -p pkgs.tor-browser-bundle-bin without problems on both accounts. The only issue I still have, is that after rebuilding/rebooting the nixos channel seems to «reappear» in nix-channel —list . Does it get added automatically?

@lourkeur Huge thanks, that works. For reference in case anyone finds this:

I removed the nixos channel for root and for my user

Then added to the configuration of all my machines

After rebuilding the configuration (or deploying) I had to logout and in again for $NIX_PATH to be set. It is now

for my user: /home/pinpox/.nix-defexpr/channels:nixpkgs=/nix/store/02bj12ja21vibib3c1k065568x1d17ds-source
for root: /root/.nix-defexpr/channels:nixpkgs=/nix/store/02bj12ja21vibib3c1k065568x1d17ds-source

and I can run commands like nix-shell -p pkgs.tor-browser-bundle-bin without problems on both accounts. The only issue I still have, is that after rebuilding/rebooting the nixos channel seems to «reappear» in nix-channel —list . Does it get added automatically?

Good point, it does it on my machines too and comes from here. Eh. Just ignore it, it’ll get fixed eventually.

Источник

sos: 404 download error #663

hi, I try TOR on Kali Linux and Parrot OS but said: error 404
I try on terminal command sudo … same error. any suggest.
many thanks and a hug for all best community

The text was updated successfully, but these errors were encountered:

FOR THE NEW INSTALLATION (not an update)
basically, follow this
build from source
however, you just have to change the first command here to
git clone https://github.com/tensornova/torbrowser-launcher.git

tell me if there is an error related to ‘float’ when you follow this.

FOR THE NEW INSTALLATION (not an update)
then
(1) delete a directory torbrowser-launcher you downloaded before via git clone https://github.com/tensornova/torbrowser-launcher.git

(2) follow build from source
but try git clone -b hotfix —single-branch https://github.com/tensornova/torbrowser-launcher.git
instead of the first command

hi, sorry for the long wait i was asleep

the software starts, but its stuck at 0% at downloading signatures

Edit: nvm it works, thanks

EDIT 2: it deleted all of my data! 🙁

Hi,
I have the same problem, do you know a way to make it work with flatpak?
Do I just need to wait for the flatpak to be updated?
Thanks you

Hi, I have the same problem, do you know a way to make it work with flatpak? Do I just need to wait for the flatpak to be updated? Thanks you

That’s exact. First we need to have it being merged via #661, and then, that a new build is pushed to flatpak.

then (1) if you’ve already installed it, please uninstall it or delete a directory torbrowser-launcher you downloaded before

(2) follow build from source but try git clone -b hotfix —single-branch https://github.com/tensornova/torbrowser-launcher.git instead of the first command

Hey none of this worked for me at all. Take a look. I’m on Ubuntu 22.04. When will TOR be fixed?

I am also getting the «Download Error: 404»

When is this going to get fixed?

hi, sorry for the long wait i was asleep

the software starts, but its stuck at 0% at downloading signatures

Edit: nvm it works, thanks

EDIT 2: it deleted all of my data! 🙁

um, sorry, I didnt considering update that is not a new installation. It’s a guess, but it seems that the data has been deleted because a path to the data has changed even though the data exists. I’ll check it out and let you know if I can. and i recommend a downgrade if you are able to do it

Issue #628
then (1) if you’ve already installed it, please uninstall it or delete a directory torbrowser-launcher you downloaded before
(2) follow build from source but try git clone -b hotfix —single-branch https://github.com/tensornova/torbrowser-launcher.git instead of the first command

Hey none of this worked for me at all. Take a look. I’m on Ubuntu 22.04. When will TOR be fixed?

not sudo apt install git clone but sudo apt install git

um, sorry, I didnt considering update that is not a new installation. It’s a guess, but it seems that the data has been deleted because a path to the data has changed even though the data exists. I’ll check it out and let you know if I can. and i recommend a downgrade if you are able to do it

thats reassuring, BTW what was the old location of the browser profile, maybe I can recover it manually?

I failed with torbrowser-launcher from Debian Stable too.
I think an update should be released through OS distributions.

it will slowly happen, just wait for it slowly

also Debian Stable will take a pretty long time to upate torbrowser-laucher so i think the bestthing to do rn is to install it maually

This is no solution, but info towards one.

Tor seems tor has moved to a universal language package in 12.0.1.

So the launcher should not use the language to composite the download path, instead it should use «ALL».

open the /usr/lib/python3/dist-packages/torbrowser_launcher/common.py file

Change the discover_arch_lang function to simply set self.language to «ALL», i.e. delete all the complicated language guessing code that is there and replace it with one line (I also show the comment of the next function, so it becomes clear how far it has to be replaced):

Now it downloads alright and tries to install . where it hangs.

Some sort of unfulfilled promise or whatever the contraption is called in Python.

So back to square one.

Okay, I’ve done this step as a workaround for an installation:

After this, on launching torbrowser-launcher it downloads successfully application’s package, but it breaks with:

Then, to complete workaround at user profile this must be run in a terminal:

And it just works.
All this expecting torbrowser-launcher incorporates new fixes.

Watching this issue also (flatpak install didn’t work for me either — flathub not recognized or something like that)

when using flatpak i get this error:

qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin «xcb» in «» even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

i tried to use source and debian repository but i got error 404. also when i try tensornova’s solution it requires my github username and password and then says that password authentication has been ended since august 2021.

also when i try tensornova’s solution it requires my github username and password and then says that password authentication has been ended since august 2021.

You have to generate a token and use that as your password. Either way, when you do that you are (or I was) notified that the repository doesn’t exist

i tried to use source and debian repository but i got error 404. also when i try tensornova’s solution it requires my github username and password and then says that password authentication has been ended since august 2021.

My workaround also works with Debian packaging source (first part to common.py , next part to postinst & skel)

Nevertheless to say I have the same issue. Commenting just for the record:
OS: Kali Linux (latest upgrade)
Downloaded: by using official kali’s repo sudo apt install torbrowser-launcher .

I hope they will make a fix soon

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

How to fix the Runtime Code 404 Tor 404 Error

Symptoms of Code 404 — Tor 404 Error

Runtime errors happen without warning. The error message can come up the screen anytime Tor is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(For illustrative purposes only)

Causes of Tor 404 Error — Code 404

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.

	Error Number:	Error 404
Error Name:	Tor 404 Error
Error Description:	Error 404: Tor has encountered a problem and needs to close. We are sorry for the inconvenience.
Developer:	Tor Project
Software:	Tor
Applies to:	Windows XP, Vista, 7, 8, 10, 11

Tor 404 Error Assessment

Usually, PC practitioners and support staff know Tor 404 Error as a form of «runtime error». Software developers like SoftwareDeveloper typically work through several stages of debugging to prevent and fix bugs found in the final product before the software is released to the public. As much as software developers attempt to prevent it, some minor errors such as error 404 might not have been found during this phase.

Some users might experience the message «Tor 404 Error» while using Tor. Reporting this error 404 will allow developers to update their application and rectify any faults that could be causing it. Tor Project can then fix these errors in the source code and prepare an update for download. Therefore, when you encounter a prompt for a Tor update, it is usually because it’s a solution for fixing error 404 and other bugs.

What Produces Runtime Error 404?

The most common occurrences Tor 404 Error problems is when loading up Tor. Here’s the three most common causes why error 404 runtime errors happen:

Error 404 Crash — The program encountered an error 404 error because of a specified task, and terminated the program. These errors typically occur when Tor inputs can’t be correctly processed, or it’s confused by what is supposed to be output.

Tor 404 Error Memory Leak — Error 404 memory leak occurs and exposes Tor as a culprit, dragging down your PC performance. It may be triggered by the misconfiguration of the software by Tor Project, or when one command starts a loop which can’t be ended.

Error 404 Logic Error — A logical error occurs when the computer produces the wrong output, even if the input is right. It materializes when Tor Project’s source code is flawed due to faulty design.

In most cases, Tor 404 Error file problems are due to the Tor-related file missing or being corrupted by malware or virus. As a first troubleshootiong step, most PC professionals will attempt to replace the applicable version of the Tor Project file. After the problem file is replaced, running a registry scan can help clean up any invalid Tor 404 Error, file extension, or other file path references which could have been affected from a previous malware infection.

Typical Tor 404 Error Errors

These Tor 404 Error-related Tor Troubles Include:

• «Tor 404 Error Program Error.»
• «Invalid Win32 Program: Tor 404 Error»
• «Tor 404 Error needs to close.»
• «Can’t locate Tor 404 Error»
• «Tor 404 Error not found.»
• «Problem starting application: Tor 404 Error.»
• «Tor 404 Error is not running.»
• «Tor 404 Error failure.»
• «Software Path Fault: Tor 404 Error.»

These Tor Project error messages can appear during program installation, while a Tor 404 Error-related software program (eg. Tor) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Notating when Tor 404 Error errors occur is paramount in finding the cause of the Tor problems and reporting them to Tor Project for help.

Origins of Tor 404 Error Troubles

Malware infestation, invalid Tor registry entries, or missing / corrupt Tor 404 Error files can create these Tor 404 Error errors.

Especially, Tor 404 Error errors stem from:

• Tor 404 Error registry keys invalid / corrupted.
• Malware has infected Tor 404 Error, creating corruption.
• Tor 404 Error mistakenly deleted or maliciously by software unrelated to the Tor application.
• Tor 404 Error is in conflict with another program (shared file).
• Incomplete or corrupt Tor (Tor 404 Error) from download or installation.

Product by Solvusoft

Download Now
WinThruster 2022 — Scan your PC for computer errors.

Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000

Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall

Reported by: Cyril Brulebois <kibi@debian.org>

Date: Thu, 5 Nov 2015 20:45:06 UTC

Severity: grave

Tags: fixed-upstream

Found in version torbrowser-launcher/0.1.9-1+deb8u1

Fixed in versions torbrowser-launcher/0.2.1-1, torbrowser-launcher/0.1.9-1+deb8u2

Done: Holger Levsen <holger@debian.org>

Bug is archived. No further changes may be made.

Report forwarded
to debian-bugs-dist@lists.debian.org, kibi@debian.org, intrigeri@boum.org, Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Thu, 05 Nov 2015 20:45:10 GMT) (full text, mbox, link).

Acknowledgement sent
to Cyril Brulebois <kibi@debian.org>:
New Bug report received and forwarded. Copy sent to kibi@debian.org, intrigeri@boum.org, Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>.
(Thu, 05 Nov 2015 20:45:10 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Fri, 06 Nov 2015 04:45:03 GMT) (full text, mbox, link).

Acknowledgement sent
to Jason Hernandez <jason@jasonhernandez.ch>:
Extra info received and forwarded to list. Copy sent to Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>.
(Fri, 06 Nov 2015 04:45:03 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Fri, 06 Nov 2015 07:51:04 GMT) (full text, mbox, link).

Acknowledgement sent
to Jason Hernandez <jason@jasonhernandez.ch>:
Extra info received and forwarded to list. Copy sent to Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>.
(Fri, 06 Nov 2015 07:51:04 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Fri, 06 Nov 2015 10:09:06 GMT) (full text, mbox, link).

Acknowledgement sent
to intrigeri <intrigeri@debian.org>:
Extra info received and forwarded to list. Copy sent to Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>.
(Fri, 06 Nov 2015 10:09:06 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Fri, 06 Nov 2015 11:15:09 GMT) (full text, mbox, link).

Acknowledgement sent
to Nicolas Vigier <boklm@mars-attacks.org>:
Extra info received and forwarded to list. Copy sent to Anonymity Tools Debian Maintainers <pkg-anonymity-tools@lists.alioth.debian.org>.
(Fri, 06 Nov 2015 11:15:09 GMT) (full text, mbox, link).

Added tag(s) fixed-upstream.
Request was from intrigeri <intrigeri@debian.org>
to control@bugs.debian.org.
(Fri, 06 Nov 2015 11:45:06 GMT) (full text, mbox, link).

Reply sent
to Holger Levsen <holger@debian.org>:
You have taken responsibility.
(Fri, 13 Nov 2015 18:21:11 GMT) (full text, mbox, link).

Notification sent
to Cyril Brulebois <kibi@debian.org>:
Bug acknowledged by developer.
(Fri, 13 Nov 2015 18:21:11 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, destirisereg@gmail.com, Debian Privacy Tools Maintainers <pkg-privacy-maintainers@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Tue, 29 Dec 2015 13:45:07 GMT) (full text, mbox, link).

Acknowledgement sent
to 24t350c254t0hc <destirisereg@gmail.com>:
Extra info received and forwarded to list. Copy sent to destirisereg@gmail.com, Debian Privacy Tools Maintainers <pkg-privacy-maintainers@lists.alioth.debian.org>.
(Tue, 29 Dec 2015 13:45:07 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Privacy Tools Maintainers <pkg-privacy-maintainers@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Tue, 29 Dec 2015 17:45:08 GMT) (full text, mbox, link).

Acknowledgement sent
to "georg@riseup.net" <georg@riseup.net>:
Extra info received and forwarded to list. Copy sent to Debian Privacy Tools Maintainers <pkg-privacy-maintainers@lists.alioth.debian.org>.
(Tue, 29 Dec 2015 17:45:08 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Privacy Tools Maintainers <pkg-privacy-maintainers@lists.alioth.debian.org>:
Bug#804184; Package torbrowser-launcher.
(Wed, 30 Dec 2015 13:48:04 GMT) (full text, mbox, link).

Acknowledgement sent
to Holger Levsen <holger@layer-acht.org>:
Extra info received and forwarded to list. Copy sent to Debian Privacy Tools Maintainers <pkg-privacy-maintainers@lists.alioth.debian.org>.
(Wed, 30 Dec 2015 13:48:04 GMT) (full text, mbox, link).

Reply sent
to Holger Levsen <holger@debian.org>:
You have taken responsibility.
(Sat, 16 Jan 2016 21:51:14 GMT) (full text, mbox, link).

Notification sent
to Cyril Brulebois <kibi@debian.org>:
Bug acknowledged by developer.
(Sat, 16 Jan 2016 21:51:14 GMT) (full text, mbox, link).

Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Sun, 14 Feb 2016 07:35:59 GMT) (full text, mbox, link).