Custom Query (16612 matches)
Results (52 - 54 of 16612)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #194 | fixed | "Failed to initialize COM ... VirtualBox COM server" error message after re-boot, first login | ||
| Description |
Hi, For more information, see the '[vbox-users]' list: March 14 around noon ET. Subject: openSUSE 10.2 - "Failed to initialize COM ... VirtualBox COM server" error It appears we have a regression. In 1.3.6, openSUSE 10.2/KDE, I am able to leave the main VirtualBox window running and reboot my machine and at first login, there are no VirtualBox errors. With 1.3.8 and the same environment, I get the above error message in a pop-up box at first login after a reboot. In 1.3.6 and 1.3.8, I see two processes running after I shut down VirtualBox:
If I manually 'kill' the processes in 1.3.8 before rebooting my machine, no error is displayed. In 1.3.6, I don't have to 'kill' these processes. Cheers, -pablo |
|||
| #3685 | fixed | "Fatal error during installation" at the deinstallation procedure | ||
| Description |
Because I see a higher CPU usage as usual I decided to deinstall VirtualBox to see if VB is the cause. |
|||
| #1358 | wontfix | "Floating-point division by zero" exception (0xc000008e) at location 0x6e9d3d54 | ||
| Description |
VirtualBox crashes when the application "Macro Magic" is running on the host OS. This may be related to the way that Macro Magic monitors some application properties in order to perform certain actions automatically. In my testing, the crash occurred using a Windows 2000 Pro SP4 host and a Windows XP Pro SP2 guest as soon as the GUI starts up on the guest. Also, the problem only seems to be present when the "Guest Additions" are installed on the guest OS. Closing the Macro Magic application while using VirtualBox does make the error go away. The complete error is given below: "The exception Floating-point division by zero. (0xc000008e) occurred in the application at location 0x6e9d3d54." |
|||

