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

Open
opened 1 month ago by sarah · 1 comments
sarah commented 1 month ago

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 added the
bug
label 1 month ago
dan commented 1 month ago
Owner

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. ```
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.