Opened 4 years ago

Last modified 12 days ago

#11245 new defect

Orbot bootstraped problem

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

Description

On my un rooted samsung galaxy note 10.1 Orbot only gets to bootstrapped 25%.

My system information:
Android version: 4.1.2
Model Number: GT - N8010

Log:

Orbot is starting…
Orbot is starting…
Tor binary exists: /data/data/org.torproject.android/lib/libtor.so
Privoxy binary exists: /data/data/org.torproject.android/lib/libprivoxy.so
Obfsproxy binary exists: /data/data/org.torproject.android/lib/libobfsproxy.so
Xtables binary exists: /data/data/org.torproject.android/lib/libxtables.so
link RM err=0 out:
link LN err=0 out:
libtor.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/lib/libtor.so
libtor.so: POST: Is binary exec? true
tor: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? true
libprivoxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/lib/libprivoxy.so
libprivoxy.so: POST: Is binary exec? true
libobfsproxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/lib/libobfsproxy.so
libobfsproxy.so: POST: Is binary exec? true
libxtables.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/lib/libxtables.so
libxtables.so: POST: Is binary exec? true
Orbot is starting…
got tor proc id: 21351
Tor process id=21351
Connecting to control port: 9051
SUCCESS connected to control port
SUCCESS authenticated to control port
Starting Tor client… complete.
adding control port event handler
SUCCESS added control port event handler
updating settings in Tor service
Starting privoxy process
/data/data/org.torproject.android/lib/libprivoxy.so /data/data/org.torproject.android/app_bin/privoxy.config &
orConnStatus (madiba): LAUNCHED
NOTICE: Bootstrapped 10%: Finishing handshake with directory server.
Privoxy is running on port:8118
Privoxy process id=21371

NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection.
orConnStatus (itpol2): CONNECTED

orConnStatus (madiba): CONNECTED

NOTICE: Bootstrapped 20%: Asking for networkstatus consensus.
Circuit (1) BUILT: itpol2

NOTICE: I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.

Circuit (2) BUILT: madiba

NOTICE: Bootstrapped 25%: Loading networkstatus consensus.

Circuit (2) CLOSED: madiba

NOTICE: I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.

Child Tickets

Change History (2)

comment:1 Changed 4 years ago by arma

Component: - Select a componentOrbot
Owner: set to n8fr8

(Unclear if this is actually an Orbot issue, or if the user is just censored or didn't have a network connection or something)

comment:2 Changed 12 days ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.