Custom Query (16363 matches)
Results (544 - 546 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10438 | worksforme | Latest Virtual Box Additions corrupt clipboard (previous additions do not) | ||
| Description |
This worked in Guest Additions 4.1.6 but is broken in the latest. I do not know what version it became broken at, I just updated the other day for the first time. With VBOX 4.1.12 and reverting Guest Additions to 4.1.6 I do not see this issue. For the most part the clipboard is fine, but when using Office 2007 Enterprise and copying a table from Excel and then doing a "Paste Special" in Word (Selecting Paste Link, and Excel Worksheet) focus will be lost in Word and Excel will become highlighted on the Taskbar. If you click on Excel it will give you a very cryptic error message "A document with the name '...' is already open. You cannot open two documents with the same name, even if the documents are in different folders. To open the second document, either close the document that's currently open, or rename one of the documents." I only started getting this bug after upgrading to the latest Virtual Box additions, and it went away when I uninstalled them and went back to the previous version. If it makes a difference, my Office documents are on a drive that's been mapped to the host machine. Host and client are both Windows 7 x64. Feel free to email me for additional details: BrainSlugs83 at gmail dot com. |
|||
| #9650 | obsolete | VBoxManage guestcontrol hangs on execute | ||
| Description |
Example session: VBoxManage --nologo guestcontrol 'Uru Build Server' execute --image 'C:\windows\notepad.exe' \ --username buildbot --password password --wait-stdout --verbose Waiting for guest to start process ... Process 'C:\windows\notepad.exe' (PID: 2104) started Waiting for process to exit ... ^C^C^C Once I close notepad (or the process terminates on its own), VBoxManage does not end, instead it just hangs at "Waiting for process to exit ...". SIGINT has no effect on VBoxManage at this point. If I kill the VBoxManage process and try to run a new instance of it, it will hang at "Waiting for guest to start process ..." (as if some sort of lock was never released by the killed process?). No process is ever launched in the VM. As far as I can tell, this can't be fixed without restarting the VM. The VM is pretty lightweight - currently the only program installed is Visual Studio. |
|||
| #12259 | obsolete | VBoxNetFlt.sys BSOD W8 after wake from sleep | ||
| Description |
To reproduce: https://github.com/mattiasbrand/bsod-sample Quoted from Microsoft Support: "From our analysis we found out that the miniport driver “VBoxNetFlt.sys” for Intel(R) 82579LM Gigabit Network Connection (VirtualBox Bridged Networking Driver Miniport) is passing the PcwDataBlock value as NULL which is the cause of the issue." |
|||

