Opened 10 years ago
Closed 8 years ago
#12930 closed defect (obsolete)
extraneous icon in dock
Reported by: | Louis King Jr | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.10 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Mac OS X |
Description
I believe since the start of the 4.3... versions of VirtualBox an extra icon shows up in the dock on OSX 10.9. Apparently caused by one of the VirtualBox services. I'm going to try and attach a screen shot.
Attachments (1)
Change History (7)
by , 10 years ago
Attachment: | Screen Shot 2014-04-09 at 2.21.39 PM.jpg added |
---|
comment:1 by , 10 years ago
comment:2 by , 10 years ago
I have been experiencing the same problem for a long time. Today I tried completely uninstalling VirtualBox using the uninstall script and then installing it afresh. Unfortunately there was no improvement, the problem persists. Whenever I start a virtual machine an additional dock icon pops up that can be seen in Activity Monitor in red as "Not Responding". Opening a second virtual machine however does not produce a second icon. Only when all VMs get closed does the icon/process go away. If I stop it with Force Quit, then VirtualBox starts behaving strangely: empty VM settings dialog with only OK and Cancel buttons, inability to do anything with the VM because it does not seem to find it, etc...
comment:4 by , 10 years ago
The problem persisted through 4.3.10 and now, 4.3.12. Strangely enough, that happens on my MacBook Pro only. On the iMac the extraneous icon isn't there and I keep the versions on both machines the same.
comment:5 by , 10 years ago
Another thing I've noticed recently, since I did a complete reinstall of VirtualBox, is that without the extension pack the icon doesn't show up. Once the extension pack is installed however it does show up.
comment:6 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Which version of VBox are you using? I think there was a fix in VBox 4.3.8 which sounds to be related to your problem.