On Wed, Jun 1, 2011 at 5:05 AM, Michel Hermier <[email protected]> wrote:
>> On Sun, May 29, 2011 at 06:10:51PM +0300, Marius Cirsta
>> <[email protected]> wrote:
>>> This in turn causes phonon to not work and fail when KDE or KDE apps
>>> try to play sound through it. One unfortunate side effect of this is
>>> bug FS#4423  where shutdown and restart fail in KDE because of this.
>>>
>>> A default backend must be present for phonon to work and I've chosen
>>> the xine one as it was the first one on Unix and is more stable. Added
>>> it asa rodepends to avoid a circular dependency issue.
>>>
>>> Attached is the git patch.
>>>
>>> P.S.  Michel I apologize for cc-ing you but I thought it might be of
>>> interest as we've talked about this before.
>>
>> Actually you did not CC him. :)
>>
>> I agree with the patch in general, thanks for doing it. Two concerns:
>>
>> - Michel, can you please ACK this patch? IIRC last time you mentioned
>>   you're rather fix KDE's code to handle missing phonon backends
>>   gracefully. That sounds fine to me as well, of you have a patch (since
>>   Marius *has* a patch.)
>
> This is not the complicated part, this is the easy fix, and I don't like it.
> I really need to take so time to investigate this issue... before I take a
> real decisions.
>
>> - Before applying it, phonon-backend-xine should be moved to main to
>>   prevent testsuite breakage.
>
>

 So what do you have against this fix ? And what other plan do you
have to fix the fact that phonon does indeed need a backend and it
simply won't work without one?  That's the way it was designed. Even
if we do manage to get everything to work properly it won't play any
sound without a backend.

 Normally I'd have nothing against taking time to analyze the
situation and find a fix but the fact is that FS#4423 has been open
for almost 4 months now , with no fix , nothing.

 Can't we just fix it this way for now ? There's no reason a better
fix can't be added at a later date. Also if there's something
seriously wrong with this fix we'll have time to spot the problems
before the stable release.

> _______________________________________________
> Frugalware-devel mailing list
> [email protected]
> http://frugalware.org/mailman/listinfo/frugalware-devel
>
_______________________________________________
Frugalware-devel mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-devel

Reply via email to