Issue with Cwtch & Tor After Restart in Qubes OS #230

新增問題

sarah · 2019-10-28T18:04:28Z

sarah 已留言

2019-10-28 18:04:28 +00:00

擁有者

From Alpha Testing Group:

When I open up Cwtch and have shut it down, I will then be unable to open it up again unless I've deleted 'tor' folder in '.cwtch'. After that, it will be able to work again. I don't if it relates to how the environment is setup in QubesOS VM's but that's an issue I just came across.

From Alpha Testing Group: When I open up Cwtch and have shut it down, I will then be unable to open it up again unless I've deleted 'tor' folder in '.cwtch'. After that, it will be able to work again. I don't if it relates to how the environment is setup in QubesOS VM's but that's an issue I just came across.

sarah 加入了

bug

標籤 2019-10-28 18:04:28 +00:00

dan 已留言

2019-10-30 17:39:01 +00:00

擁有者

further report on request for console logs

"I get this error, if I delete tor folder as stated before, Cwtch will work again."

2019/10/30 16:55:08 connectivity/torProvider.go [INFO] tor version: 0.3.5.8
Oct 30 16:55:08.000 [warn] It looks like another Tor process is running with the same data directory.  Waiting 5 seconds to see if it goes away.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x797c6e]

Oct 30 16:55:13.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.3.5.8 )
Oct 30 16:55:13.000 [err] Reading config failed--see warnings above.

further report on request for console logs "I get this error, if I delete tor folder as stated before, Cwtch will work again." ``` 2019/10/30 16:55:08 connectivity/torProvider.go [INFO] tor version: 0.3.5.8 Oct 30 16:55:08.000 [warn] It looks like another Tor process is running with the same data directory. Waiting 5 seconds to see if it goes away. panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x797c6e] Oct 30 16:55:13.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.3.5.8 ) Oct 30 16:55:13.000 [err] Reading config failed--see warnings above. ```

sarah 已留言

2020-10-22 01:02:34 +00:00

作者

擁有者

I am going to assume that this has been fixed given all the new connectivity / tor improvements - at least on Windows/Linux

If anyone on the most recent alpha is seeing tor issues, please opeen another ticket

I am going to assume that this has been fixed given all the new connectivity / tor improvements - at least on Windows/Linux If anyone on the most recent alpha is seeing tor issues, please opeen another ticket

sarah 關閉了這個問題

2020-10-22 01:02:34 +00:00

此存儲庫已封存，您不能在問題上留言。