Custom Query (16363 matches)
Results (520 - 522 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14445 | fixed | Debian package: libvpx* dependency problem | ||
| Description |
Debian package (virtualbox-5.0 5.0.2-102096~Debian~jessie) depends on the "libvpx1" package. Yes, that package can be found in Debian "Jessie" (stable), but it is no longer in "Stretch" (testing) and "Sid" (unstable) repositories (they instead contain a new variant of that binary package, "libvpx2"), making the "virtualbox-5.0" package non-installable. 2 possible solutions:
|
|||
| #12119 | obsolete | BSOD in VBoxUSBMon, host Win7 amd64 after upgrading 4.2.16 ==> 4.2.18 | ||
| Description |
Host Win7 pro 64-bit, guest Win 8.1 32-bit. VM USB filter set for guest to capture Lumia phone device. repro: guest boots and runs fine until I plug in the USB device. Host crashes immediately. 100% reproduceable. Never had this problem on 4.2.16. DumpCHK output: BugCheck D1, {34, 2, 1, fffff880040c3c78}
Probably caused by : VBoxUSBMon.sys ( VBoxUSBMon+3c78 )
Narrative of the problem in the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=57308 DumpCHK log attached. |
|||
| #1614 | fixed | Missing Run Level shortcuts with generic Linux .RUN install => Fixed in 1.6.2 | ||
| Description |
I have installed VB three times, using the generic Linux .RUN installer. I noticed that the VirtualBox kernel driver and networking are not initialized in run level 2, which is the default run level in Debian. I'm using "testing" and "unstable", so the pre-packaged Debian binaries for "stable" are not usable for me. Symbolic links S20vboxdrv -> ../init.d/vboxdrv S20vboxnet -> ../init.d/vboxnet are installed in /etc/rc3.d/ and /etc/rc5.d/ but not /etc/rc2.d/ which is the Debian default run level. Please consider putting the symbolic links into Run Levels 2 through 5. People who know enough to alter their run level will know to delete these symbolic links if they do not want those drivers to be active. Sadly, it took me a while to figure out why VirtualBox would give me an error when I first started my machine, but work once I "rebuilt" the driver. The initial installation and subsequent driver "rebuilds" all occurred in Run Level 2, which I must assume your installer does not check before creating the symbolic links. |
|||

