[pulseaudio-tickets] [PulseAudio] #639: Phonon error-messages about not working device after KDE-login.

PulseAudio trac-noreply at tango.0pointer.de
Mon Oct 5 08:38:38 PDT 2009


#639: Phonon error-messages about not working device after KDE-login.
------------------------+---------------------------------------------------
  Reporter:  COMER352L  |       Owner:  lennart 
      Type:  defect     |      Status:  reopened
 Milestone:             |   Component:  daemon  
Resolution:             |    Keywords:          
------------------------+---------------------------------------------------
Changes (by COMER352L):

  * status:  closed => reopened
  * resolution:  elsewhere =>


Comment:

 Replying to [comment:1 coling]:
 > This is purely an issue with Phonon.
 > ...
 > In Mandriva we patch phonon to hide all real devices and show only
 PulseAudio output as the only valid option (when pulse is in use, this
 config just doesn't make sense). This avoids this whole issue as phonon no
 longer tries to access the h/w directly but instead goes via the pulse
 layer of gstreamer (our default phonon engine). The xine pulseaudio
 support is sadly lacking so I wouldn't recommend using the xine phonon
 engine on this kind of setup.
 > ...
 > Really the bug is "phonon should not try and perform direct hardware
 access when pulseaudio is in use".

 Can't believe what I read... this attitude is kiddy ! I know you believe
 PulseAudio is superior but this is not a battle PulseAudio vs. Phonon !
 Instead of trying to "replace" other sound systems by forcing users to use
 PulseAudio only, you should fix nasty bugs like this. The better it works,
 the less people will use other sound-systems.
 I'm using Phonon, simply because it currently works much better for me at
 the moment. Because of this issue, I had to ban PulseAudio from my system
 (like many others !).

 Back to the facts: I reopened this report because I think you
 misunderstood me:
 I'm not using PulseAudio with Phonon (no plugins, backends... installed
 !), therefore it's NOT a phonon-bug. Running the daemon only already
 causes the problem (that's what I meant with "pure presence"). It
 definitely shouldn't affect Phonon (or other sound-systems).

 Still present in 9.18.

 Replying to [comment:1 coling]:
 > I'm working towards better support in Phonon, but there is nothing we
 should do at this end.

 Again: I'm not talking about phonon-integration !

-- 
Ticket URL: <http://pulseaudio.org/ticket/639#comment:2>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server


More information about the pulseaudio-bugs mailing list