bug? coyim + tor browser

i’ve yet to test this outside of virtualbox. but, i’m wondering if it can be reproduced in any other hypervisor environment. at the moment, coyim and tor browser cannot be run at the same time. if coyim is already loaded, opening the tor browser results in either a lock up or tor browser simply cannot load anything. if tor browser is run first, coyim crashes out upon asking for a master password on boot up. i haven’t come across any talk about this elsewhere yet. can anyone else reproduce this?

All looks good here on KVM. So I’m going to give the patented asshole answer: Works for me™ Maybe you should switch :slight_smile:

1 Like

thanks a lot @HulaHoop. :stuck_out_tongue:

here’s a quick grab of some debugs from tor browser.

when coyim is NOT running:
1534093467700 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232} WARN Loading extension ‘{73a6fe31-595d-460b-a920-fcc0f8843232}’: Reading manifest: Error processing permissions.1: Unknown permission “privacy”

1534093467700 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232} WARN Loading extension ‘{73a6fe31-595d-460b-a920-fcc0f8843232}’: Reading manifest: Error processing permissions.4: Unknown permission “unlimitedStorage”

1534093467900 addons.webextension.https-everywhere-eff@eff.org WARN Loading extension ‘https-everywhere-eff@eff.org’: Reading manifest: Error processing devtools_page: An unexpected property was found in the WebExtension manifest.

1534093468000 addons.webextension.https-everywhere-eff@eff.org WARN Please specify whether you want browser_style or not in your browser_action options.
windows.onRemoved event fired after context unloaded.

when coyim IS running:
1534093343700 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232} WARN Loading extension ‘{73a6fe31-595d-460b-a920-fcc0f8843232}’: Reading manifest: Error processing permissions.1: Unknown permission “privacy”

1534093343700 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232} WARN Loading extension ‘{73a6fe31-595d-460b-a920-fcc0f8843232}’: Reading manifest: Error processing permissions.4: Unknown permission “unlimitedStorage”

1534093343900 addons.webextension.https-everywhere-eff@eff.org WARN Loading extension ‘https-everywhere-eff@eff.org’: Reading manifest: Error processing devtools_page: An unexpected property was found in the WebExtension manifest.

1534093344000 addons.webextension.https-everywhere-eff@eff.org WARN Please specify whether you want browser_style or not in your browser_action options.

[Parent 2375] WARNING: Failed to launch tab subprocess: file /var/tmp/build/firefox-df11f76d94e5/ipc/glue/GeckoChildProcessHost.cpp, line 627

[Parent 2375] WARNING: pipe error (42): Connection reset by peer: file /var/tmp/build/firefox-df11f76d94e5/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322

[Parent 2375] WARNING: Failed to launch tab subprocess: file /var/tmp/build/firefox-df11f76d94e5/ipc/glue/GeckoChildProcessHost.cpp, line 627

[Parent 2375] WARNING: pipe error (42): Connection reset by peer: file /var/tmp/build/firefox-df11f76d94e5/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322

[Parent 2375] WARNING: Failed to launch tab subprocess: file /var/tmp/build/firefox-df11f76d94e5/ipc/glue/GeckoChildProcessHost.cpp, line 627

[Parent 2375] WARNING: pipe error (42): Connection reset by peer: file /var/tmp/build/firefox-df11f76d94e5/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322

i couldn’t get it to crash again that time around. it’s sporadic. some times, after those errors, it crashes out with a seg fault. every time, however, it hangs completely unresponsive to any web requests.

Hm. Strange if true. I don’t how/if a standalone program like coyim could possibly touch or alter the Tor Borwser code base. I think this is a sign of a bug in TBB nothing to do directly with Coyim. Try comparing the debug output of TBB in a system without coyim installed and you will probably see an identical output, meaning there’s no useful info here?

Could you report any crash bugs upstream against TBB and/or coyim?

not yet, @Patrick. i wanted to see if anyone else was experiencing this with other hypervisors. it’s making very little sense to me at the moment. but, i need to explore it more.

did anyone else manage to replicate this in virtualbox?

on my machine, the fix was more basic and thus i overlooked it. i increased the ram for use by the whonix workstation from 1024 to 2048. now it works fine. if someone else replicates the issue in virtualbox, please let me know and i will include this as a step in my guide. otherwise, if it was specific to me, i’ll leave it alone.

1 Like

No such problem in Qubes with Whonix 14. I use CoyIM and TBB regularly together.

1 Like