[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [CONTRIBUTE] [DONATE]

Whonix 12.0.0.3.2 RC – Testers Wanted!

Yes, it’s specific to Qubes-Whonix. These packages were installed in the first versions of Qubes-Whonix as part of a bug. Expected to happen for templates that are being upgrades from Whonix 11 to Whonix 12. Please do as whonixcheck advice.

I never used that feature. It’s disabled by default. For similar reasons as https://www.whonix.org/wiki/VirtualBox_Guest_Additions#Clipboard_Sharing. Once you enable it, and if it works, it’s specific to VirtualBox only. Glad it works in Debian, and Whonix also.

yeah i know this https://www.whonix.org/wiki/VirtualBox_Guest_Additions#Clipboard_Sharing

but now just go to virtualbox banner -> devices -> Drag and Drop -> tick Bidirectional -> congratulation!! :triumph:. (without the need to turn off the system).

whonix + Vbox errors:-

1- at startup it shows always red failure:-

2- whonix freezed at the shutdown , so i kill it (End Process of it) then i open it again, and i have got this error:-

Failed to open a session for the virtual machine Whonix-Workstation 12.

The machine ‘Whonix-Workstation 12’ already has a lock request pending.

Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

3- when i press the PrtSc (print screen button) , whonix considering it as an out link, c:-

4- icons sticking (specially TBB) with pointer even after increasing the RAM:-

5- whonix now recognize that im connected to eth0 (the “question mark gone”) not sure i have read that in the changes…:-

From https://www.whonix.org/wiki/VirtualBox_Guest_Additions#Shared_Folder please do:

Power off the virtual machine.[3] 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.

No idea. Does this happen once or often? Does it happen with Debian jessie [KDE] VMs also?

You mean icon bouncing? kde launch feedback?
Bouncing Tor Browser icon (green earth) won't stop bouncing sometimes? ?

From https://www.whonix.org/wiki/VirtualBox_Guest_Additions#Shared_Folder please do:

Power off the virtual machine.[3] 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.

You mean icon bouncing? kde launch feedback?
Bouncing Tor Browser icon (green earth) won't stop bouncing sometimes? ?

yeah , icon bouncing. it keeps dancing witha mouse pointer.

whonix-qubes

this problem seems to be it did no solved well:-

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.

btw , did u removed the wireshark installation ? it didnt showed up when i have installed whonix in the vbox.

The package (anon-gw-leaktest) that depended on it (tshark) has been removed from whonix recommend package dependencies.

Please use the existing thread.

Yes. Will be fixed in Whonix 13:
https://phabricator.whonix.org/T144#7370

Error starting VM: operation failed: device matching mac address 00:16:3e:5e:6c:0d already exist

Note:- happened even before with non-whonix templates. i dont think it is specifically related to whonix.

Answered here: Error starting VM: operation failed: device matching mac address 00:16:3e:5e:6c:

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?

TNT_BOM_BOM:

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
often more.

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 (


) one.

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 12.0.0.3.2 RC also.”

I was unable to reproduce this. Even with fullscreen. When I press print screen, nothing happens. And once I install ksnapshot, then when pressing printscree, ksnapshot opens.

never used that feature. It’s disabled by default. For similar reasons as https://www.whonix.org/wiki/VirtualBox_Guest_Additions#Clipboard_Sharing. Once you enable it, and if it works, it’s specific to VirtualBox only. Glad it works in Debian, and Whonix also.

whonix gateway Guest to host shared clipboard enabled by default! , but the WS both r disabled.

Took v 12 for a spin and can confirm all is looking good here. Shared folders work seamlessly now and the power management is disabled according to system modules in KDE settings.

The network manager isn’t complaining like in v 11 can you see it too?

I want to try and push the qxl performance fix before the final release but we’ll see.

I haven’t looked yet but did you update the forum links in the TBB local homepage?

TNT_BOM_BOM:

never used that feature. It’s disabled by default. For similar reasons as https://www.whonix.org/wiki/VirtualBox_Guest_Additions#Clipboard_Sharing. Once you enable it, and if it works, it’s specific to VirtualBox only. Glad it works in Debian, and Whonix also.

whonix gateway Guest to host enabled by default! , the WS both r disabled.

This is expected as per
https://www.whonix.org/wiki/VirtualBox_Guest_Additions#Clipboard_Sharing.

1 Like

HulaHoop:

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.

    1. disabling power saving is done separately - if that works is a
      different story
    1. 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
      savings entry.

HulaHoop:

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.

HulaHoop:

I haven’t looked yet but did you update the forum links in the TBB local homepage?

No. Will do for Whonix 13. (Low priority, because the redirection works.)

[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Contributors] [Investors] [Priority Support] [Professional Support]