[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Another update, another reboot, no sound!

On Thu, 07.05.09 16:33, Dimi Paun (dimi lattica com) wrote:

> This is getting ridiculous!

Oh my. 

> I had running sound, and today I've updated my system.
> Right away, my sound was b0rken:
>   - no sound from Skype, in any configuration imaginable
>     (even when ran through pasuspender)
>   - no sound from Flash in Firefox
>   - no sound from VirtualBox, even though I was seeing
>     the stream listed under "Playback" tab in PA's VC
>   - however, I was getting sound from Rhythmbox!

Ah, so closed-source software we don't ship is broken -- Proper Free
Software we ship works? Quelle surprise! And it's our fault of course,

> It turns out that I had to run "alsamixer" manually _again_
> because the master volume was, logically, set to zero. And
> this after filling a bug about this:
>     https://bugzilla.redhat.com/show_bug.cgi?id=493790
> The bug was marked as fixed.

Maybe that specific bug was fixed in the packages. Have you made sure
you are running the updated packages?

Have you filed a bug about your new issue after you made sure you are
running the newest packages?

> Sure enough, even after fixing the master volume, I still:
>   - have no sound from Skype in any imaginable combination,
>     even if it was working fine before (and I have not
>     changed the version of Skype that I use)
>   - no sound out of VirtualBox, even if it was working before

We don't ship that software. It's not what I test my stuff with. Also,
my interest in working on software that we don't ship or is even is
impossible to debug (due to its closed source nature) is rather

Do those programs appear in g-v-c? Are they properly unmuted there?

> I've tried filing bugs, it doesn't help -- the rate of breakage
> is way faster than I can file bugs (not to mention that filing
> bugs is too sluggish for words). 

Hmm, let me see, that other issue you filed 2009-04-03 and this one is
already too fast for you to file? I mean, I really don't want to
burden you too much. From now on I'll try to make sure that bugs in
software I work on for *development* distributions only appears at a
rate of 1 every *two* months, to make sure it doesn't get too fast for
you to follow.

> Something is Just Plain Wrong (TM). WTH is going on? How can the
> situation be improved? I've just lost 1h right now trying to deal
> with this problem, in the middle of my work day -- this is not
> sustainable.

I mean, seriously. You are complaining that you have to file more than
one bug per month and are using a development distribution! Calm down!

Also, there's always the option to reopen a bug when you think it is
not fixed properly. This options was added because sometimes things
like this happen.

Calm down!


Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]