Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-12 Thread Brad Rogers
On Tue, 11 Sep 2018 21:24:42 -0400 Ric Moore wrote: Hello Ric, >Works a charm for me, and has for years, BUT every once in awhile As it does for many, I'm sure. >the volume levels back up to 100%. Pulse rides on top of alsa, so alsa And that's a problem. Now, if sound goes wrong there are

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-11 Thread Ric Moore
On 09/10/2018 08:27 AM, Brad Rogers wrote: On Mon, 10 Sep 2018 11:53:01 + (UTC) Curt wrote: Hello Curt, So uninstall it then in that unfortunate case--with extreme prejudice Time. Oh, and I can't be arsed to try PA in the first place. :-) Or are we dealing with the supernatural

Re: [beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread rhkramer
On Monday, September 10, 2018 09:37:28 AM Thomas Schmitt wrote: > I could offer my program cdrskin as real example. > It is a cdrecord/wodim compatibility wrapper but exceeds both when it > comes to DVD and BD media. Thanks, for: * the useful example, and * changing the Subject: line

Re: [beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread Reco
Hi. On Mon, Sep 10, 2018 at 03:37:28PM +0200, Thomas Schmitt wrote: > Hi, > > Reco wrote: > > > It's the usual. A compatibility wrapper can never exceed the original. > > rhkra...@gmail.com wrote: > > Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how > > to

[beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread Thomas Schmitt
Hi, Reco wrote: > > It's the usual. A compatibility wrapper can never exceed the original. rhkra...@gmail.com wrote: > Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how > to say what I want to say, let me try a made-up example. I could offer my program cdrskin as real

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread Brad Rogers
On Mon, 10 Sep 2018 11:53:01 + (UTC) Curt wrote: Hello Curt, >So uninstall it then in that unfortunate case--with extreme prejudice Time. Oh, and I can't be arsed to try PA in the first place. :-) >Or are we dealing with the supernatural here (software from Hell)? I'm wary because of

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread Curt
On 2018-09-10, Brad Rogers wrote: > > The machine it does affect is the one that I routinely use, which has > been in use for longer than PA has been around. I /could/ install PA, > but am reluctant to do so, since sound works here ATM and I'm concerned > that installing PA may cause issues for

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread rhkramer
On Monday, September 10, 2018 05:49:01 AM Reco wrote: > It's the usual. A compatibility wrapper can never exceed the original. Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how to say what I want to say, let me try a made-up example. Suppose some piece of software is

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread Brad Rogers
On Mon, 10 Sep 2018 12:49:01 +0300 Reco wrote: Hello Reco, >On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote: >> I've not been running apulse long, but so far, no crashes in Ff 62. >So upstream lies then. To quote apulse's README.md: Maybe, maybe not. It's only been a couple of

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread Reco
Hi. On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote: > On Sun, 9 Sep 2018 11:43:39 +0300 > Reco wrote: > > Hello Reco, > > >Moreover, apulse causes Firefox to crash since Firefox version 58, as > > I've not been running apulse long, but so far, no crashes in Ff 62. So

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-10 Thread Brad Rogers
On Sun, 9 Sep 2018 11:43:39 +0300 Reco wrote: Hello Reco, >Moreover, apulse causes Firefox to crash since Firefox version 58, as I've not been running apulse long, but so far, no crashes in Ff 62. >apulse is a kludge, not a solution. That's as may be (I don't have an opinion either way).

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-09 Thread deloptes
Rob van der Putten wrote: > Does anyone know why ALSA is no longer supported? You mean supported by Firefox? I guess they decided PA is more easy to implement as default interface ... whatever underlaying audio system you use. I still could not understand why, but this seems irreversible.

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-09 Thread Nicolas George
to...@tuxteam.de (2018-09-09): > Personally, I couldn't care less: I consider my browser's inability > to make sounds a welcome *feature*, so not having Pulse (which is my > default) just naturally takes care of that. Same for me. And apulse seems to work for me anyway. > Given the amount of

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-09 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Sep 09, 2018 at 10:24:30AM +0200, Rob van der Putten wrote: > Hi there > > > Note: A reply in bugs failed. > > On 09/09/18 10:08, Marco Lucidi wrote: > > > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault > > wrote: > > > Unfortunately

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-09 Thread Reco
Hi. On Sun, Sep 09, 2018 at 10:24:30AM +0200, Rob van der Putten wrote: > Hi there > > > Note: A reply in bugs failed. > > On 09/09/18 10:08, Marco Lucidi wrote: > > > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault > > wrote: > > > Unfortunately AIUI upstream has stopped

Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-09 Thread Rob van der Putten
Hi there Note: A reply in bugs failed. On 09/09/18 10:08, Marco Lucidi wrote: > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault > wrote: > > Unfortunately AIUI upstream has stopped supporting ALSA, so we are stuck > > with pulseaudio for firefox. > > Is there any particular reason for