Adobe Flash Player 11.0  -  Bug 2968177

Created on Monday, September 12, 2011

Login for more options

Title

[Platform_Linux]Flash player 11 on linux does not record from the "default" alsa sound device.

Description

Please note: This bug was originally reported on: https://bugs.adobe.com/jira/browse/FP-7441 but it seems you are no longer using Jira for bug tracking (which is very confusing as I could not for the life of me work out how to follow up on the above bug report).

The above bug report was closed, but I have tested the two subsequent versions of the plugin released after the above bug was closed and BOTH still suffer from the same problem.

Steps to reproduce:
1. Have a 64 or 32 bit linux system configured to direct alsa's 'default' device to the alsa pulseaudio plugin (as is standard on ALL desktop distributions).
2. Use the test recorder flash package found here: http://code.google.com/p/micrecorder/downloads/detail?name=TestRecorder.zip&can=2&q=
3. Attempt to record sound + authorize the app.
4. Run pavucontrol. The recording should show up under the "Recording" tab. It does not.

Actual Results:

Flash is using the built in hardware directly. When a PA system is used, flash should not enumerate the audio devices and use the hardware, it should just use the default. Not doing so breaks pretty much every desktop linux distribution.

Expected Results:

Flash should use PulseAudio via the alsa-pulse plugin (or better, it should integrate proper PA support directly).

Workaround (if any):

Nah, no workaround, just fix it please :D

Test Configuration

1, For issues related to Video/Audio/Rendering, please upload your system info file.
http://kb2.adobe.com/cps/839/cpsid_83952.html

2, It will be always helpful if you can provide code snippet that can reproduce the issue.

App Language(s) ALL
OS Language(s) ALL
Platform(s) Linux
Browser(s) Unspecified

