Comment 9 for bug 486154

Robert: It looks like the reason module-x11-bell isn't loaded by default is because it's commented out in /etc/pulse/default.pa (along with the load-sample mentioning it near the top of that file). Presumably, uncommenting and restarting pulse (or just rebooting) would load it. But of course, unless pulse can know to beep the -system- beeper (I don't know if it can), this doesn't necessarily help me (or you). Though if loading that -still- means that xkbbeep (etc) don't produce any output on an audio-out jack (or wherever pulse is trying to route high-quality sound), then it would mean that gnome/metacity/pulse is just throwing away the event entirely, which it could well be doing---at one point in my testing, I tried hooking a speaker up to my line-out, and even though mplayer can certainly play music out that, I never heard the bell come out of that. (And then I unhooked it, so most of my testing hasn't had anything connected there.)