Custom Query (16363 matches)
Results (616 - 618 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18048 | fixed | "SUPLIB not initiated successfully" with --disable-hardening --build-debug ==> fixed in SVN | ||
| Description |
In VirtualBox-5.2.18/src/VBox/VMM/VMMR3/VM.cpp
The VM starts when I call SUPR3Init(NULL) earlier. I attached a patch, but I assume you will know how to fix it better. I see someone else has experienced this issue before: https://forums.virtualbox.org/viewtopic.php?f=10&t=84300 |
|||
| #11186 | obsolete | Guest aborts after xsane fails to access scanner on USB | ||
| Description |
Host: Slackware 14.0 64 bit. (have seen error with Slackware 13.37 64 bit host as well) Guest is also running Slackware 14.0 64 bit. If I try to run xsane on the guest, sometimes it will work the first time. However, afterwards if I disconnect the USB and then reconnect the USB under the Devices menu and then try to start up xsane, it will give a message indicating it failed to connect to the scanner. (Failed to open device 'brother2:bus2;dev3':Invalid argument. After a minute or so, the guest will abort. I do not see this error with a Slackware 13.37 64 bit guest. I also do not see this error if I run xsane on the Slackware 14.0 64 bit physical machine or the host machine either. In logs included, xsane failed to connect the first time through. I first saw this error with VirtualBox 4.2.0. I've upgraded to VirtualBox 4.2.4 and still see the same error. |
|||
| #13589 | duplicate | Regular crashes guest after install VirtualBox-4.3.18-96516-Win | ||
| Description |
After installing VirtualBox-4.3.18-96516-Win my VM guest crashes regularly (about every hour). the error in the log seems to indicate : 'Changing the VM state from 'DESTROYING' to 'TERMINATED'.' |
|||

