Custom Query (16612 matches)
Results (52 - 54 of 16612)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17242 | duplicate | no video or audio reproduction | ||
| Description |
After upgrade from virtualbox version 5.1.26 to 5.1.30 on the guest os (debian 9 x64) the video/audio reproduction with mplayer, vlc, firefox htlm 5 ecc no video reproduction. After several attempts find the problem is located on the audio settings, in fact on the oracle site change logs read: VirtualBox 5.1.28 (released 2017-09-13) [...] Audio: fixed accidental crashes when using the AC'97 sound emulation (bug #16959) Audio: fixed crash when default input or output devices have changed (bugs #16968, #16969, #17004) Audio: fixed recording when using the ALSA backend Audio: fixed handle leak when using the OSS backend [...] in fact if change the audio guest controller from "ICH AC47" to "intel hd audio" or "sound blaster 16" the video reproduction is ok but no audio output. Same problem with original virtualbox release by oracle. The host system: OS: debian 9 x64 with kde and without pulseaudio (virtualbox hostaudio ALSA Audio Driver) CPU: i7_920 with all virtualized option active VIDEO: Radeon HD 5850 (audio hdmi disabled) AUDIO: Creative Labs EMU20k2 GUEST OS: debian 9 x64 with lxde and without pulseaudio |
|||
| #20642 | duplicate | network host only not run | ||
| Description |
hello, network host only not run if the defaults ip address of vboxnet0 interface change with specific address (ex 192.168.80.X, 192.168.100.X etc), also the panel for configuration of hostif display error like this Callee RC: E_ACCESSDENIED (0x80070005) on various ip address inserted. OS HOST: Ubuntu 20.04 OS GUEST: Debian 11, Windows 10...
|
|||
| #3843 | fixed | Network adapter disabled on every boot of VM, though settings says enabled. | ||
| Description |
I have a WinXP guest (Ubuntu 9.10 host). Everytime I start it, the network adapter is disabled, thouth the settings show it enabled. I can right-click it and enable it using the adapter icon on the VBox window. I used to always disable the adapter when shutting the VM down, to save time while it timesout trying to run logout scripts for a VPN connection that's not connected. This worked fine in VBox 2.1. The adapter would always be enabled on the next boot (as the machine settings indicate). Only since updating to 2.2 have I seen this odd behavior where the settings show the adapter to be enabled, but launching the VM shows otherwise. This even occurs if I don't disable the adapter when shutting the vm down. I've tried disabling/re-enabling the adapter, and even changing the type - but the VM still always starts with the adapter disabled. |
|||

