Discuss the 5.0.14 release

[frank]

Discuss the 5.0.14 release here. See the changelog for details.

The main points of this release are improved USB support for Mac OS X El Capitan and fixing a couple of Audio issues.

[loukingjr]

FWIW, Just installed 5.0.14 on a OSX 10.11.3 host. Geting this error when starting a OSX 10.6.8 guest…

Some HDA audio streams (PCM Input) could not be opened. Guest applications generating audio output or depending on audio input may hang. Make sure your host audio device is working properly. Check the logfile for error messages of the audio subsystem.

Error ID:
HostAudioNotResponding
Severity:
Warning

[loukingjr]

As it turns out, I am getting the error mesage on all guests. However, Windows and Linux guests still have audio. OSX 10.6.8 does not.

[socratis]

Did you try switching to the "Input" tab of the Sound preferences in a Mac guest? To me it freezes the VM. Completely! I'll open a new topic...

[loukingjr]

No but I will. I was just testing s few things in the new version.

[loukingjr]

I assume you meant in 10.6.8's sound preferences. I just checked and it doesn't freeze mine.
I just have no audio. lol

[ssawgift]

I once heard that release was always on Friday. Is this an oob release?

[frank]

I once heard that release was always on Friday. Is this an oob release?

Nope. No special day reserved for releases.

[frank]

FWIW, Just installed 5.0.14 on a OSX 10.11.3 host. Geting this error when starting a OSX 10.6.8 guest…

Some HDA audio streams (PCM Input) could not be opened. Guest applications generating audio output or depending on audio input may hang. Make sure your host audio device is working properly. Check the logfile for error messages of the audio subsystem.

Error ID:
HostAudioNotResponding
Severity:
Warning

Lou, 5.0.14 contains a fix to get audio capturing work on Mac OS X hosts. According to the log, audio in does not work on your host for some reason. This should not affect audio output. And audio in did most likely also not work with older 5.0.x releases on your host.

[loukingjr]

Lou, 5.0.14 contains a fix to get audio capturing work on Mac OS X hosts. According to the log, audio in does not work on your host for some reason. This should not affect audio output. And audio in did most likely also not work with older 5.0.x releases on your host.

Hi Frank, I didn't realize the error only related to audio in. All Windows and Linux guests do indeed have functioning audio out. I assume audio in gives an error because Macs use a combined audio in/out jack and I have external speakers connected in mine so there would not be any audio in available unless I assume I was using a USB microphone or a headset with three rings, 2 for left/right audio out and 1 for audio in. Or unplugged the external speakers.

From AskDifferent: "The microphone or headset in question must be of the three-ring variety, just like Apple’s headsets. The fourth pin (ring) is for the microphone."

cTO2F.png (107.88 KiB) Viewed 8503 times

on the other hand, somewhere around VB 5.0.10 - 5.0.12 audio out stopped working with my OSX 10.6.8 guest and failed on several OSX guests according to socratis. See: Bugtracker # 14975

[pingadam]

Hi Frank,

I was just wondering - are the repositories for Ubuntu / Debian updated properly yet?

I'm using Linux Mint 17.3 "Rosa" 64-bit (based on Ubuntu 14.04 "Trusty Tahr"), and get the following message from the Update Manager:

Could not download all repository indexes
Failed to fetch http://download.virtualbox.org/virtualb ... 6/Packages Hash Sum mismatch
Some index files failed to download. They have been ignored, or old ones used instead.

(The URL is shown truncated above - it is actually: download.virtualbox.org/virtualbox/debian/dists/trusty/contrib/binary-i386/Packages)

Updates have always worked fine before - I haven't actually tried yet to install, but just thought I'd flag up this error message.

Many thanks.

[pingadam]

UPDATE: the Ubuntu repositories seem to be working again now (as of around 16:00 GMT, when I updated to VirtualBox 5.0.14 via Linux Mint's Update Manager).

Many thanks.

[johnlee]

re very latest test build 5.0.16 50518, just downloaded the win flavour, run the vm manager & looked at 'help contents' , section 15.1, 5.0.16 xxx and the only item is 'dummy'.

Was this intended? Surely the whole point of you creating a new test build is that it fixes something - otherwise not much point asking vb users to try them.

[loukingjr]

I assume "dummy" is a place holder for more info to follow.

My understanding is, test builds are to address certain problems a user or users have posted either on Bugtracker or in the forums. Those users are notified there is a Test Build available to try that addresses their problem.

As far as general users…

If you want advance peeks at what has changed since the last stable release, or to help us catch little problems which may have sneaked in and which we failed to spot, we encourage you to regularly try out test builds. Doing this greatly helps our testing effort. We only add features and fixes to these builds that we think are ready for release, so the stability of these builds should be similar to that of official releases.

[johnlee]

No point in replying if you are just reiterating stuff that we all know! My point was why do a test build w/o saying what's changed, which is what's normally in the hel contents - ps I use them all the time, you obviously don't! j