The problem is when start virtual machine it crash in a few seconds after start. With disabled sound in virtualbox propereties it works fine. Problem began after upgrade libsdl from 1.2.14 to 1.2.14-r1, downgrade back to libsdl-1.2.14 fixed the crashes. I think that the reason for this: 15 Mar 2010; Michael Sterrett <mr_bones_@gentoo.org> +libsdl-1.2.14-r1.ebuild: don't use dlopen to open libraries but instead link against them. Reproducible: Always
i confirm. with 1.2.14 sound works fine, but not with 1.2.14-r1 it doesn't crash for me though just silence with 1.2.14-r1
i have a similar problem. with libsdl-1.2.14-r1 virtualbox-bin complains about "HostAudioNotResponding" when using alsa. with oss the problem is no longer present, but access needs to be exclusive. this is not a good option for me. downgrading to libsdl-1.2.14 fixed it. should this be considered a bug for virtualbox-bin or is it rather a bug for libsdl?
Confirm with virtualbox-bin-3.1.6. Downgrade to libsdl-1.2.14 fixed it.
Ditto here
libsdl-1.2.14-r2 + virtualbox-bin-3.1.6 = broken alsa. Anybody look at this bug?
(In reply to comment #5) > libsdl-1.2.14-r2 + virtualbox-bin-3.1.6 = broken alsa. Anybody look at this > bug? > Same problem here. I had to downgrade to libsdl 1.2.14, masking both r1 and r2.
Here too - no sound in WindowsXP guest. Commenting out the following lines in the current ebuild like this: #--disable-alsa-shared \ #--disable-esd-shared \ #--disable-pulseaudio-shared \ #--disable-arts-shared \ #--disable-nas-shared \ #--disable-x11-shared \ #--disable-osmesa-shared \ and reemerging (emerge -av =libsdl-1.2.14-r2) made sound in Virtualbox 3.1.6 come again here.
(In reply to comment #7) > Here too - no sound in WindowsXP guest. > > Commenting out the following lines in the current ebuild like this: > > #--disable-alsa-shared \ > #--disable-esd-shared \ > #--disable-pulseaudio-shared \ > #--disable-arts-shared \ > #--disable-nas-shared \ > #--disable-x11-shared \ > #--disable-osmesa-shared \ > > and reemerging (emerge -av =libsdl-1.2.14-r2) made sound in Virtualbox 3.1.6 > come again here. > For people who uses alsa, the problem is here: --disable-alsa-shared (Enabling alsa won't do --enable-alsa-shared). It looks like no --disable-*-shared should be set, just like in libsdl-1.2.14.ebuild, because it won't be enabled after --enable-*.
ah finally got my sound working in vbox with these tips :) should implement this someway =)
Is this still an issue with >=app-emulation/virtualbox-bin-3.1.8?
app-emulation/virtualbox-bin-3.2.0 media-libs/libsdl-1.2.14-r2 no sound, same error :-(
*** Bug 322015 has been marked as a duplicate of this bug. ***
Hi, i 've reached the same conclusion. For the users using alsa, the compiling option --enable-alsa-shared is absolutely needed. The others no (But for those who use pulse audio, i've down a use also). And it solved the problem for me. Have a look to the duplicated bugg i created.
games herd, what do you think?
No way are we exposing the dynamic loading again. That is way too error prone.
Mr Bones, could you explain please ? or give a bugg reference for my understanding ? Cause i'm not aware about this dynamic load that is giving errors. If i am, i will be able to understand what's happening if it occurs on my desk with this modified ebuild. Thx
is anybody going to fix this bug or should i keep masked >=media-libs/libsdl-1.2.14-r1 ? =)
(In reply to comment #17) > is anybody going to fix this bug or should i keep masked > >=media-libs/libsdl-1.2.14-r1 ? =) > It is still present. I did not understand where this bug came out in the sub-release version of libsdl.
Created attachment 243983 [details] bug fix for virtualbox and alsa Edited ebuild like in connment #8 sound now works with alsa in virtualbox 3.28 and libsdl-1.2.14-r3 just recompile and sound will work tested 8-21 0930 with virtualbox 3.2.8 on kernel 2.6.34
ommenting out the following lines in the current ebuild like this: #--disable-alsa-shared \ #--disable-esd-shared \ #--disable-pulseaudio-shared \ #--disable-arts-shared \ #--disable-nas-shared \ #--disable-x11-shared \ #--disable-osmesa-shared \ and reemerging (emerge -av =libsdl-1.2.14-r3) made sound in Virtualbox 3.1.6 come again here. TESTED and working on virtualbox 3.2.8 and libsdl-1.2.14-r3
Please see comment #15. Games herd is not interested in this kind of fix. Unfortunately due to the nature of virtualbox-bin being a binary package this leaves us (vbox maintainers) with no real solution to this problem. You might have two options here which are both not quite satisfactory: - maintain your own libsdl ebuild via private overlay. - convince upstream to let vbox-bin use libsdl without dynamic loading (which I doubt they even can implement reliably).
cool solution. "if we have broken something just because this is cool. fix it yourself or ask somebody to fix" =) of course i don't know what didn't work with shared sdl, but maintainers should be sure that at least most popular packages work fine before commiting smth or closing bugs IMHO. at least don't remove last working versions..
I do not accept the solution "CANTFIX". It worked with libsdl-1.2.14 and libsdl-1.2.14-r3 breaks a working solution.
Guys, please don't think that we vbox maintainers do not want to help you. The problem here is that libsdl is not maintained by us but by the games herd. And if they dropped dlopen it was for some (most probably good) reason. Of course I'd love to see someone from games herd explaining to us in detail why they dropped dlopen. If someone from games herd reads this, please be so kind and drop a comment here. And if you really want to do us a favour, maybe you can come up with some idea how to solve this problem. Fact is that there is not much we vbox maintainers can do here because the problem is within a binary package (which means no source code that can be patched and no chance to disable libsdl support). I am going to try poking vbox upstream about the problem but like I said before, I doubt they are willing to come with a solution to this.
Then if i good understand you don't why they dropped dlopen. As i'm using "tell me more", i need the sound in vbox windows. If you don't know why deactivating dlopen. please, just activate it via a USE option, add a comment at the end of the ebuild and let the users choose. Cause today, i must patch it myself each time there is an upgrade on it. When we'll know why deactivating is necessary then we'll be able to argument it. Thx
Ijust want to mention that i didn't encountered any problem with libsdl using the option --enable-alsa-shared since i'm using it.
Since I have no problems with my "hacked" libsdl either, therefore enjoying sound in my virtual maschine, I guess adding an appropriate USE-Flag to the libdsl package and making virtualbox-bin depend on it would be the right solution. Wasn't gentoo about choice? To whom do we have to adress?
try it with media-libs/libsdl-1.2.14-r4
(In reply to comment #28) > try it with media-libs/libsdl-1.2.14-r4 > Still broken with latest virtualbox-bin.
same here. --disable-alsa-shared is still used. Commenting it out (=changing the ebuild) makes sound comes again in virtualbox-bin.
polynomial-c@shanghai:~ $ diff -u $(portageq envvar PORTDIR)/media-libs/libsdl/libsdl-1.2.14-r{3,4}.ebuild --- /var/portage/media-libs/libsdl/libsdl-1.2.14-r3.ebuild 2010-10-26 18:06:15.000000000 +0200 +++ /var/portage/media-libs/libsdl/libsdl-1.2.14-r4.ebuild 2010-10-26 18:03:26.000000000 +0200 @@ -1,6 +1,6 @@ # Copyright 1999-2010 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 -# $Header: /var/cvsroot/gentoo-x86/media-libs/libsdl/libsdl-1.2.14-r3.ebuild,v 1.2 2010/10/26 16:03:26 mr_bones_ Exp $ +# $Header: /var/cvsroot/gentoo-x86/media-libs/libsdl/libsdl-1.2.14-r4.ebuild,v 1.1 2010/10/26 16:03:26 mr_bones_ Exp $ EAPI=2 inherit flag-o-matic multilib toolchain-funcs eutils libtool polynomial-c@shanghai:~ $ mr_bones_ did you really change anything in the ebuild? Let's reopen this bug till this is finally sorted out.
Forget my previous comment about no changes. I was just told that the fix went into both revisions. So it seems like the fix really doesn't help.
the ABI changes due to the X11 configure flag and SDL does a lot of crap with it, so that's what was fixed in -r4. however, the ABI now matches between 1.2.14 and 1.2.14-r4 and no one else seems to be affected. alsa audio certainly still works between my systems and random games. no interest in undoing these fixes that SDL has seen for one binary-only package. as pointed out, Debian also does this with their sdl install. so someone will need to investigate why the virtualbox binary doesnt work. i certainly have no interest in troubleshooting binary only packages, especially when their open source counter part (virtualbox-ose) works fine.
Allright, i really don't understand you. Is it so difficult to add a USE like "AlsaShared" to enable it for the binary package of Virtual Box and let's the users choosing ? By default it will be -AlsaShared. Then the games herd will be also happy. Really, i don't understand your point of view on this. That's a binary package. Some users of your distro wish to use it. They don't want to use the OSE version. They ask you to enable the flag with a USE and will assume any collaterals effects. Is gentoo just a copy of Debian ? Isn't more flexible than Debian ? I wonder why i'm using Gentoo instead of Debian or Ubuntu then. Again, i'm working with it since 6 months and have experimented no problem with it as i'm not a gamer. I think a compromise that will satisfy everybody could be found on this.
plz, have a look to bugg 322015.
(In reply to comment #33) > i certainly have no > interest in troubleshooting binary only packages, especially when their open > source counter part (virtualbox-ose) works fine. -ose works fine, but has limitations when compared to the -bin version (no USB device support, for example). That's why it's not just a 'save me the compiling' package. Would be great if someone could fix this issue.
-ose doesn't work for me (https://bugs.gentoo.org/show_bug.cgi?id=348302) so i want fully functional binary package. =)
I just added app-emulation/virtualbox-4.0.0 (please note the missing -ose in the package's name) to the tree. When you emerge this package with USE="extensions" set you get everything the -bin package also provides. Maybe that's an option you guys can live with.
Any chance to get this problem fixed? Going back to the current stable libdsl 1.2.13 just postpones the problem (especially for no-multilib user like me) until 1.2.14 gets stabilized.
Same here for Virtualbox-4.0.4 All builds 1.2.14-r1 and later are resulting in no working sound for the VirtualBox Guest. libsdl-1.2.14 is working.
I also have sound problem with app-emulation/virtualbox-bin-4.0.6. I get the "HostAudioNotResponding" message when starting any virtual machine (every "Host driver" has the same problem). My VirtualBox does not crash though. I had media-libs/libsdl-1.2.14-r6 but when I masked this version and media-libs/libsdl-1.2.13-r1 got installed, the problem flew away.
(In reply to comment #40) > Same here for Virtualbox-4.0.4 > > All builds 1.2.14-r1 and later are resulting in no working sound for the > VirtualBox Guest. > > libsdl-1.2.14 is working. Hah. Of course. None "--disable-alsa-shared"
More than one year later .... same state.
Complain to Oracle, or use KVM.
I still can't understand why we should address to someone else than the package maintainer. A simple USE-Flag should solve all the questions asked here. Until then, we have to switch to the non-binary version or do the change in the ebuild manually.
since no one has shown a bug in sdl, nothing for games to do
I still don't understand the politics here, but I really would: No one speaks about a bug in libsdl. There is a missing feature in libsdl because of a hardcoded configuration. The idea is just to make it configurable to be used with virtualbox-bin. Or does someone has to oben a new bug(report) here literally strictly adressing to libsdl?
Please rad the whole bug. I'm afraid such a new bug would be closed as INVALID by the games herd members. Unfortunaltely there's nothing I can do here as co-maintainer of virtualbox-bin to change this narrow-minded opinion.
TO GAMES HERD TO Mr BONES I saw that in the ebuild : if use !audio || use !video || use !joystick ; then ewarn "Since you've chosen to turn off some of libsdl's functionality," ewarn "don't bother filing libsdl-related bugs until trying to remerge" ewarn "libsdl with the audio, video, and joystick flags in USE." ewarn "You need to know what you're doing to selectively turn off parts of libsdl." epause 30 fi if use custom-cflags ; then ewarn "Since you've chosen to use possibly unsafe CFLAGS," ewarn "don't bother filing libsdl-related bugs until trying to remerge" ewarn "libsdl without the custom-cflags use flag in USE." epause 10 fi Would it be possible to add 'alsashared' 'use' with a comment at the begin and the end of the ebuild like those ones when used ? I think it should be a good compromise. What's your opinion about ?
O.K., just another thing I won't understand .... So I did it again - the whole story for someone else out there, if there is still life out there .... 1. Open /usr/portage/media-libs/libsdl/libsdl-1.2.14-r6.ebuild as root with a text editor, 2. adding a # before --disable-alsa-shared ====> new code: ... --enable-file \ -enable-cpuinfo \ #--disable-alsa-shared \ --disable-esd-shared \ --disable-pulseaudio-shared \ .... and finally: cd /usr/portage/media-libs/libsdl ebuild libsdl-1.2.14-r6.ebuild manifest emerge -1av libsdl So now my PC sings constantly like a drunken sailor, the FBI and the games herd is chasing me around the whole world and my shrink begs me to contact him (off course - I won't) but the good news: !!!! My windowsXP guest in virtualbox-bin has sound again. !!! Well, updating KDE is much more work than doing this change to the ebuild of libsdl so maybe one day I will finally live in peace with this matter.
Same here. VirtualBox 4.0.8, no sound in guest when alsa selected. Removing --disable-alsa-shared from ebuild fixes the problem. Is that really so difficult for package maintainer to do the same ?
(In reply to comment #51) > Same here. > VirtualBox 4.0.8, no sound in guest when alsa selected. > Removing --disable-alsa-shared from ebuild fixes the problem. > Is that really so difficult for package maintainer to do the same ? No offense intended but it's kind of pointless for people to keep commenting about this. We all know removing --disable-alsa-shared fixes this. Why the maintainer(s) can't add a simple use flag to fix it is beyond me. They have other use flags with warnings in this package but for some reason are just being bull-headed about this one. So unfortunately we're all stuck maintaining are own ebuilds in local overlays in order to use virtualbox-bin.
O.K., we lost hope that the maintaniners of libsdl will do something. But at least in some way we can maintain our local work arounds together here. So I still enjoy to hear from you at least from time to time, that I am a) on the right track b) that "it" (=the work around compiling libsdl with changed ebuild again) still works
(In reply to comment #53) > But at least in some way we can maintain our local work arounds together here. > So I still enjoy to hear from you at least from time to time, that I am > a) on the right track > b) that "it" (=the work around compiling libsdl with changed ebuild again) > still works I had the same problem back in the times, when I used virtualbox-bin. So I can add a version of libsdl to cj-overlay until we find a real solution, if you post a patch to ebuild here.
(In reply to comment #54) > (In reply to comment #53) > > But at least in some way we can maintain our local work arounds together here. > > So I still enjoy to hear from you at least from time to time, that I am > > a) on the right track > > b) that "it" (=the work around compiling libsdl with changed ebuild again) > > still works > I had the same problem back in the times, when I used virtualbox-bin. So I can > add a version of libsdl to cj-overlay until we find a real solution, if you > post a patch to ebuild here. There's a "-r7" version in funtoo with a alsa-shared and pulseaudio-shared USE flag i committed to funtoo a little while back when i was helping them. You could just copy that one. https://github.com/funtoo/portage/blob/funtoo.org/media-libs/libsdl/libsdl-1.2.14-r7.ebuild
(In reply to comment #55) > There's a "-r7" version in funtoo with a alsa-shared and pulseaudio-shared USE > flag i committed to funtoo a little while back when i was helping them. You > could just copy that one. > https://github.com/funtoo/portage/blob/funtoo.org/media-libs/libsdl/libsdl-1.2.14-r7.ebuild Added -r7 to cj-overlay including alsa-shared and pulseaudio-shared use flag.
(In reply to comment #50) > O.K., > > just another thing I won't understand .... > > So I did it again - the whole story for someone else out there, if there is > still life out there .... > cut ... Yes, we're out here Solved the problem through your indications , thx
I read this "thread" and I'm sad. All the users want to use virtualbox-bin must read pages of google matches to find this bug, and manually edit an ebuild or create overlay to fix a problem, that affecting thousands of users, just because libsdl maintainer is not agree on implementing a USE flag on this? Unbelievable. This is not about the bug anymore, it's about gentoo package maintenance politics. I think it's not a package maintainer's job to decide what's useful, right, or free to do for users.
(In reply to comment #58) > I read this "thread" and I'm sad. All the users want to use virtualbox-bin must > read pages of google matches to find this bug, and manually edit an ebuild or > create overlay to fix a problem, that affecting thousands of users, just > because libsdl maintainer is not agree on implementing a USE flag on this? > Unbelievable. > > This is not about the bug anymore, it's about gentoo package maintenance > politics. I think it's not a package maintainer's job to decide what's useful, > right, or free to do for users. BTW the commenting out, and enabling alsa-shared in the ebuild (and rebuilding) didn't solved the problem for me.
(In reply to comment #58) > I read this "thread" and I'm sad. All the users want to use virtualbox-bin must > read pages of google matches to find this bug, and manually edit an ebuild or > create overlay to fix a problem, that affecting thousands of users, just > because libsdl maintainer is not agree on implementing a USE flag on this? > Unbelievable. > > This is not about the bug anymore, it's about gentoo package maintenance > politics. I think it's not a package maintainer's job to decide what's useful, > right, or free to do for users. This problem here has two sides "the virtualbox-bin (only bin) sound issue" vs. "the exposing the dynamic loading, which is too error prone". And it is not obvious what is the best for the majority of users. That is why I put libsdl in my overlay to make it less painful for those who are on the virtualbox-bin side like me. So go and run these simple 5 commands: $ emerge layman $ layman -a cj-overlay $ echo media-libs/libsdl >> /etc/portage/package.accept_keywords $ echo "media-libs/libsdl alsa-shared pulseaudio-shared" >> /etc/portage/package.use $ emerge media-libs/libsdl
(In reply to comment #60) > $ echo media-libs/libsdl >> /etc/portage/package.accept_keywords I'd suggest against unmasking all libsdl libraries, as it might cause some trouble in future, whenever a new version gets released and the user forgets that line in package.keywords (it has already happened to me, but with another package). It's better to run this: $ echo '=media-libs/libsdl-1.2.14-r7' >> /etc/portage/package.accept_keywords
(In reply to comment #61) > (In reply to comment #60) > > $ echo media-libs/libsdl >> /etc/portage/package.accept_keywords > > I'd suggest against unmasking all libsdl libraries, as it might cause some > trouble in future, whenever a new version gets released and the user forgets > that line in package.keywords (it has already happened to me, but with another > package). > > It's better to run this: > > $ echo '=media-libs/libsdl-1.2.14-r7' >> /etc/portage/package.accept_keywords Well, yes and no. If the tree gets an revision bump, which happened in the past already, it will also be called r7 and I will have to create r8 and then the above line is not so useful anymore. However, the commands were more meant as an example anyway, gentoo user should know what is in their package.* files.
I just tried the build suggested by #(In reply to comment #55) > There's a "-r7" version in funtoo with a alsa-shared and pulseaudio-shared USE > flag i committed to funtoo a little while back when i was helping them. You > could just copy that one. > https://github.com/funtoo/portage/blob/funtoo.org/media-libs/libsdl/libsdl-1.2.14-r7.ebuild Just tried this solution and definitely works, I don't know the implications of the two flags, but indeed having a static compile flags in the ebuild doesn't seem to be a good solution either. I wonder if libsdl maintainer can ever fix this, it seems to be going on since like 3 years or so.
Fix is available on overlay moonrise - modified ebuild: https://github.com/Barthalion/moonrise/blob/master/media-libs/libsdl/libsdl-1.2.14-r6.ebuild
*** Bug 363635 has been marked as a duplicate of this bug. ***
Well, it's nice to have a fix in some overlay, but I really think this should be fixed in the main tree. The "Debian does it" excuse is ridiculous: This is Gentoo, we used to have "choice". There's so many ebuilds with custom USE flags, full of warnings and "be sure to know what you're doing", heck there are even undocumented USE flags like "I_KNOW_WHAT_I_AM_DOING" and "MYSQL_INIT_I_KNOW_WHAT_I_AM_DOING". Start listening to your users and get this "herd A vs. herd B" politics crap out of the distribution! Else we could just drop the whole "USE flag" feature altogether and rename this distribution to Gentoobian, if we're exposed to the maintainers' caprice anyway... Note: This is not meant to piss any maintainers off. We have too few of them anyway, and I really appreciate their hard work. This is also not meant to piss the games herd off, who are also doing a great job. But the back and forth between two herds on this bug, each claiming not to be responsible doesn't help anyone, least of all the users.
Hello, the problem still persists here: Host: Gentoo Linux 10.0 kernel 3.2.6 x86_64 VBox version: app-emulation/virtualbox-bin-4.1.8 Guest Additions 4.1.8r75467 Guest OS: Windows 7 64bit Ultimate media-libs/libsdl-1.2.15 (X alsa audio fbcon joystick opengl video xv) No errors, no audio. All seems to be OK in the guest, as the audio would reproduce as usual. Further info at https://forums.virtualbox.org/viewtopic.php?p=219019#p219019
I happened across this thread almost a year ago and masked libsdl > 1.2.14 so I wouldn't unknowingly lose sound in VirtualBox. I also expected that by the time libsdl was required to be upgraded beyond 1.2.14, that this issue would have been fixed by the Gentoo maintainers. I agree w/ many other posters that it's disappointing to have to choose between losing sound and maintaining my own ebuild in an overlay. One thing I noticed after having read all comments in this issue to date was a couple comments about no bug having been opened in SDL. One comment (#46) from SpanKY: https://bugs.gentoo.org/show_bug.cgi?id=310793#c46 : "since no one has shown a bug in sdl, nothing for games to do" So I'm wondering, has anyone actually opened a bug in SDL asking for support on this issue?
(In reply to comment #68) > I happened across this thread almost a year ago and masked libsdl > 1.2.14 > so I wouldn't unknowingly lose sound in VirtualBox. I also expected that by > the time libsdl was required to be upgraded beyond 1.2.14, that this issue > would have been fixed by the Gentoo maintainers. I agree w/ many other > posters that it's disappointing to have to choose between losing sound and > maintaining my own ebuild in an overlay. > > One thing I noticed after having read all comments in this issue to date was > a couple comments about no bug having been opened in SDL. One comment (#46) > from SpanKY: https://bugs.gentoo.org/show_bug.cgi?id=310793#c46 : > "since no one has shown a bug in sdl, nothing for games to do" > > So I'm wondering, has anyone actually opened a bug in SDL asking for support > on this issue? Because it isn't an upstream issue, it's a configuration issue. It works if you pass --enable-alsa-shared to configure, but games herd refuses to even add this as an option.
Just use the ebuild without "--disable-alsa-shared" from moonrise or cj-overlay and wait for virtualbox-bin-(N+1).
(In reply to comment #69) > Because it isn't an upstream issue, it's a configuration issue. It works if > you pass --enable-alsa-shared to configure, but games herd refuses to even > add this as an option. Maybe I used the wrong terminology. I'm wondering if anyone opened a bug for the libsdl Gentoo package maintainers asking for support. From this thread, I take it that's the "games herd"? In other words, are we all assuming they won't help based on the comments that have been left in this bug? Or has someone actually asked for help beyond this bug?
(In reply to comment #70) > Just use the ebuild without "--disable-alsa-shared" from moonrise or > cj-overlay and wait for virtualbox-bin-(N+1). Yes, I know how to work around the issue (semi-)manually. I'd prefer a more official solution (and from this thread, it seems I'm not the only one). Are you saying that the next virtualbox-bin version will solve this problem? If so, can you substantiate that?
(In reply to comment #72) > (In reply to comment #70) > Are you saying that the next virtualbox-bin version will solve this problem? > If so, can you substantiate that? No, but there is always a next version in which things may have changed ;-)
(In reply to comment #70) > Just use the ebuild without "--disable-alsa-shared" from moonrise or > cj-overlay and wait for virtualbox-bin-(N+1). I doubt virtualbox people will change anything in handling of libsdl in their future bin-packages. Anyway I wonder why people seem to prefer virtualbox-bin over virtualbox source package. The only group of people we keep virtualbox-bin for are users of the "amd64 no-multilib" profile. All people not using such a system can get the same kind of functionality with app-emulation/virtualbox and the extensions USE flag being enabled.
(In reply to comment #74) > Anyway I wonder why people seem to prefer virtualbox-bin over virtualbox > source package. The only group of people we keep virtualbox-bin for are > users of the "amd64 no-multilib" profile. OK, and then please tell me why is virtualbox-bin not masked for those people not using "amd64 no-multilib" profile?
(In reply to comment #74) > > Anyway I wonder why people seem to prefer virtualbox-bin over virtualbox > source package. virtualbox-bin used to have support for things that were not available in the open-source edition, like USB. Is it not true anymore? Does the open-source edition have the same features as the binary one?
(In reply to comment #76) > (In reply to comment #74) > > > > Anyway I wonder why people seem to prefer virtualbox-bin over virtualbox > > source package. > > virtualbox-bin used to have support for things that were not available in > the open-source edition, like USB. Is it not true anymore? Does the > open-source edition have the same features as the binary one? Since app-emulation/virtualbox-4.0.0 it supports USB-1 without any extensions package. With help of the app-emualtion/virtualbox-extpack-oracle package it has USB-2, VRDP and PXE-boot support like the -bin package. So no need to stick with virtualbox-bin for any of these features.
(In reply to comment #76) > virtualbox-bin used to have support for things that were not available in > the open-source edition, like USB. Is it not true anymore? Does the > open-source edition have the same features as the binary one? And this is why I use virtualbox-bin since many years! Actually I was using app-emulation/virtualbox before switching to virtualbox-bin just for that reason.
(In reply to comment #77) > (In reply to comment #76) > > (In reply to comment #74) > > > > > > Anyway I wonder why people seem to prefer virtualbox-bin over virtualbox > > > source package. > > > > virtualbox-bin used to have support for things that were not available in > > the open-source edition, like USB. Is it not true anymore? Does the > > open-source edition have the same features as the binary one? > > Since app-emulation/virtualbox-4.0.0 it supports USB-1 without any > extensions package. With help of the app-emualtion/virtualbox-extpack-oracle > package it has USB-2, VRDP and PXE-boot support like the -bin package. So no > need to stick with virtualbox-bin for any of these features. The primary reason I was using the bin package (was for USB support). So does app-emulation/virtualbox-bin have any advantages (from a feature set perspective) over app-emulation/virtualbox-4 + app-emualtion/virtualbox-extpack-oracle?
Please update the ebuild in overlay. 1.2.15 went stable in main tree and does not get updated from overlay anymore... I really hate this behaviour...
@Lars (comment 77) The devel of vbox say they cannot however guarantee that OSE will be working with the binary only extpack. Is that guaranteed by vbox-ose gentoo mantainers? thansk (i'd rather switch to ose and get out of this mess with sdl! :) )
(In reply to comment #80) > Please update the ebuild in overlay. 1.2.15 went stable in main tree and > does not get updated from overlay anymore... > I really hate this behaviour... lidsdl-1.2.15-r1 is in cj-overlay since Jan 2012.
Christoph, sorry , should have explained better, i was using moorise since i don't have mercurial installed. However i fixed by copying the ebuild to -r999
(In reply to comment #81) > @Lars (comment 77) > The devel of vbox say they cannot however guarantee that OSE will be working > with the binary only extpack. Is that guaranteed by vbox-ose gentoo > mantainers? > > thansk (i'd rather switch to ose and get out of this mess with sdl! :) ) https://github.com/Barthalion/moonrise/blob/master/media-libs/libsdl/libsdl-1.2.15.ebuild This is there for some time. Maybe something blocked you git pull? If you use stable version of gentoo add ~amd64/~x86 to package.keywords. I specially made it for unstable.
(In reply to comment #81) > @Lars (comment 77) > The devel of vbox say they cannot however guarantee that OSE will be working > with the binary only extpack. Is that guaranteed by vbox-ose gentoo > mantainers? > > thansk (i'd rather switch to ose and get out of this mess with sdl! :) ) From my experience with vbox-ose on several machines the USB2 module seems to work properly. I tested VRDP only once but it seemed to work reliable as well. On the other hand I haven't tested the PXE-boot images as I don't know how to test them properly...
This is the oldest most commented bug is the proxy maintainers queue, as well as a bug started in 2010; please evaluate the following options, so we can proceed: 1. Is this issue still present nowadays? 2. Which person or group can do something about this? -> If it it a maintainer, assign to him; drop proxy maintainers. -> If it is games, assign to them (drop p-m); but close as RESOLVED CANTFIX. -> If it is upstream, please close this bug as RESOLVED UPSTREAM. 3. Can a solution for this bug be provided in the Portage tree? -> If so, please indicate as such and let us know status updates. -> If not, please close the bug as RESOLVED WONTFIX; but given that you should probably have a good reason, do RESOLVED CANTFIX. Though as the latter isn't really possible, as it is fixed in overlay. 4. There are complaints in this thread that it is hard to find the existence of fixes in the overlay, can this be documented elsewhere like pkg_postinst? 5. If documentation is a valid enough resolution, then RESOLVED FIXED might work? If no action happens, I suggest we re-evaluate this bug by the end of the year. Thank you very much in advance.
(In reply to Tom Wijsman (TomWij) from comment #86) > This is the oldest most commented bug is the proxy maintainers queue, as > well as a bug started in 2010; please evaluate the following options, so we > can proceed: > > 1. Is this issue still present nowadays? Seems it's resolved... works fine for me with media-libs/libsdl-1.2.15-r4 and app-emulation/virtualbox-bin-4.1.26 But it would be better if somebody else rechecked that.
Sound works for me media-libs/libsdl-1.2.15-r4 app-emulation/virtualbox-bin-4.2.20 kde-base/kde-meta-4.11.4 media-sound/amarok-2.8.0 WinXP in virtualbox , AudioDriver ALSA , AudioController ICH AC97 While playing music in amarok , started vbox , sound from winxp combines with sound from amarok.
Ok, marking this as OBSOLETE, feel free to reopen