Custom Query (16611 matches)
Results (19 - 21 of 16611)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16047 | duplicate | Error deleting a snapshot -> duplicate of #15831 | ||
| Description |
Linux host with windows guest and three .vdi disks. If I try to delete the snapshot the process starts, but after merging the first image the progress window closes but the screen still shows the snapshot as existing. However, the first snapshot physical file has been deleted from the disk, but not removed from the .vbox configuration file. The other two .vdi files are untouched. I can no longer start the VM. This has happened on multiple different VMs. |
|||
| #16469 | fixed | Unresponsive after sleep | ||
| Description |
After upgrading to VB 5.1.14 I have had mouse and keyboard problems. Host: SuSE Leap 64 Bit Default 4.1.36 Kernel Guests: Various 1) If the system is idle long enough for one of the guests to go to sleep, the entire system stops accepting any input. I can not use any of the controls on the VBox Manager, the window manager (openBox), or any of the guest machines - either applications running in the guest, or any of the VBox decorations. The only option is to ssh to the box and kill the VBox threads. On restart, all of the machines that were running are now in an aborted state 2) With the VBox manager running I can no longer use the mouse right-click on an open spot on the desktop to bring up the window manager menu. If I close VBox manager, the mouse right-click again works. Everything was working in 5.1.12 However, on another server I am only having the 2nd issue. This 2nd machine only ever has 1 guest running at a time and only has a single processor. |
|||
| #17101 | duplicate | RDP connection failure | ||
| Description |
After updating the guest additions to 5.1.28 on a Windows 10 guest, I am getting errors with RDP clients - "Remote Desktop Connection has stopped working". Worked with 5.1.26, works on non-VirtualBox systems, and works if I remove the guest additions. I get the following error logged: Faulting application name: mstsc.exe, version: 10.0.10240.17184, time stamp: 0x580ee9a2 Faulting module name: VBoxOGLpackspu.dll, version: 5.1.28.17968, time stamp: 0x59b8f746 Exception code: 0xc0000005 Fault offset: 0x000000000004966f Faulting process id: 0xd64 Faulting application start time: 0x01d3323e84eb3d97 Faulting application path: C:\Windows\system32\mstsc.exe Faulting module path: C:\Windows\system32\VBoxOGLpackspu.dll Report Id: a8105f28-28b8-4122-b3b0-226dec3879c9 Faulting package full name: Faulting package-relative application ID: |
|||
