Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • 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
  • #1286
Closed
Open
Created Mar 07, 2010 by Sebastian Hahn@sebastian

Entering invalid config info makes Orbot go into infinite loop

When Tor dies due to a config error, orbot tries to start it repeatedly. It doesn't realize that Tor will never start, and it'll just spam the log with "starting Tor. waiting" messages.

This loop is not interrupted by clicking the symbol again, even though the symbol goes grey. Orbot keeps trying to start Tor and spamming the log.

The only way to get out of this mess seems to be force-stopping the orbot application or killing the service.

[Automatically added by flyspray2trac: Operating System: All]

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