Bug 5214 - VirtualBox 4.1.12 (released 2012-04-02)
Summary: VirtualBox 4.1.12 (released 2012-04-02)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-03 16:20 CEST by Bit Twister
Modified: 2012-04-05 00:52 CEST (History)
0 users

See Also:
Source RPM: virtualbox
CVE:
Status comment:


Attachments

Description Bit Twister 2012-04-03 16:20:29 CEST
Description of problem:
Audio: fixed a crash in the NUL audio backend (bug #10374; 4.1.10 regression)
Guest Additions: VBoxService should not crash on exit (bug #10326; 4.1.10 regression) 

https://www.virtualbox.org/wiki/Changelog

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Frédéric "LpSolit" Buclin 2012-04-04 00:02:15 CEST
4.1.12 is already available in Cauldron.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 2 Bit Twister 2012-04-04 12:54:09 CEST
4.1-4.1.12_77218 replaced by
4.1-4.1.12_77245

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 3 Manuel Hiebel 2012-04-04 19:43:40 CEST
can you reproduce the bug https://www.virtualbox.org/ticket/10405 ?
Comment 4 Bit Twister 2012-04-04 21:15:21 CEST
No, this reopen was a heads up that VB developers had done a quick 24+ hour
re-release of virtual box and Extension_Pack where I had assumed Mageia's 4.1-4.1.12 copy is not the _77245 copy.

I was wanting the recent copy to verify adding the audio group to a user at runlevel 3 causes a VB Guest to abort when KDE attempts to connect to the sound device during login.
Comment 5 Manuel Hiebel 2012-04-05 00:17:56 CEST
if you can't reproduce I guess it's ok, thomas can you check ?

(don't know how we can check in our side)

Assignee: bugsquad => tmb

Comment 6 Thomas Backlund 2012-04-05 00:52:15 CEST
We have the 77245 build.

I verified that before releasing it into Cauldron

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.