Opened 4 years ago

Closed 9 months ago

#18502 closed defect (fixed)

Orbot tries to kill Tor processes it doesn't own

Reported by: akwizgran Owned by: n8fr8
Priority: Medium Milestone:
Component: Applications/Orbot Version:
Severity: Normal Keywords: orbot kill briar
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


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/
Set background service to FOREGROUND
TorService is shutting down
An error occurred stopping Tor: Cannot kill: /data/data/
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.

Child Tickets

Change History (6)

comment:1 Changed 4 years ago by n8fr8

Status: newassigned

Looking into it

comment:2 Changed 4 years ago by n8fr8

Right. Even though we start with the full path:


at some point, we reduce it down to just "/tor" or "tor"

Will look at not doing that.

comment:3 Changed 4 years ago by n8fr8

This should help:

Needs more testing, but hopefully we can get it into the next build.

comment:4 Changed 4 years ago by bugzilla

Killer feature :)))

comment:5 Changed 9 months ago by eighthave

Switching tor daemon to a shared library loaded in TorService will make killing the daemon entirely unnecessary.

comment:6 Changed 9 months ago by eighthave

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.