Custom Query (16363 matches)
Results (2092 - 2094 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10512 | duplicate | Clipboard stops working after taking snapshot | ||
| Description |
I see that this issue keeps popping up, but has no real resolution, hopefully this will help, it's repeatable 100% of time. On Windows 7 x64 with Ubuntu 12 VBox, using latest 4.1.14r77440 with same on guest additions and extensions Clip board stopped working so I re-installed everything After re-install clipboard worked, I should note that I only re-installed the VBox client on windows, not the guest additions on Ubuntu. Shutdown and restarted a few times, no issues After 1st snap shot of the VBox it stopped working, I did not stop and restart ubuntu, just did a snap shot and right away the clipboard failed Attached log |
|||
| #6552 | duplicate | Clipboard use locks up VirtualBox in some circumstances (reproduceable) | ||
| Description |
VirtualBox process freezes and renders the clipboard operations on the system unusable upon pasting data that was previously copied from inside VirtualBox process. You may find there's something else that's going on, but the exact steps to reproduce the lockup are as follows: Start VirtualBox GUI. Start "Create New Virtual Machine Wizard" Hit Next, for VM name type "VIRBS_SERVER_MY" Select the text ("VIRBS_SERVER_MY") and hit CTRL+C (I do this as I usually paste the same name for VDI). Click Next, leave memory at default. Click Next, Create New hard disk should be as default. In the "Create New Virtual Disk Wizard" click Next, leave default "Dynamically expanding storage". Click Next, for Location of the VDI, click the browse icon/button to the right of the text box. Press CTRL+V - it should lock up. This doesn't happen if I copy the same text from, say, Notepad. After writing this, I realised the you can go straight to creating a new VDI. |
|||
| #5989 | invalid | Clock is almost at a stand-still | ||
| Description |
Host: Solaris 10 U8 (10/09) Guest: CentOS 5.4, kernel 2.6.18-164.10.1.el5 Guest additions installed: Yes With a fresh install, the clock is going very very slowly in the guest os. I have tried different suggestions from this bug report: http://www.virtualbox.org/ticket/3135 but it seems they have the opposite problem, that the clock is going way too fast... When trying these options to the kernel, the clock seems to work ok, but then the machine just dies after a few minutes with nothing in any logs: nmi_watchdog=0 elevator=deadline noapic nolapic divider=10 nolapic_timer clocksource=acpi_pm After hours and hours of googling, I resort to open a bug report for this, and hope there is a solution for this problem, as I have to choose between having a machine that only stay on for a few minutes, or a clock that slows down 10 minutes per minute or so... |
|||

