extension pack breaks safari and unlock on Mac OSX

[Dave Geysemans]

I installed the extension pack (latest downloaded from the website) and after that I had the following issues on my Mac host:

• Safari stopped working and could not be started again
• when screen was locked I could not unlock it anymore. Only option was a reboot.

Removed extension pack and functionality is back to normal.

[Socratis]

Frankly I can't see why the ExtPack would cause this behavior, except if there's something to do with the USB:

• Follow a "start from cold-boot"/"observe error"/"shutdown" cycle.
• With the VM shut down completely (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response.

Then, post the output of the following commands in the Terminal:

VBoxManage list usbhost
VBoxManage list usbfilters
VBoxManage showvminfo "<Your_Virtual_Machine_Name>"

[Dave Geysemans]

vbox-log

[Dave Geysemans]

thanks for the update. I added two attachements, one the zipped log, the other the output from the asked commands.

I have to say that the extension pack is not installed now because this realy breaks a lot. Would you need me to test provide the output again with the extension pack installed?

[Socratis]

OK, I completely misread the original report, I thought that you were talking about an OSX guest (yes, I know, you wrote it clearly). So, those logs and information do not apply in your problem...

But, it still doesn't compute. Installing the ExtPack on the OSX host affects Safari and screen-locking? Doesn't make any sense. I mean where could it break native functionality?

• Support for USB 2.0 and USB 3.0 devices: you don't even have a USB filter, so that's out.
• VirtualBox RDP: you don't access the host remotely, do you?
• Host webcam passthrough: n/a.
• Disk encryption: n/a.
• NVMe and PXE boot for Intel cards: you don't use it.
• Experimental support for PCI passthrough: n/a.

So, I can't even begin to understand where there might be a conflict. At all! That's the first time I've heard of such a similar case...

Does it happen after the ExtPack installation or when you run your VM? Any VM?

[Dave Geysemans]

I installed the extension pack to be able to attach a USB-device (headset) to a W8 guest. I had a few guests (3 actually) running. When I wanted to browse to a webpage, safari did not respond in any matter at all anymore. Firefox did still work. Restarting Safari resulted in the fact that it did not come up again anymore. I have my screensaver configured to immediately lock as well, so when that activated I could not unlock anymore. The mouse pointer could be moved on the screen, but no keyboard-actions or fingerscan worked to unlock (screensaver did not even stop) After a while I decided to undo the only 'change' I did on the system and that was de-installing the extension pack. When that was done, it all worked perfectly again. I did not access the host remotely.

[Socratis]

Run the following in the Terminal and post the output:

kextstat | grep -v com.apple

[Dave Geysemans]

Index Refs Address Size Wired Name (Version) UUID <Linked Against>

80 0 0xffffff7f81064000 0x9000 0x9000 com.asix.driver.ax88179-178a (1.8.0) 18E125DD-F66C-31C1-8C66-552F9CE8F501 <53 39 7 5 4 3 1>

147 0 0xffffff7f80f1d000 0x45000 0x45000 com.Logitech.Control Center.HID Driver (3.9.5) no UUID <146 145 39 34 5 4 3> 155 3 0xffffff7f84782000 0x63000 0x63000 org.virtualbox.kext.VBoxDrv (5.0.36) E5654976-6355-30F3-B00F-E503D330E0B1 <7 5 4 3 1> 158 0 0xffffff7f847e5000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (5.0.36) FC8E1727-50E9-3FDE-8E5F-BBFCFF129C3D <157 155 39 7 5 4 3 1> 159 0 0xffffff7f847ed000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (5.0.36) E9164EF4-66DF-3B0E-8906-76C47029DB8A <155 7 5 4 3 1> 160 0 0xffffff7f847f2000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (5.0.36) B48422C3-64D0-322C-BB14-A8D5C2B49A53 <155 5 4 1>

[Socratis]

I don't know. You have two external kexts, but still I fail to see how and why they would interact or conflict with the ExtPack. The only thing that you could easily try is to remove temporarily the Logitech control center. Other than that, I really don't know where to start looking and I think that I might have to leave this to the more seasoned ones.

What I do know for sure, is that you're pretty much the only person reporting this. So far...

[Dave Geysemans]

thanks for the feedback anyway. I hope someone with more / other insight reads this and has a possible idea. If I have to test something it might not be possible right away. This is my business laptop which I need running almost all the time... I'll find a moment to do it off course but maybe not right away.