OperaTor 2.6 checks to see if Tor is running before it will start up, and it will refuse to start if ANY Tor instance is running, even if the Tor instance is not related to OperaTor in any way. For example, I cannot run TorChat at the same time as OperaTor 2.6 because OperaTor will detect the bundled Tor instance that TorChat has started, and then OperaTor will refuse to run.
I may possibly be able to start OperaTor first, and start TorChat second, which might prevent OperaTor from detecting TorChat Tor and refusing to start.
TorChat uses nonstandard ports with it's bundled Tor instance, and so it should never cause a problem with OperaTor. To fix this, OperaTor needs to only detect Tor instances that may cause problems for OperaTor. If OperaTor's bundled Tor instance used it's own non-standard ports, then when starting up, OperaTor can check to see if any of the running Tor instances respond to OperaTor's signalling on it's special Tor ports. If none of the running Tor instances respond, then OperaTor can assume they are not going to cause a problem if OperaTor starts up it's own instance of Tor.
English
Polski