Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694494 - Tor Browser doesn't start up anymore.
Summary: Tor Browser doesn't start up anymore.
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: torbrowser-launcher
Version: 29
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-31 21:34 UTC by xzj8b3
Modified: 2020-01-15 17:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description xzj8b3 2019-03-31 21:34:42 UTC
Tor Browser doesn't start up anymore.

In case of update please allow the download of the Italian version if possible thanks!!



# torbrowser-launcher
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 29, in <module>
    import torbrowser_launcher
  File "/usr/lib/python2.7/site-packages/torbrowser_launcher/__init__.py", line 38, in <module>
    from .launcher import Launcher
  File "/usr/lib/python2.7/site-packages/torbrowser_launcher/launcher.py", line 36, in <module>
    import requests
ImportError: No module named requests

Comment 1 Gwyn Ciesla 2019-04-01 14:50:59 UTC
What version of this do you have? 0.3.1-3 and above should require python2-requests.

Comment 2 Fedora Admin XMLRPC Client 2019-12-18 17:01:59 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 3 Fedora Admin XMLRPC Client 2020-01-15 17:41:15 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.


Note You need to log in before you can comment on or make changes to this bug.