Opened 5 days ago

Last modified 3 days ago

#26126 new defect

Tor configuration did not verify: Error: -4 ERR= OUT=

Reported by: Winston Owned by: n8fr8
Priority: Medium Milestone:
Component: Applications/Orbot Version:
Severity: Blocker Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

After upgrading to 16.02-RC1 from F-Droid on a Nexus 5X with copperheados (android 8.1.0), Orbot is unable to start. Log says "Tor configuration did not verify: Error: -4 ERR= OUT=".

Orbot has all three requested permissions.
Clearing data and cahce did not change the behaviour.
Reinstalling from scratch didn't change the behaviour.

Child Tickets

Change History (3)

comment:1 Changed 5 days ago by Winston

F-Droid repo: Guardian Project Official Releases
Added on 17/05/2018 armeabi

Looking at what F-Droid reports as previous version, only the size and abi are different: 18.0 MiB and "armeabi armeabi-v7a x86" for the previous version and 9.1 MiB and "armeabi" for the newer.

comment:2 Changed 5 days ago by Winston

By forcing installation of the 18.0 MiB package (uninstalling and then clicking on that version explicitly) things started working again.

This might well be an issue with F-Droid. Hints on how to debug packaging vs. F-Droid issues welcome.

comment:3 Changed 3 days ago by pant

Same happend when I installed Orbot-16.0.2-RC-1-fullperm-armeabi-release.apk https://github.com/n8fr8/orbot/releases ...

Note: See TracTickets for help on using tickets.