"set bell-style none" doesn't silence my bell.

JordanH · 04-24-2005, 02:33 PM

Hi All,

I have tried modifying /etc/inputrc to set my bell-style to none. It doesn't sound like it works. I have also made the change in /usr/share/base-files/inputrc just in case for some strange reason it picks up the config there. Eitherway, my system bell still beeps at me and it's driving me insane.

Any ideas how to fix this?

Currently
Ubuntu 5.04
Kernel 2.6.10-5-386
Running in VMWare 5 for now

nukkel · 04-24-2005, 03:31 PM

Try "setterm -blength 0" (in console) or "xset -b" (in X)

You can also put this in your ~/.bashrc or ~/.profile or whatever.

To totally silence the bell at boot time it may be appropriate to put "setterm -blength 0 >/dev/ttyX" in the startup scripts (a line for each terminal you wish to silence, with X the appropriate number).

The best file to put it in is a bit distro-specific I'm afraid...

JordanH · 04-24-2005, 05:15 PM

That works.

As for silencing it through my virtual consoles, no sweat.

Is there a place to make this universal throughout the system for X users? I want to ensure that by default the bell is off and have my users only turn it on if they so desire.

p.s. I like your sig

Quote:

"UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things."
- Doug Gwyn

nukkel · 04-24-2005, 05:27 PM

Quote:

Originally posted by JordanH

Is there a place to make this universal throughout the system for X users? I want to ensure that by default the bell is off and have my users only turn it on if they so desire.

If you use a display manager (xdm, gdm, kdm, wdm, ...), somewhere in their setup directories (something like /etc/X11/xdm), there should be a script called "Xsession". This runs after a user logs into X (and ultimately runs his window manager). So this is a good place to put "xset -b" in. Users can then "xset +b" to turn the bell back on.

If your users go into X from console using "startx", then there is no system-wide place to do it; they'll have to put it in their ~/.xinitrc or ~/.xsession

Quote:

Originally posted by JordanH
p.s. I like your sig

Thx

JordanH · 04-24-2005, 09:54 PM

Perfect. Thanks.

stabu · 07-10-2005, 05:39 AM

Yes, I also had this problem and though the setterm solution is fine, the worry remains about what Ubuntu actually does with /etc/inputrc.

Does it ignore it? I ran a search right now on ubuntuforums and the word inputrc got 4 results, none of which really dealt with this issue.

/etc/inputrc is pretty crucial to command line editing. Ubuntu has to be using something . Guesses?

nukkel · 07-28-2005, 06:15 AM

Sorry, I've no experience with Ubuntu...

uenglert · 04-22-2014, 10:19 AM

Hi,

have a look for profile on gnome-terminal or for properties when
the terminal is open.
If you find a entry named terminal bell, remove the active flag.

That did help me, maybe it will help you too.