Notes (25)

  • Duncan Mac-Vicar P.

    6:52:05 AM GMT+00:00 Jan 13, 2014

    For your information, if you use Chromium with the pepper-flash package, it bundles a flash 11.9 which has this bug fixed. I can see "default" in the list of devices now.

  • Duncan Mac-Vicar P.

    6:35:49 AM GMT+00:00 Jan 13, 2014

    Why enumerating devices and using ALSA with working PulseAudio has to be exclusive?

    If you do "aplay -l" or "arec -l" in your system you will get the devices Flash currently uses, which can lead to a device used by pulseaudio. On my system I get:

    If you do "aplay -L" or "arec -L" you list device names, which gives you much better hints, and in a system with PulseAudio, you can see the "default" device, which reroutes to PulseAudio".

    This still gives you the ability to select a device, but makes people using PulseAudio get all the benefits of the sound being routed automatically to the best device.






  • Stephen Hartke

    7:48:12 AM GMT+00:00 Jan 13, 2012

    I also would like a fix for this bug. In the meantime, here is a workaround that enabled me to use Flash plugin 11.1 r102 (64-bit) on Fedora 14 (64-bit):

    uninstall alsa-plugins-pulseaudio (both i686 and x86_64)
    run firefox using: "pasuspender firefox"; this avoids having to remove PulseAudio completely.

    Which device is the primary ALSA device may need to be configured using .asoundrc.

    This is an unsatisfactory solution, since then no other audio works on my computer, but I needed to use Adobe Connect for my job.

  • whwi999

    6:33:44 AM GMT+00:00 Nov 25, 2011

    should we open a new bug report for 11.2 ? this is not fixed right now :-/

  • coling2

    4:04:15 PM GMT+00:00 Sep 29, 2011

    Sorry Jozsef I managed to spell your name wrong in two different ways in that previous reply! I blame my small font and the long day :p

  • coling2

    4:03:04 PM GMT+00:00 Sep 29, 2011

    Hi Jozef,

    A lot of Desktop Environments these days integrate UIs to allow easy selection of audio devices. This also how CoreAudio works with many applications on OSX (you pick your default devices and then all apps use it, unless configured otherwise).

    This is in some ways similar to the "default" device in ALSA. It's designed to capture the user's general preference and if any alsa client app doesn't know any better, it should just use that to ensure it fits in with the users general preference. Any app not doing that is really going to break policy wise. Really individual apps should not be deciding their own policy. I mean, if I'm running a VoIP app I want my sound system to know that when I connect my bluetooth headset, that it's really the most appropriate device to use for this currently active call an move both the streams over to it. It's not really an applications role in the world to decide such things.

    So as far as enumerating the devices goes, I not 100% against it, but by the same token I would also generally discourage it unless there is a really good reason to provide an in-app GUI. I think in the case of Flash on Linux I would argue that there should be no enumeration and just leave it up to the underlying system to set the alsa 'default' device up correctly. You do not offer enumeration for output devices for example, so users are happy to configure this elsewhere, so I don't think input devices should be special cased.

    I've been musing over the topic of providing more metadata to PA from web-based things: It would be really nice if we know the sound was just music or was also associated with video (media.role=music or media.role=video) as policy can configure different devices for each (e.g. my HDMI for video and my Apple Airport for music), however, in the short term, I'd settle for things just working :) (getting such info is very difficult anyway I presume - I mean is there anything internal in flash that knows if it's music vs. video vs. voip?).

    So, to summarise, I would very much recommend as a short term fix to just add 'default' into the enumeration and, obviously, use it by default. That way you lose nothing and return to a fully functioning system on the majority of Desktop linux installs.

    As before Jossef, you would be most welcome to come and chat to us on IRC. Myself (coling) and Arun (Ford_Prefect) are usually not too far away from the IRC channel #pulseaudio on freenode. Some of the Skype guys have hung out there before when they were integrating with PA, all the cool kids do it :D

    All the best.

  • ArunRaghavan

    8:02:54 PM GMT+00:00 Sep 28, 2011

    Jozsef: that (just using 'default' in the PulseAudio case) would work.

    If you were using the native PulseAudio API, you would be able to enumerate the available capture devices as well. Is this an option?

  • Jozsef Vass

    4:01:36 PM GMT+00:00 Sep 28, 2011

    We will use ALSA implementation and not Pulse Audio API. We will change how microphone devices are used from player:
    1. If pulse audio is installed and running, we will expose a single microphone device called "Pulse Audio Microphone." We will open "default" device for capture and playback.
    2. If no pulse audio is present on the system, we will enumerate microphone devices using ALSA API (as currently)

  • lndr2

    3:59:36 AM GMT+00:00 Sep 23, 2011

    Adobe might have poor linux support, but these replies from linux users are embarrassing to the linux community...

  • Jozsef Vass

    2:14:08 PM GMT+00:00 Sep 21, 2011

    Before Flash Player 10.3, on Linux, we have exposed a single microphone called "Linux Microphone" (for flash.media.Microphone.names) and we used the "default" ALSA input device for capture. Users were able to select their device using e.g., pavucontrol. This is, however, completely different behavior from OSX/Windows, where microphone devices are enumerated. So when we added Acoustic Echo Cancellation, we have decided to add microphone device selection as well. We enumerate available microphone devices (using ALSA API such as snd_card_next, snd_ctl_card_info, etc.), expose device names to flash.media.Microphone.names, and open hw:0, hw:1, etc. microphone device based on user selection. There is no need for the user to run other software to select input device.

    This was a definite change in behavior, but I do not think it is a bug and we have properly documented. I am open to work with you and improve microphone selection on Linux. Maybe all we need is to add a "default" device.

  • Gogalinator

    3:29:41 AM GMT+00:00 Sep 17, 2011

    i think this bug is not important because users of linux about 1% http://goo.gl/jOwPk

  • Konstantin1345

    1:18:50 PM GMT+00:00 Sep 16, 2011

    One more request for fix. At the moment flash experience on Linux isn't that perfect. One more step and we will go on with html5 without looking back.

  • Konstantin1345

    1:18:01 PM GMT+00:00 Sep 16, 2011

    One more request for fix. At the moment flash experience on Linux isn't that perfect. One more step and we will go on with html5 without looking back.

  • AnonZombi

    9:36:12 AM GMT+00:00 Sep 16, 2011

    This must be addressed. Adobe has really had a horrible track of development, especially on the Linux platform. While your at it fix the bug that makes flash peg your CPU no matter how fast it is. You guys are a disgrace.

  • Ping Huang

    3:01:20 AM GMT+00:00 Sep 16, 2011

    Hi all,
    1, I just published a piece of info in our bug template to reflect our process to avoid future confusion. Bug is set as ToTrack or Closed as defer means we have reproduced the issue, but couldn't get it fixed in current release. We track follow up messages and votes info for each (open & closed)bug.

    2, The reason that we couldn't address this issue is that we're too closed to our current FP11 release, thus it will be too risky to take any further changes. I will appreciate your understanding. This issue has been listed in our next quarterly release scope. We will update you with our internal progress for this issue.
    Thanks for your patience.

  • HappyCerberus

    1:57:30 AM GMT+00:00 Sep 16, 2011

    I have just forwarded this bug to our management and recommended that the Adobe stance on this bug should be considered when renewing our Adobe Connect license. Have a nice day.

  • Bing Cai

    11:47:58 PM GMT+00:00 Sep 15, 2011

    Hi Coling2,
    Your consideration and comments are really important to us.
    Yes, we can reproduce it and it's important and serious sound related bug to Linux platform, but we don't have enough time to fix it right now, Close/Defer it didn't mean just close it and we'll never touch it again,that's because we have internal system to track this bug. Sorry for the confusion, and your responses to this bug will speed up the fix process, that's much appreciate.

  • satgarcia

    11:05:23 PM GMT+00:00 Sep 15, 2011

    Well, if a bug which results in breaking the entire sound system is considered low priority, then I don't want to imagine what the other bugs are.

  • tmarmo

    7:21:36 PM GMT+00:00 Sep 15, 2011

    You've got to be kidding. That is not a response but an insult to the entire linux community. Continually you've played down the amount of users who actively use linux, the efforts they make to improve not only linux itself but the products and software that others provide. I find this to be a totally unacceptable and unprofessional response which does not surprise coming from your company.

  • creat79

    2:29:54 PM GMT+00:00 Sep 15, 2011

    This bug is of critical importance and should be re-opened until it's fixed.

  • creat79

    2:29:00 PM GMT+00:00 Sep 15, 2011

    This bug is of critical importance and should be re-opened until it's fixed.

  • zeenix147

    2:01:38 PM GMT+00:00 Sep 15, 2011

    I don't understand two things:

    1. If you are working on this, why would you close it (even if very slow because of low priority)? Is it possible that you are doing it because a bug like this will reflect badly on you if its kept open for too long?

    2. One of the developer of pulseaudio himself is telling your about the extremely critical importance of this issue so how can you prioritize anything above this bug? Could you point to some bug(s) that you have prioritized over this bug?

    For what its worth, everyone that reads planet.gnome.org knows about this bug and believe me you are looking very bad in the eyes of at least several thousand people and further insistance on keeping it closed will only worsen that situation.

  • coling2

    5:10:45 AM GMT+00:00 Sep 15, 2011

    I'm sorry but it's absolutely unacceptable that you closed a bug that you've just acknowledged.

    This is totally against proper procedure.

    I am at the front line of support for audio on linux and your actions here are going to cause me significant headaches. I will be writing to your CEO about this as I find these actions totally disrespectful and also completely ignorant to the seriousness of the problem.

    I *strongly* recommend not shipping any linux version until this bug is fixed as it's a critical problem on the vast majority of installed systems.

    If you do not you'll end up causing me a *lot* of extra work in support and I will be very, very unhappy about that.

    I would also like to know your policy on prioritisation. Why is this bug considered lower priority? It causes breakage of the whole sound system because YOUR app is misbehaving. That's not low priority, that's data loss (what if a VOIP call comes in when some web pages is open that records sound?). Depriving me the ability to use voip apps is data loss, plain and simple and data loss bugs are typically of the highest priority.

    So in short, please do not close bugs when they have been acknowledged and do not dismiss matters when the very people who run systems are reaching out to you to offer support. I am not a typical user or customer, I am the maintainer of a key component of the default sound stack on Linux!! Please treat me with at least a modicum of respect.

    In addition, why was I not emailed when this bug was updated? And why can I not reopen bugs?

  • Bing Cai

    8:36:37 PM GMT+00:00 Sep 12, 2011

    Dear Customer,

    We can reproduced this issue and we're working this issue, but from our perspective, we don't have enough time to fix all bugs, we set priority to each bugs and this bug has a lower priority and won't be fixed quickly, so thanks for your understanding.

  • coling2

    2:40:44 AM GMT+00:00 Sep 12, 2011

    I am upstream PulseAudio developer and maintainer. I have helped other software developers (including Skype) fix their systems to work well with PulseAudio and I offer the same to yourselves. I do not know if you have ever engaged with us, but please do. We are very approachable and will help out whenever we can. Flash has got a very poor reputation due to it often "hogging" sound devices and generally breaking peoples desktops. I would very much like to help you change that, if you are willing to engage.

Duplicate ID
Reported By coling2

Status

State Closed
Status Deferred
Reason NotEnoughTime

Importance

Priority 4-Very High
Frequency All users will encounter
Failure Type Data Loss
Product Area Audio

Build

Found In Build 11.0.1.129(beta)
Fixed In Build

Attachments (0)

No Files Attached

Votes (23)

  • Duncan Mac-Vicar P.

    6:36:26 AM GMT+00:00 Jan 13, 2014

    Broken conferencing (OpenMeetings)

  • a.leach

    7:29:45 AM GMT+00:00 Nov 19, 2013

    This is a long standing bug now and will be a driving factor in users choosing Windows or OSX over Linux for their desktop environments. This is an insult to all Linux developers, who contribute their free time to its development and further evidence towards Adobe's greed, lack of morality and Flash's inefficacy.

  • sphakka

    2:33:05 AM GMT+00:00 Jan 26, 2012

    This bug prevents accessing video interview sites for job seekers. Linux people are losing important job opportunities! Please fix it.

  • Leonardo Afonso

    9:25:37 AM GMT+00:00 Nov 18, 2011

    This bug prevents effective use of a web learning platform at my employee

  • lelikDark

    10:23:58 PM GMT+00:00 Oct 10, 2011

    Hello Correct the error please, so as the sound device by default does not work, we can not use any audio device other than a microphone. Our business suffers.

  • FernandoLozano

    5:35:13 PM GMT+00:00 Oct 5, 2011

    This bug prevents effective use of a web learning platform at my employee

  • billf5

    12:23:43 PM GMT+00:00 Sep 23, 2011

    This bug will prevent me from use Flash based conferencing services at home and at work, forcing me to look for non-flash based alternatives.

    How can we, the consumers of this product, enable Adobe to put more resources into Linux support and development ?

  • Artic Ice

    1:41:06 PM GMT+00:00 Sep 18, 2011

    Please fix. Bug also present in 10.3, #2967168.

  • Konstantin1345

    1:19:33 PM GMT+00:00 Sep 16, 2011

    One more request for fix. At the moment flash experience on Linux isn't that perfect. One more step and we will go on with html5 without looking back.

  • AnonZombi

    9:35:26 AM GMT+00:00 Sep 16, 2011

    This must be addressed. Adobe has really had a horrible track of development, especially on the Linux platform. While your at it fix the bug that makes flash peg your CPU no matter how fast it is. You guys are a disgrace.

  • RussianNeuroMancer

    7:15:02 AM GMT+00:00 Sep 16, 2011

    > Bug is set as ToTrack or Closed as defer means we have reproduced the issue, but couldn't get it fixed in current release.

    Then keep it open until this bug get fix.

  • Daniel A. Cordeiro

    6:03:14 AM GMT+00:00 Sep 16, 2011

    Please consider "coling2" offer to help better integrating flash with PulseAudio.

  • igman

    2:03:43 AM GMT+00:00 Sep 16, 2011

    Please fix this issue as soon as possible.

  • andybz

    2:03:03 AM GMT+00:00 Sep 16, 2011

    Are you guys serious? Do you really care that little about Linux users that you'd actually close the bug? Bring on HTML5!

  • houqp

    12:33:21 AM GMT+00:00 Sep 16, 2011

    This bug affects all of us

  • satgarcia

    11:05:16 PM GMT+00:00 Sep 15, 2011

    Please fix. Linux is important. This is an insult.

  • DoctorOwl

    5:59:33 PM GMT+00:00 Sep 15, 2011

    It should be self-evident.

  • soliac

    5:19:08 PM GMT+00:00 Sep 15, 2011

    This makes flash player incompatible with modern linux distributions! It breaks VOIP functionality, indeed any situation where the user tries to record audio when flash is using the microphone.

  • snagglepants

    3:10:19 PM GMT+00:00 Sep 15, 2011

    I've also been affected by this. Arch Linux. Please consider taking the Pulse Audio devs up on their offer, it'd be greatly appreciated!

  • nil.gradisnik

    11:16:56 AM GMT+00:00 Sep 15, 2011

    This is simply unacceptable.
    I'm a developer of a VoIP web application vox.io and this bug will most definitely break our functionality, rendering it useless for all our Linux users.

    Please reconsider the status of this bug.

  • sdejean

    10:41:40 AM GMT+00:00 Sep 15, 2011

    I am experiencing the same issue on Ubuntu 11.04, disappointed this bug was closed without a comment on why.

  • whwi999

    6:29:38 AM GMT+00:00 Sep 15, 2011

    breaks all linux distros audio

  • ArunRaghavan

    5:45:18 AM GMT+00:00 Sep 15, 2011

    This is pretty fundamental breakage, especially since PulseAudio is now pretty much a standard part of the stack on all major Linux distributions.

Your session has expired! Click to login
Current form data will be preserved

Cancel