I'm the original reporter of this bug thread.
I have to say, I'm completely dissatisfied so far. Every proposal has
been to effectively kick this downrange and make it someone else's
problem, and I'm -particularly- unhappy that this is viewed as a
window manager issue! It means the (a) behavior
Yes, I agree re part 3---safer to leave it in as long as metacity claims
responsibility. (But it has no business claiming responsibility---leave
that to PulseAudio.)
We haven't heard yet about getting this bug punted to the metacity
folks, so it may be time take more direct action in letting them
Okay, for anyone who's trying to restore the pre-Karmic behavior of
beeping, here's what to do. It will give you old-style motherboard
beeps when you hit rubout at an empty shell prompt in gnome-terminal or
at an empty password prompt during gdm login; it will make xkbbell work;
all rate-limiting
Oh btw, someone else will to have to verify if the patch is well-formed;
I applied it by hand, since I was poking around to verify each piece.
--
System beep broken in Karmic despite heroic efforts to fix it
https://bugs.launchpad.net/bugs/486154
You received this bug notification because you are
Confirmed---your patch fixes the issue. Now I can migrate to Karmic
without going mad. (I'll make a post showing all the extant bugs & what
fixes them, since this is but one part of all the bell lossage we've
discovered, but this is certainly the most-annoying one and the one that
got us started.
I can't quite reproduce your it-must-be-metacity results, because when
-I- try compiz, I just lose X bells completely. BUT---metacity is
-definitely- doing something wacky. Read on.
Starting from metacity, xkbbell (and rubout at an empty shell prompt)
"work" in the same not-really-working manner
Yes, I had the same behavior with "killall metacity" (which I was using because
I was recompiling it with various things commented out). I'll run some compiz
tests and make sure I can reproduce your results. I think there -is- some
negotiation going on, and I'm not sure what happens if a proce
Aha! You've done -exactly- the debugging I was thinking of asking you
to do... :) [More, even, since I didn't realize you could easily try
out 9.04; I don't have any 9.04 systems and didn't really want to
install one just for testing, though i guess I could. I'd assumed this
was broken before th
I'm beginning to wonder if this might be a gtk issue. Or gdm. Or gdk.
Does anyone know how to tell which application might have called
XkbSelectEvents or XkbChangeEnabledControls? Can I ask X somehow?
For the moment, I'm reduced to, e.g., doing "apt-get --dry-run build-dep
gdm", noting which p
Oy.
I know this is probably going to be an unpopular discovery, but I am no
longer sure this is necessarily a metacity bug. The problem is, then,
whose bug -is- it?
I just spent a couple hours hacking around in the metacity source code
doing things like commenting out XkbSelectEvents and
XkbChan
I've rerun all my tests. I've attached a table and legends for it, since no
doubt it would
otherwise be smashed by the automatic reformatting done by launchpad (is there
any way to
turn that off?).
Note that EVERYTHING works fine in Hoary, Dapper, and Breezy. I did not test
9.04.
But 9.10 has
Robert: Re the rmmod/modprobe fandango I'm doing: I've done a bunch of
testing (my next post will detail it), but I'm pretty sure what's going
on with rmmod/modprobe is simply a kernel regression---if pcspkr is
loaded too early, it doesn't work correctly. So if it's blacklisted,
and then loaded
Robert: Thanks for the summary. I'm going to prepare a little table
for the studio audience to try to make things clearer, especially since
you correctly pointed out in comment #27 that there's ambiguity over
whether I'm talking about bell.ogg or the squarewave beep coming out of
line-out (whoops
[IG: I don't understand your comments re the bell working in metacity
-instead of- compiz. If that's true, you're talking about something
different than we are. You should also strive to be more precise in
your description. For example, when you say "system bell", I'm not sure
if you're talking
Thanks! I just put a pointer in your bug back to here, so hopefully
people will see both and figure out if we're talking about the same
thing.
--
System beep broken in Karmic despite heroic efforts to fix it
https://bugs.launchpad.net/bugs/486154
You received this bug notification because you ar
Daniel: If this bug is truly independent of PulseAudio, then why does
renaming /usr/share/sounds/ubuntu/stereo/bell.ogg change the behavior?
If your argument is that libcanberra is looking at that file, then why
is it necessary to remove a -PA- cache file to fix the bell after
renaming the file ba
16 matches
Mail list logo
