[pulseaudio-tickets] [PulseAudio] #439: early load of module-x11-bell leaves standard X bell active too

[PulseAudio]

#439: early load of module-x11-bell leaves standard X bell active too
---------------------------+------------------------------------------------
  Reporter:  liblit        |       Owner:  lennart
      Type:  defect        |      Status:  new    
  Priority:  normal        |   Milestone:         
 Component:  module-x11-*  |    Severity:  normal 
Resolution:                |    Keywords:         
---------------------------+------------------------------------------------
Comment (by liblit):

 I think it unlikely that some other program is also catching the X11 bell
 events.  I am running compiz-fusion, not metacity, and I do not believe I
 have any special effects wired up to the bell.  More importantly, observe
 that the standard bell is no longer played after I unload and reload
 `module-x11-bell` later in the session.  Presumably if some other program
 were catching the X11 bell events, it would continue to do so even after
 that module reload?

 Is there some sort of race condition here?  Perhaps `module-x11-bell`
 racing with some other bell-event-catching program, or even racing with
 the X server itself?  Is there some way for me to query who's catching the
 bell at any given moment?  That would let me answer your original question
 more authoritatively.

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