Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #18502

Closed
Open
Created Mar 08, 2016 by Trac@tracbot

Orbot tries to kill Tor processes it doesn't own

Orbot fails to start when Briar is running because Orbot tries and fails to kill Briar's Tor process, leading to the following error in Orbot:

Waiting for control port...
Unable to start Tor: java.lang.Exception: Cannot kill: /data/data/org.torproject.android/app_bin/tor
Set background service to FOREGROUND
TorService is shutting down
An error occurred stopping Tor: Cannot kill: /data/data/org.torproject.android/app_bin/tor
Something bad happened. Check the log

It looks like TorService#killAllDaemons() is taking its name a bit too literally. If Orbot had been running as root it would have succeeded in killing Briar's Tor process.

Trac:
Username: akwizgran

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking