Wontfix.
** Changed in: metacity (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486154
Title:
System beep broken in Karmic despite heroic efforts to fix it
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-xenial (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486154
Tit
Okay, I submitted bug #1599599 for the same problem on Ubuntu 16.04 Xenial
Xerus.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486154
Tit
** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486154
Title:
System beep broken in Karmic despite heroic efforts
Hi all,
It is six years later and this exact problem is back with Ubuntu 16.04 Xenial
Xerus.
I unblacklisted pcspkr and loaded the module, plus the overwhelming multitude
of other steps.
The "beep" command works and "echo blahblah | wall" also works, "but
echo -e '\a'" and "printf '\a'" do not
I am on Lubuntu 12.04 and beep isn't working for me, so I am not getting
notifies on highlights from WeeChat with beep script.
I have
1. removed pcspkr from modprobe blacklist
2. modprobed pcspkr
3. rebooted
4. ensured that beep isn't muted in alsamixer
5. I have ran "xset b on" multiple times and
On 04/17/2012 01:57 PM, John Vivirito wrote:
> This is a problem again. it was working until last week or so. I
> reinstalled than updated and it stopped working, anything i can do to
> help with this?
Your first step should be to determine if this bug is your problem or
not. This bug is specifi
This is a problem again. it was working until last week or so. I
reinstalled than updated and it stopped working, anything i can do to
help with this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/4861
> the system bell should work in metacity without issue
Well, except for the issue that we've spent 18 months and 89 comments
discussing: You can't turn off the libcanberra bell handling without
patching Metacity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
In a default natty install, the system bell should work in metacity
without issue, i.e a system bell is triggered, and metacity calls
libcanberra functions to play the system bell sound event.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Thomas, Pete:
Problems with the system bell are subtle and strongly dependent on what
exactly you are trying to do. One of these factors is the window
manager. This bug is primarily focused on getting the system bell
working under Metacity. gconf twiddling *may* be necessary in this
case; Pulse
Pete, thanks for the information.
To summarize what I now know
There are several separate issues. One is the traditional square-wave
beep function. Many people say that it is necessary to:
* Un-blacklist the pcspkr kernel module and load it.
However, I have just discovered that this mod
Thomas, I don't think you need to run gconf-editor at all. This is what
does it for me on Natty 11.04:
/usr/bin/pactl remove-sample bell.ogg
/usr/bin/pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg
bell.ogg
/usr/bin/xset b on
/usr/bin/xset b 100
Plug this into a session
I've filed another bug about problems with the system bell in Unity
(#769314). Basically those problems are the same as in Compiz discussed
here. So let's talk about Compiz problems over there and keep the
Metacity discussion here.
--
You received this bug notification because you are a member
We shouldn't depend on upstream fixing this by removing
behavior that upstream regards as a feature.
It would be nice if upstream made their feature easier to disable.
But we shouldn't wait for them to do that, either, before fixing
the problem in Ubuntu.
--
You received this bug notification be
Addendum. Even after doing what I just described (above, reply #81), I
find that after reboot sometimes beeping doesn't work until I switch
window managers between metacity and compiz. :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
To re-enable the terminal bell on my ThinkPad X61 running Ubuntu 10.10 I took
the following actions suggested above:
* Un-blacklist pcspkr as described above, then either reboot or modprobe
pcspkr.
* On the terminal window, tick "Edit | Profile Preferences | General |
Terminal bell"
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
Two non-reporter comments, including none from metacity developers, over
13 months may be called many things, but I wouldn't call it "being
discussed." Let's be honest - upstream is not fixing this bug. Ubuntu
is apparently not fixing this bug. Let's stop misleading people into
thinking this wil
Being discussed in the upstream bug (where it should be applied first),
unassigning.
** Changed in: metacity (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I think until this is fixed in a sensible way upstream, there isn't a
safe way to backport fixes to earlier releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486154
Title:
System beep broken i
Thanks for the patches and the discussion on this. Can someone from the
Ubuntu Desktop team follow this patch through to the end?
** Changed in: libcanberra (Ubuntu)
Status: New => Invalid
** Changed in: metacity (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Team (canonical-des
>Is there something I'm missing that makes having the window managers be
responsible for the system bell so attractive? And >regardless, should
the discussion continue here or in a new bug for "Coherent handling of
the system bell"?
I think the latter is important, especially on servers that have
Michael and Chris, thanks for taking a look at this. But I still don't
understand why the system bell should be tied to the window manager. It
seems to me a strange connection that leads to silly bugs like #430203.
IMHO, the obvious solution is to let Pulse Audio handle the beep and
leave the win
The patch looks sane to me (and I've mentioned as much on the upstream
bug), but as you've noted it will need some system-integration work to
avoid regressions for the people who want their bell to ding rather than
PC bleep.
To that end, I brought this up with Luke Yelavich (the main Ubuntu audio
Thanks a lot Robert for looking into this problem and for your patch. I
do not feel comfortable enough with the code to judge if that will not
have regresions. It would be great if upstream would comment. I noticed
that you forward it to the gnome bugzilla (thanks for this). But it
looks like upstr
This will load the bell.ogg sample for pulseaudio. My guess is that
there is some disconnect between the alert settings in "Sound
Preferences" and actually doing the load in gnome.
/usr/bin/pactl upload-sample
/usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg
--
System beep broken in Ka
On 10/11/2010 11:58 AM, Thomas Troesch wrote:
> When I get the system bell, I have no control over the volume, and the
> duration parameter 'beeps' twice as long as xset q would indicate. Is
> this the same behavior you are getting?
I suspect that this may be related to bug #280767. I've noticed
Thank you all for your incredible effort. I have had success with the
instructions in these comments.
The system bell is very important for me as well. I have scripts and
programs that run when the user is not sitting at the computer or even
looking at it, and in a relatively noisy environment.
Nic, thanks for figuring out that Pulse Audio was the thing breaking the
bell in Compiz. I couldn't believe that I should have to restart Compiz
to restore the bell, and you showed that I don't.
Armed with this knowledge, I went looking around for where Pulse Audio
loads its modules. The X11 one
Having struggled with this for ages, just thought I'd post the
(extremely hacky!) workaround which finally got the system bell working
normally for me, in case it's of any help to anyone. This is for Lucid.
There were two issues for me: first, the fact that the pcspkr kernel
module (when removed fr
** Changed in: metacity
Importance: Unknown => Medium
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
A week ago I wrote about un-blacklisting the module. But even with the
pcspkr module loaded (lsmod shows it), most of the time there's no beep,
either in or out of X. The pcspkr module seems very flaky in Ubuntu
kernels. I've never figured out why; if I build my own kernel, pcspkr
works fine, wheth
Update for Lucid, for which I'm sure everyone has been waiting with
bated breath.
pcspkr is still blacklisted. See the above comment for details.
Metacity behaves the same way as it did in Karmic, trapping all system
bell events and using it's own playback capabilities. This is despite
the fact
A lot of the discussion in this bug has to do with metacity and pulse, but for
people who don't use gnome, metacity, pulse or any of that stuff, and just want
their pcspkr module to beep when asked under lucid, I just posted a blog
article:
http://shallowsky.com/blog/linux/kernel/pcspkr-lucid.ht
** Changed in: metacity (Ubuntu)
Status: Confirmed => Triaged
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: metacity
Status: Unknown => New
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
This was probably unspeakably gauche of me, but I removed the -needswork
tag until someone can explain to me why we would want metacity mucking
about with the audible system bell events. This bug (and system bell
events in general) obviously does still need work, but I just don't see
what more is
Dmitrijs, metacity is categorised as desktop, as indeed is audio in
general - I don't see anything here for the foundations team. I've
subscribed canonical-desktop-team and unsubscribed canonical-
foundations.
--
System beep broken in Karmic despite heroic efforts to fix it
https://bugs.launchpa
Just to confirm my previous assertion, I installed the Lucid beta on a virtual
machine. I applied my patch [1], restarted metacity, and unloaded and reloaded
Pulse Audio's module-x11-bell [2]. System bells rang the same bell.ogg sound
file, but through Pulse Audio. Additionally, I could now s
Dmitrijs Ledkovs wrote:
> I'm part of Ubuntu Reviewers team. Your patch is good to brute-force
> revert the change but what about people who want both options and switch
> between the two behavior? As discussed in this long bug report it's not
> possible yet due to many issues raised and the patch
I'm part of Ubuntu Reviewers team. Your patch is good to brute-force
revert the change but what about people who want both options and switch
between the two behavior? As discussed in this long bug report it's not
possible yet due to many issues raised and the patch doesn't bring
configurable behav
** Tags added: patch
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
** Changed in: metacity (Ubuntu)
Importance: Undecided => Medium
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Thank you thank you thank you Grondr and Robert for giving some respite
to people who are suffering from this horrible bug.
This problem is highly annoying to me. The initial reason for neutering
the pc speaker was that besides it being "outdated" you had to grovel
through 8 miles of innards to ge
I've edited the description to try to give a better overview of our
current understanding of the various problems in this bug. Please add
anything I left out.
Also, I nominated this for Lucid because, hey, why not?
** Description changed:
- In a fully up-to-date AMD64 Karmic on an MSI MS-7511 a
Robert, I think that you have gone above and beyond at this point. At
least at this point, the maintainers can try out your patches and take a
good look at them to see if they want to integrate it. The best bug
reports are the ones with patches! Thank you for making Ubuntu better!
--
System be
** Branch linked: lp:~rschroll/metacity/system-bell
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I've created a branch of metacity with the changes from the attached
patch, and requested a merge with master, as that seems to be what I was
supposed to do (https://wiki.ubuntu.com/SponsorshipProcess). For
purposes of cross-referencing, here's the merge request:
https://edge.launchpad.net/~rschro
Since there's been no action from the Ubuntu maintainers on this, I
finally got around to reporting this upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=607906 Please take a look
and add anything that I forgot.
** Bug watch added: GNOME Bug Tracker #607906
https://bugzilla.gnome.org/show_
I have flagged down Daniel Chen to take another look at this report,
however it is quite low on his priority list and he probably has not
looked at it yet. I'll see if I can get someone else to at least mark
it as "Triaged".
--
System beep broken in Karmic despite heroic efforts to fix it
https:
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
> Confirmed---your patch fixes the issue.
Good to hear!
> Strictly speaking, I don't think you need part 3 of your patch
I this is correct. Part 3 only re-enables the gconf
/apps/metacity/general/audible_bell key to turn the bell on and off.
Whether metacity *should* have a key to do this, I do
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.
Wow, that's... exhaustive. I'll see if I can flag someone down for you
guys and see if they can help you any further.
--
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 a member of Ubuntu
Bugs
I think I've solved the issue of metacity grabbing audible system bell
events. The attached patch contains my changes to metacity
(specifically src/core/bell.c). Please give it a try and let me know if
it works for you. If not, please let me know. I am a complete novice
at dealing with .deb fil
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
> Can you be precise about what you're doing to enable/disable compiz so
I can try the same tests?
I had been switching between "None" (metacity) and "Normal" (compiz) in
the Visual Effects panel of Appearance Preferences. I just figured out
that I can also switch by running "compiz --replace" an
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
Grondr, thanks for your exhaustive efforts to describe the many
permutations of this bug. I have only one thing to add: On my 9.04
system, the system bell seems to work exactly as it did in previous
versions. So I think what changed, changed between 9.04 and 9.10.
Perhaps we need to start diff-in
Donald, I fear you've mis-understood what this bug is about. We are
trying to get the system beep to come out of the PC speaker, which is
that speaker on your motherboard that can only play square waves. You
probably don't want to use this for your video conferencing, unless
you'll be talking to
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 also am affected by this. After lots of playing around I got it to do
the horrible system bell, which in my case is better than a nice
sounding one, but still.
Here's the steps I took to get the workaround:
1) Unblacklist pcspkr in /etc/modprobe.d/blacklist.conf
2) Reboot (or modprobe, whatever)
Grondr, thank you for your in-depth and exhaustive analysis. It will
prove to be very valuable. I have marked this report as "Confirmed" for
metacity, and I hope that will help capture the attention of the
metacity maintainers.
I think you have a much better handle on what is going on than I do,
** Changed in: metacity (Ubuntu)
Status: New => Confirmed
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
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
> 4. In my case the sound coming from the sound card was missing (point 1)
> and it works only if you disable compiz so I have to understand why
> compiz stops that sound.
If I understand correctly, this has nothing to do with the motherboard
speaker. In Metacity, you're getting a sound file (bel
Quoth Grondr:
> Re the rmmod/modprobe fandango: I'm not the only person who needs to
> do this. In fact, it would never have occurred to me that it would
> even change the behavior if I hadn't seen it mentioned in bug #398161
> (see comments #1 and #2 in this thread, where Philip asked if I'd
> tri
Some more clarification:
1. Starting from ubuntu version 9.10 the system beep has been replaced
from a sound coming from the sound card.
2. If you load the module pcspkr you can ear a sound coming from the pc
speaker but the system don't use it (only at the shut down or with the
beep command)
3
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
Since we have some new people following this now, and our history of
trying to track this down has been long and convoluted, I though it
might help for me to summarize my understanding of the current
situation. As you read this, please keep in mind that I have no idea
what I'm talking about. The
In reply to Grondr's post from yesterday:
> But if you hit rubout at the start of a line in that shell, you'll
> hear the bell out your line-out, not from the motherboard speaker. If
> you rmmod/modprobe, -then- a rubout there will -not- come out of
> line-out and -will- come out of the motherboard
[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
uhm.. I don't know. I can't understand why a video manager interacts
with sounds... some strange dependency?
--
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 a member of Ubuntu
Bugs, which is
Therefore, if indeed the differential is metacity versus compiz, then
the problem might be with libcanberra?
--
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 a member of Ubuntu
Bugs, which is
New information: Using metacity instead of compiz the system beep
works!! any suggestions??
--
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 a member of Ubuntu
Bugs, which is subscribed to Ub
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
Same problem in my system. See bug 493127
GM
--
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
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
I've marked the Pulse Audio bug as invalid.
The bug I feel is in metacity or libcanberra is that there is no (easy)
way to disable the system bell played back through the sound card in
favor of the PC speaker. (This is point (d) from above.) I don't know
whether the problem is in metacity, libca
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libcanberra (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Invalid
--
System beep broken in Karmic despite heroic efforts to fix i
> Now, let's consider whether your window manager uses libcanberra
> fully. I know metacity does. Compiz doesn't.
Everything I've reported has been using metacity. If I turn on desktop
effects (which switches to compiz, if I'm not mistaken), I don't get any
system bells at first. If I enable th
On Mon, Dec 7, 2009 at 11:58 PM, Robert Schroll wrote:
> In fact, it doesn't look to me that module-x11-bell is actually loaded
> by PA. I can rename /usr/lib/pulse-0.9.19/modules/module-x11-bell.so,
> restart, and still have the system bell intercepted! This confuses me
> to no end.
We don't a
On Tue, Dec 8, 2009 at 1:18 AM, Robert Schroll wrote:
> back. But the next time it happens, PA survives and rings the PC
> speaker itself. I can only assume that pulseaudio is learning,
> evolving, and slowly gaining sentience, and we must kill it now. With
> fire.
No. Delete it from the cache
One of the reasons I wanted to disable the PA bell was that it only
fires about once a second (as discussed in bug #430203) when, e.g., you
hold down the backspace key at a terminal prompt. I prefer the old
behavior of the PC speaker of nearly-continuous beeping. When I first
implemented workarou
Grondr wrote:
> Robert: I think actually we had exactly the same problem, and your
> workaround works for me. I'll explain, 'cause it'll help in debugging
> this for real.
That seems like a reasonable assessment. I'll point out a few places where our
systems differ. These should be signs of
Robert: I think actually we had exactly the same problem, and your
workaround works for me. I'll explain, 'cause it'll help in debugging
this for real.
First off, I've now gotten to a state where my system bell is coming out
of line-out. It wasn't before. I'm reasonably sure that this was
beca
I've found two work-arounds. Let me know if either works for you.
Workaround #1
Whatever is trapping system bell events tries to play the file
/usr/share/sounds/ubuntu/stereo/bell.ogg. If I rename this file, it falls back
to the using the system bell. So long as the PC speaker is enabled (`su
We seem to be having slightly different problems - I am getting a sound
out of my speakers when I would expect a system beep. What I'm trying
to do is go back to the ugly PC speaker beep that I know and love. I
was guessing that the sound was being produced by pulse audio, and it
seems that modul
Oh, right, so some quick research indicates the .tdb files in ~/.pulse
are Trivial Database Files. Installing the tdbtools package (bug
#557819 already complains about their total lack of documentation) lets
you run tdbtool on 'em and use commands like "keys" and "dump", although
the values of the
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, unl
I now think that Gnome, Metacity, or Pulseaudio are implicated. The
hardware and X itself are probably not. Details:
I think I've managed to pry this bug quite a bit farther open, but it's
not quite there yet. In particular, I -can- get the system bell to work
under bare X as any user. And I c
I'm having the same problem on a Presario 2100 running 32-bit Karmic.
Running `modprobe pcspkr` enables beeping from the ttys, but Pulse Audio
continues to handle the system bell for X. Please let me know if you
need more hardware info from me, but this really looks like a software
issue to me.
O
Btw, these tests under X that I'm doing---I'm doing them typing directly
on the machine's actual keyboard and using its actual display. Don't
get confused by my comments about ssh'ing in from elsewhere---I'm making
sure to run the tests directly on the machine's actual I/O hardware so I
can't get
Ah, and my comment above about reboot---I just tried "shutdown -r 3"
from the LiveCD, and -that- beeped the speaker! "echo foo | wall" also
beeps.
I rebooted the normal 64-bit system and noticed that "echo foo | wall"
didn't beep the system bell. (Although I was also ssh'ed in from
elsewhere and
1 - 100 of 104 matches
Mail list logo
