Power off the virtual machine. Go to VirtualBox -> Machine -> Settings -> Shared Folder -> choose a folder -> use folder name shared. Choose mount automatically and create permanently. Press OK.
then see if that error goes away. It’s not very serious. It’s just a service to help automate the rest of the instructions.
yeah i know it is not big issue. but u know , it looks like one for the new users when they c red failure.( oh nooo i got hacked , or whonix contains backdoors and the vbox showed it lol.)
No idea. Does this happen once or often? Does it happen with Debian jessie [KDE] VMs also?
just happened once. debian i dont have it now. the old pc with debian = the motherboard made his way to heavens. thought about the qubes-debian is a good solution but it turns out that i cant download any VM because of the kernel issues.
i just got the same issue. further more the GW didnt understand this error, and showed up in the right top corner of the screen “connected to Tor”. whereas in fact there is no internet connection or crashing one.
Note:- happened even before with non-whonix templates. i dont think it is specifically related to whonix.
oh ok. im little bit confused tho. should i put the testing phase issues related to whonix here (as mentioned in phabricator , that this is the place of discussion). or in the similar issues topics which they contain the same errors even if they r from whonix 9 or 10 or 11 ? or open new topic saying this is for whonix xx testers repository issue or enhancement material?
oh ok. im little bit confused tho. should i put the testing phase
issues related to whonix here (as mentioned in phabricator , that
this is the place of discussion). or in the similar issues topics
which they contain the same errors even if they r from whonix 9 or
10 or 11 ? or open new topic saying this is for whonix xx testers
repository issue or enhancement material?
That’s difficult indeed. The overall goal is to keep the time for
searching, reading and typing for everyone as low as possible. Less is
There are various old, known issues. Such as the Error starting VM: operation failed: device matching mac address 00:16:3e:5e:6c:0d already exist (
If they’re unspecific to Whonix and not of much concern, then there is
no need to repeat them here. There are so many bugs inherited from
Debian, and Qubes, if we’d mirror them all here, we get flood.
If these issues can be already found using the forum search and or a
google search, perhaps even have solutions, then there is no need to
mirror them here.
For example the matching mac address Qubes issue is best sorted out
without even mentioning it at Whonix forums. Again, if we mirror all
Qubes native issues at Whonix forum, that will be a mess.
If there are already existing threads, such as for the Bouncing Tor Browser icon (green earth) won't stop bouncing sometimes? (
), and you’re aware of the thread, or found it, then please contribute
to that thread something like “Happens for me in Whonix 184.108.40.206.2 RC also.”
and the power management is disabled
according to system modules in KDE settings.
Yes. One note on that.
Right. That configuration module is now no longer added to kde
sytemsettings. Two things.
disabling power saving is done separately - if that works is a
disabling the kde systemsettings entry - independent of above. Now,
if 1 does not work, then things get get awful without 2). The
alternative would have been a grayed out kde systemsettings power
The network manager isn’t complaining like in v 11 can you see it too?
Yes, this was fixed.
I want to try and push the qxl performance fix before the final release but we’ll see.
Too late now. That would go into Whonix 13. The RC stands for release
candidate. That candidate is going to be released without
rebuild/without changes. I don’t plan to create new builds before Whonix
13 before something is seriously broken.
Then you did build from a tag that did not have that package yet.[quote=“HulaHoop, post:28, topic:1646”]
Can you please post an example build command that targets x64 and stretch sources for both WG and WS.
sudo ./whonix_build --gnw – --build --target qcow2
FYI: If it could not be made to build because of some extraneous package, that would be an awful evironment. Add --allow-untagged true --allow-uncommitted true.