Custom Query (16363 matches)
Results (1261 - 1263 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2210 | fixed | Text copy/paste broken when run headless (only) | ||
| Description |
I am running headless an XP client in VB 2.0.0 on an XP host and accessing it from yet another XP with the MS standard RDP client (6.0.6001.18000). All XPs are SP2 or SP3. When in a text editor (e.g., notepad.exe), pasting of a (just) copied chunk of text produces garbage. The garbage, seemingly non-text, seems to be same across various clients (XP) and in a clean (rebooted) machine, checked for small chunks of text. Note that this effect does not show when the VM is displayed locally. |
|||
| #2211 | fixed | Mac Leopard Spaces sometimes causes VirtualBox window to disappear entirely | ||
| Description |
This has happened to me a few times. I don't have simple reproducible steps since I really try to avoid this as much as possible. When it happens I have to force quite VirtualBox and deal with potential data loss and disk corruption. Steps go roughly like so though:
|
|||
| #2212 | fixed | VirtualBox.exe crashes VBoxSvc.exe on startup -> fixed in SVN/2.0.4 | ||
| Description |
After installing v2.0.2 (does not happen with 1.6.2-6, 2.0.0), VirtualBox.exe seems to be crashing VBoxSVC on startup. If I go straight to VirtualBox.exe, I get a Debug Dialog indicating VBoxSVC has had an unhandled exception, and offers to debug (I have VS2008 installed). After saying no to debugging, I am then prompted with a critical error from VirtualBox as it is unable to create a COM Object. Error: "Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)" I am pretty sure that it isn't VBoxSvc crashing on its own as I can manually start VBoxSvc from the command line and it runs stable until VirtualBox or VBoxSDL is started, at which it crashes immediately. I Uninstalled 166, installed 202, and had the crash. I then uninstalled 202 and installed 200, worked just fine. Upgraded (Installed over) back to 202 and its crashing again. Uninstalled 202 and deleted the three left over drivers in Win\System32, then rebooted installed, rebooted and tried and crashed. I was in the chat room earlier trying to troubleshoot the issue and there was another individual with the exact same issue. This makes VBox 2.0.2 completely unusable. TEMPORARY SOLUTION See below. |
|||

