How to COMPLETELY turn off system beep sounds forever for good for real

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
49
down vote

favorite
4












I use Nautilus to explore my files. I use a Debian-based OS with KDE Plasma 5.



I use the keyboard a lot. When I press the key up when navigating files, if I'm already at the extremity of the list of files, Nautilus will send a big system beep which I will hear at 100% volume through my headphones. My reaction is comparable to getting electrified.



I have placed the following lines in ~/.bashrc for the sudo (root) user and for my regular desktop user:



# Turn off system beep in console:
xset b off
xset b 0 0 0


However, despite the beep going away from some places in the OS (such as erasing an empty line in the gnome-terminal), it's still in Nautilus. I believe it's because Nautilus doesn't source any of the .bashrc or because it ignores the xset commands.



How do I fix this?



What I need might be at a deeper level than the .bashrc, some file that is executed by everything, but which can still control the sound. Otherwise, disabling the sound another way or replacing it could be interesting.










share|improve this question



















  • 3




    Is it a system beep (so loud tone), or sound (bark/drip/dong etc for gnome)? If its the former its probably system level (in which case, try disabling the pcspkr module, or using a different sound card - if its the latter you will have to turn off the sound in system settings (including Gnome's as in Stephen's answer)
    – Wilf
    Jul 2 at 12:01







  • 9




    Just to make it explicit for those who didn't realize it: ~/.bashrc is the user configuration file of the bash shell, the default Debian terminal shell. If you realize that, it's pretty obvious why bash settings do not affect other applications like Nautilus.
    – MSalters
    Jul 2 at 12:04






  • 3




    Some sound cards have the system beep as a separate channel which can be muted.
    – Simon Richter
    Jul 2 at 12:25






  • 3




    Try using ~/.profile instead of ~/.bashrc. As noted by @MSalters, ~/.bashrc is run when you open a new terminal, and not when you log in. ~/.profile is run when you log in. (Laughed good on your reaction, I've experienced it myself!)
    – Teodor
    Jul 2 at 15:56







  • 14




    Wire cutters; just cut it out ^^
    – esoterik
    Jul 2 at 17:16














up vote
49
down vote

favorite
4












I use Nautilus to explore my files. I use a Debian-based OS with KDE Plasma 5.



I use the keyboard a lot. When I press the key up when navigating files, if I'm already at the extremity of the list of files, Nautilus will send a big system beep which I will hear at 100% volume through my headphones. My reaction is comparable to getting electrified.



I have placed the following lines in ~/.bashrc for the sudo (root) user and for my regular desktop user:



# Turn off system beep in console:
xset b off
xset b 0 0 0


However, despite the beep going away from some places in the OS (such as erasing an empty line in the gnome-terminal), it's still in Nautilus. I believe it's because Nautilus doesn't source any of the .bashrc or because it ignores the xset commands.



How do I fix this?



What I need might be at a deeper level than the .bashrc, some file that is executed by everything, but which can still control the sound. Otherwise, disabling the sound another way or replacing it could be interesting.










share|improve this question



















  • 3




    Is it a system beep (so loud tone), or sound (bark/drip/dong etc for gnome)? If its the former its probably system level (in which case, try disabling the pcspkr module, or using a different sound card - if its the latter you will have to turn off the sound in system settings (including Gnome's as in Stephen's answer)
    – Wilf
    Jul 2 at 12:01







  • 9




    Just to make it explicit for those who didn't realize it: ~/.bashrc is the user configuration file of the bash shell, the default Debian terminal shell. If you realize that, it's pretty obvious why bash settings do not affect other applications like Nautilus.
    – MSalters
    Jul 2 at 12:04






  • 3




    Some sound cards have the system beep as a separate channel which can be muted.
    – Simon Richter
    Jul 2 at 12:25






  • 3




    Try using ~/.profile instead of ~/.bashrc. As noted by @MSalters, ~/.bashrc is run when you open a new terminal, and not when you log in. ~/.profile is run when you log in. (Laughed good on your reaction, I've experienced it myself!)
    – Teodor
    Jul 2 at 15:56







  • 14




    Wire cutters; just cut it out ^^
    – esoterik
    Jul 2 at 17:16












up vote
49
down vote

favorite
4









up vote
49
down vote

favorite
4






4





I use Nautilus to explore my files. I use a Debian-based OS with KDE Plasma 5.



I use the keyboard a lot. When I press the key up when navigating files, if I'm already at the extremity of the list of files, Nautilus will send a big system beep which I will hear at 100% volume through my headphones. My reaction is comparable to getting electrified.



I have placed the following lines in ~/.bashrc for the sudo (root) user and for my regular desktop user:



# Turn off system beep in console:
xset b off
xset b 0 0 0


However, despite the beep going away from some places in the OS (such as erasing an empty line in the gnome-terminal), it's still in Nautilus. I believe it's because Nautilus doesn't source any of the .bashrc or because it ignores the xset commands.



How do I fix this?



What I need might be at a deeper level than the .bashrc, some file that is executed by everything, but which can still control the sound. Otherwise, disabling the sound another way or replacing it could be interesting.










share|improve this question















I use Nautilus to explore my files. I use a Debian-based OS with KDE Plasma 5.



I use the keyboard a lot. When I press the key up when navigating files, if I'm already at the extremity of the list of files, Nautilus will send a big system beep which I will hear at 100% volume through my headphones. My reaction is comparable to getting electrified.



I have placed the following lines in ~/.bashrc for the sudo (root) user and for my regular desktop user:



# Turn off system beep in console:
xset b off
xset b 0 0 0


However, despite the beep going away from some places in the OS (such as erasing an empty line in the gnome-terminal), it's still in Nautilus. I believe it's because Nautilus doesn't source any of the .bashrc or because it ignores the xset commands.



How do I fix this?



What I need might be at a deeper level than the .bashrc, some file that is executed by everything, but which can still control the sound. Otherwise, disabling the sound another way or replacing it could be interesting.







debian audio kde nautilus






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 17 at 1:44

























asked Jul 2 at 7:49









Guillaume Chevalier

35338




35338







  • 3




    Is it a system beep (so loud tone), or sound (bark/drip/dong etc for gnome)? If its the former its probably system level (in which case, try disabling the pcspkr module, or using a different sound card - if its the latter you will have to turn off the sound in system settings (including Gnome's as in Stephen's answer)
    – Wilf
    Jul 2 at 12:01







  • 9




    Just to make it explicit for those who didn't realize it: ~/.bashrc is the user configuration file of the bash shell, the default Debian terminal shell. If you realize that, it's pretty obvious why bash settings do not affect other applications like Nautilus.
    – MSalters
    Jul 2 at 12:04






  • 3




    Some sound cards have the system beep as a separate channel which can be muted.
    – Simon Richter
    Jul 2 at 12:25






  • 3




    Try using ~/.profile instead of ~/.bashrc. As noted by @MSalters, ~/.bashrc is run when you open a new terminal, and not when you log in. ~/.profile is run when you log in. (Laughed good on your reaction, I've experienced it myself!)
    – Teodor
    Jul 2 at 15:56







  • 14




    Wire cutters; just cut it out ^^
    – esoterik
    Jul 2 at 17:16












  • 3




    Is it a system beep (so loud tone), or sound (bark/drip/dong etc for gnome)? If its the former its probably system level (in which case, try disabling the pcspkr module, or using a different sound card - if its the latter you will have to turn off the sound in system settings (including Gnome's as in Stephen's answer)
    – Wilf
    Jul 2 at 12:01







  • 9




    Just to make it explicit for those who didn't realize it: ~/.bashrc is the user configuration file of the bash shell, the default Debian terminal shell. If you realize that, it's pretty obvious why bash settings do not affect other applications like Nautilus.
    – MSalters
    Jul 2 at 12:04






  • 3




    Some sound cards have the system beep as a separate channel which can be muted.
    – Simon Richter
    Jul 2 at 12:25






  • 3




    Try using ~/.profile instead of ~/.bashrc. As noted by @MSalters, ~/.bashrc is run when you open a new terminal, and not when you log in. ~/.profile is run when you log in. (Laughed good on your reaction, I've experienced it myself!)
    – Teodor
    Jul 2 at 15:56







  • 14




    Wire cutters; just cut it out ^^
    – esoterik
    Jul 2 at 17:16







3




3




Is it a system beep (so loud tone), or sound (bark/drip/dong etc for gnome)? If its the former its probably system level (in which case, try disabling the pcspkr module, or using a different sound card - if its the latter you will have to turn off the sound in system settings (including Gnome's as in Stephen's answer)
– Wilf
Jul 2 at 12:01





Is it a system beep (so loud tone), or sound (bark/drip/dong etc for gnome)? If its the former its probably system level (in which case, try disabling the pcspkr module, or using a different sound card - if its the latter you will have to turn off the sound in system settings (including Gnome's as in Stephen's answer)
– Wilf
Jul 2 at 12:01





9




9




Just to make it explicit for those who didn't realize it: ~/.bashrc is the user configuration file of the bash shell, the default Debian terminal shell. If you realize that, it's pretty obvious why bash settings do not affect other applications like Nautilus.
– MSalters
Jul 2 at 12:04




Just to make it explicit for those who didn't realize it: ~/.bashrc is the user configuration file of the bash shell, the default Debian terminal shell. If you realize that, it's pretty obvious why bash settings do not affect other applications like Nautilus.
– MSalters
Jul 2 at 12:04




3




3




Some sound cards have the system beep as a separate channel which can be muted.
– Simon Richter
Jul 2 at 12:25




Some sound cards have the system beep as a separate channel which can be muted.
– Simon Richter
Jul 2 at 12:25




3




3




Try using ~/.profile instead of ~/.bashrc. As noted by @MSalters, ~/.bashrc is run when you open a new terminal, and not when you log in. ~/.profile is run when you log in. (Laughed good on your reaction, I've experienced it myself!)
– Teodor
Jul 2 at 15:56





Try using ~/.profile instead of ~/.bashrc. As noted by @MSalters, ~/.bashrc is run when you open a new terminal, and not when you log in. ~/.profile is run when you log in. (Laughed good on your reaction, I've experienced it myself!)
– Teodor
Jul 2 at 15:56





14




14




Wire cutters; just cut it out ^^
– esoterik
Jul 2 at 17:16




Wire cutters; just cut it out ^^
– esoterik
Jul 2 at 17:16










4 Answers
4






active

oldest

votes

















up vote
31
down vote













Short of muting the sound entirely or disconnecting your headphones, there is no system-wide setting for events which will be followed by all applications. In your case especially, since you’re using Nautilus on a KDE system, you’ll run into issues since Nautilus won’t follow your desktop’s configured behaviour.



Nautilus uses GNOME’s settings. If you have the GNOME control centre, you can disable sound effects there — go to the sound settings, and disable sound effects. Alternatively, run dconf-editor, go to “org/gnome/desktop/sound”, and disable “event-sounds” and “input-feedback-sounds”. You can do this from the command line too, see How to turn off alert sounds/sound effects on Gnome from terminal? for details.






share|improve this answer




















  • I don't think this is true. If it is using the PC speaker, you can disable that globally.
    – forest
    Jul 3 at 7:52






  • 5




    @forest the question states “Nautilus will send a big system beep which I will hear at 100% volume through my headphones”. That can’t be disabled by disabling the PC speaker.
    – Stephen Kitt
    Jul 3 at 7:57










  • Nitpicking, but there is a kernel configuration setting that sends requests to trigger the PC speaker through the ALSA driver instead, but I don't know if any distros actually do that by default. But that's probably not the case, so good point.
    – forest
    Jul 3 at 7:59







  • 6




    @forest there’s really a terminology issue in the question — Nautilus doesn’t use the system beep.
    – Stephen Kitt
    Jul 3 at 8:00

















up vote
19
down vote













I do not know what sound KDE does, but if you mean system beep, just disable loading of the pcspkr module. As root do:



rmmod pcspkr ; echo "blacklist pcspkr" >>/etc/modprobe.d/blacklist.conf






share|improve this answer
















  • 1




    This only disables the PC speaker, which Nautilus doesn't use. You're solving the wrong problem.
    – Gilles
    Jul 3 at 11:10











  • I was amused yet annoyed to learn my new Lenovo laptop has a speaker. Every time I hit backspace one too many times, have a failed Ctrl+F search in Firefox, have a failed tab completion... always this loud, obnoxious beep. Instead of configuring each piece of software, removing the pcspkr mod worked! (I needed to use /sbin/rmmod by the way, PATH was not set correctly for root.)
    – Luc
    Sep 14 at 19:45


















up vote
1
down vote













The xset command you're using operates on the X server/X session, not the terminal, so .bashrc or similar is not the right place to put it. If Nautilus is really beeping via the X server's bell function, I would expect the xset to stop it, if you've already opened a terminal (and thereby run the command) beforehand.



If that works, what you need to do is get the command run as part of starting/logging in under X. The traditional way to do this is via a .xsession or .xinitrc file; however, these files (scripts) were traditionally expected to run your window manager/desktop environment session program, as the final line via exec, and if you just go dropping in a script containing nothing but xset, you might find yourself unable to login under X (rather, immediately getting logged out when you do). Figuring out the right thing to do here is going to be somewhat specific to the OS/distro's X and desktop environment setup, so I feel like I'm leaving this answer somewhat incomplete, but as a source of direction for where to look.






share|improve this answer



























    up vote
    0
    down vote













    To mute Gnome alerts:



    $ dconf write /org/gnome/desktop/sound/event-sounds "false" 


    Equivalently:



    $ gsettings set org.gnome.desktop.sound event-sounds false





    share|improve this answer






















    • Oops, this duplicates Stephen Kitt's answer. Consider this the tl;dr version.
      – Camille Goudeseune
      Jul 3 at 19:20










    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452978%2fhow-to-completely-turn-off-system-beep-sounds-forever-for-good-for-real%23new-answer', 'question_page');

    );

    Post as a guest






























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    31
    down vote













    Short of muting the sound entirely or disconnecting your headphones, there is no system-wide setting for events which will be followed by all applications. In your case especially, since you’re using Nautilus on a KDE system, you’ll run into issues since Nautilus won’t follow your desktop’s configured behaviour.



    Nautilus uses GNOME’s settings. If you have the GNOME control centre, you can disable sound effects there — go to the sound settings, and disable sound effects. Alternatively, run dconf-editor, go to “org/gnome/desktop/sound”, and disable “event-sounds” and “input-feedback-sounds”. You can do this from the command line too, see How to turn off alert sounds/sound effects on Gnome from terminal? for details.






    share|improve this answer




















    • I don't think this is true. If it is using the PC speaker, you can disable that globally.
      – forest
      Jul 3 at 7:52






    • 5




      @forest the question states “Nautilus will send a big system beep which I will hear at 100% volume through my headphones”. That can’t be disabled by disabling the PC speaker.
      – Stephen Kitt
      Jul 3 at 7:57










    • Nitpicking, but there is a kernel configuration setting that sends requests to trigger the PC speaker through the ALSA driver instead, but I don't know if any distros actually do that by default. But that's probably not the case, so good point.
      – forest
      Jul 3 at 7:59







    • 6




      @forest there’s really a terminology issue in the question — Nautilus doesn’t use the system beep.
      – Stephen Kitt
      Jul 3 at 8:00














    up vote
    31
    down vote













    Short of muting the sound entirely or disconnecting your headphones, there is no system-wide setting for events which will be followed by all applications. In your case especially, since you’re using Nautilus on a KDE system, you’ll run into issues since Nautilus won’t follow your desktop’s configured behaviour.



    Nautilus uses GNOME’s settings. If you have the GNOME control centre, you can disable sound effects there — go to the sound settings, and disable sound effects. Alternatively, run dconf-editor, go to “org/gnome/desktop/sound”, and disable “event-sounds” and “input-feedback-sounds”. You can do this from the command line too, see How to turn off alert sounds/sound effects on Gnome from terminal? for details.






    share|improve this answer




















    • I don't think this is true. If it is using the PC speaker, you can disable that globally.
      – forest
      Jul 3 at 7:52






    • 5




      @forest the question states “Nautilus will send a big system beep which I will hear at 100% volume through my headphones”. That can’t be disabled by disabling the PC speaker.
      – Stephen Kitt
      Jul 3 at 7:57










    • Nitpicking, but there is a kernel configuration setting that sends requests to trigger the PC speaker through the ALSA driver instead, but I don't know if any distros actually do that by default. But that's probably not the case, so good point.
      – forest
      Jul 3 at 7:59







    • 6




      @forest there’s really a terminology issue in the question — Nautilus doesn’t use the system beep.
      – Stephen Kitt
      Jul 3 at 8:00












    up vote
    31
    down vote










    up vote
    31
    down vote









    Short of muting the sound entirely or disconnecting your headphones, there is no system-wide setting for events which will be followed by all applications. In your case especially, since you’re using Nautilus on a KDE system, you’ll run into issues since Nautilus won’t follow your desktop’s configured behaviour.



    Nautilus uses GNOME’s settings. If you have the GNOME control centre, you can disable sound effects there — go to the sound settings, and disable sound effects. Alternatively, run dconf-editor, go to “org/gnome/desktop/sound”, and disable “event-sounds” and “input-feedback-sounds”. You can do this from the command line too, see How to turn off alert sounds/sound effects on Gnome from terminal? for details.






    share|improve this answer












    Short of muting the sound entirely or disconnecting your headphones, there is no system-wide setting for events which will be followed by all applications. In your case especially, since you’re using Nautilus on a KDE system, you’ll run into issues since Nautilus won’t follow your desktop’s configured behaviour.



    Nautilus uses GNOME’s settings. If you have the GNOME control centre, you can disable sound effects there — go to the sound settings, and disable sound effects. Alternatively, run dconf-editor, go to “org/gnome/desktop/sound”, and disable “event-sounds” and “input-feedback-sounds”. You can do this from the command line too, see How to turn off alert sounds/sound effects on Gnome from terminal? for details.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 2 at 8:19









    Stephen Kitt

    145k22319385




    145k22319385











    • I don't think this is true. If it is using the PC speaker, you can disable that globally.
      – forest
      Jul 3 at 7:52






    • 5




      @forest the question states “Nautilus will send a big system beep which I will hear at 100% volume through my headphones”. That can’t be disabled by disabling the PC speaker.
      – Stephen Kitt
      Jul 3 at 7:57










    • Nitpicking, but there is a kernel configuration setting that sends requests to trigger the PC speaker through the ALSA driver instead, but I don't know if any distros actually do that by default. But that's probably not the case, so good point.
      – forest
      Jul 3 at 7:59







    • 6




      @forest there’s really a terminology issue in the question — Nautilus doesn’t use the system beep.
      – Stephen Kitt
      Jul 3 at 8:00
















    • I don't think this is true. If it is using the PC speaker, you can disable that globally.
      – forest
      Jul 3 at 7:52






    • 5




      @forest the question states “Nautilus will send a big system beep which I will hear at 100% volume through my headphones”. That can’t be disabled by disabling the PC speaker.
      – Stephen Kitt
      Jul 3 at 7:57










    • Nitpicking, but there is a kernel configuration setting that sends requests to trigger the PC speaker through the ALSA driver instead, but I don't know if any distros actually do that by default. But that's probably not the case, so good point.
      – forest
      Jul 3 at 7:59







    • 6




      @forest there’s really a terminology issue in the question — Nautilus doesn’t use the system beep.
      – Stephen Kitt
      Jul 3 at 8:00















    I don't think this is true. If it is using the PC speaker, you can disable that globally.
    – forest
    Jul 3 at 7:52




    I don't think this is true. If it is using the PC speaker, you can disable that globally.
    – forest
    Jul 3 at 7:52




    5




    5




    @forest the question states “Nautilus will send a big system beep which I will hear at 100% volume through my headphones”. That can’t be disabled by disabling the PC speaker.
    – Stephen Kitt
    Jul 3 at 7:57




    @forest the question states “Nautilus will send a big system beep which I will hear at 100% volume through my headphones”. That can’t be disabled by disabling the PC speaker.
    – Stephen Kitt
    Jul 3 at 7:57












    Nitpicking, but there is a kernel configuration setting that sends requests to trigger the PC speaker through the ALSA driver instead, but I don't know if any distros actually do that by default. But that's probably not the case, so good point.
    – forest
    Jul 3 at 7:59





    Nitpicking, but there is a kernel configuration setting that sends requests to trigger the PC speaker through the ALSA driver instead, but I don't know if any distros actually do that by default. But that's probably not the case, so good point.
    – forest
    Jul 3 at 7:59





    6




    6




    @forest there’s really a terminology issue in the question — Nautilus doesn’t use the system beep.
    – Stephen Kitt
    Jul 3 at 8:00




    @forest there’s really a terminology issue in the question — Nautilus doesn’t use the system beep.
    – Stephen Kitt
    Jul 3 at 8:00












    up vote
    19
    down vote













    I do not know what sound KDE does, but if you mean system beep, just disable loading of the pcspkr module. As root do:



    rmmod pcspkr ; echo "blacklist pcspkr" >>/etc/modprobe.d/blacklist.conf






    share|improve this answer
















    • 1




      This only disables the PC speaker, which Nautilus doesn't use. You're solving the wrong problem.
      – Gilles
      Jul 3 at 11:10











    • I was amused yet annoyed to learn my new Lenovo laptop has a speaker. Every time I hit backspace one too many times, have a failed Ctrl+F search in Firefox, have a failed tab completion... always this loud, obnoxious beep. Instead of configuring each piece of software, removing the pcspkr mod worked! (I needed to use /sbin/rmmod by the way, PATH was not set correctly for root.)
      – Luc
      Sep 14 at 19:45















    up vote
    19
    down vote













    I do not know what sound KDE does, but if you mean system beep, just disable loading of the pcspkr module. As root do:



    rmmod pcspkr ; echo "blacklist pcspkr" >>/etc/modprobe.d/blacklist.conf






    share|improve this answer
















    • 1




      This only disables the PC speaker, which Nautilus doesn't use. You're solving the wrong problem.
      – Gilles
      Jul 3 at 11:10











    • I was amused yet annoyed to learn my new Lenovo laptop has a speaker. Every time I hit backspace one too many times, have a failed Ctrl+F search in Firefox, have a failed tab completion... always this loud, obnoxious beep. Instead of configuring each piece of software, removing the pcspkr mod worked! (I needed to use /sbin/rmmod by the way, PATH was not set correctly for root.)
      – Luc
      Sep 14 at 19:45













    up vote
    19
    down vote










    up vote
    19
    down vote









    I do not know what sound KDE does, but if you mean system beep, just disable loading of the pcspkr module. As root do:



    rmmod pcspkr ; echo "blacklist pcspkr" >>/etc/modprobe.d/blacklist.conf






    share|improve this answer












    I do not know what sound KDE does, but if you mean system beep, just disable loading of the pcspkr module. As root do:



    rmmod pcspkr ; echo "blacklist pcspkr" >>/etc/modprobe.d/blacklist.conf







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 2 at 12:30









    Edheldil

    58524




    58524







    • 1




      This only disables the PC speaker, which Nautilus doesn't use. You're solving the wrong problem.
      – Gilles
      Jul 3 at 11:10











    • I was amused yet annoyed to learn my new Lenovo laptop has a speaker. Every time I hit backspace one too many times, have a failed Ctrl+F search in Firefox, have a failed tab completion... always this loud, obnoxious beep. Instead of configuring each piece of software, removing the pcspkr mod worked! (I needed to use /sbin/rmmod by the way, PATH was not set correctly for root.)
      – Luc
      Sep 14 at 19:45













    • 1




      This only disables the PC speaker, which Nautilus doesn't use. You're solving the wrong problem.
      – Gilles
      Jul 3 at 11:10











    • I was amused yet annoyed to learn my new Lenovo laptop has a speaker. Every time I hit backspace one too many times, have a failed Ctrl+F search in Firefox, have a failed tab completion... always this loud, obnoxious beep. Instead of configuring each piece of software, removing the pcspkr mod worked! (I needed to use /sbin/rmmod by the way, PATH was not set correctly for root.)
      – Luc
      Sep 14 at 19:45








    1




    1




    This only disables the PC speaker, which Nautilus doesn't use. You're solving the wrong problem.
    – Gilles
    Jul 3 at 11:10





    This only disables the PC speaker, which Nautilus doesn't use. You're solving the wrong problem.
    – Gilles
    Jul 3 at 11:10













    I was amused yet annoyed to learn my new Lenovo laptop has a speaker. Every time I hit backspace one too many times, have a failed Ctrl+F search in Firefox, have a failed tab completion... always this loud, obnoxious beep. Instead of configuring each piece of software, removing the pcspkr mod worked! (I needed to use /sbin/rmmod by the way, PATH was not set correctly for root.)
    – Luc
    Sep 14 at 19:45





    I was amused yet annoyed to learn my new Lenovo laptop has a speaker. Every time I hit backspace one too many times, have a failed Ctrl+F search in Firefox, have a failed tab completion... always this loud, obnoxious beep. Instead of configuring each piece of software, removing the pcspkr mod worked! (I needed to use /sbin/rmmod by the way, PATH was not set correctly for root.)
    – Luc
    Sep 14 at 19:45











    up vote
    1
    down vote













    The xset command you're using operates on the X server/X session, not the terminal, so .bashrc or similar is not the right place to put it. If Nautilus is really beeping via the X server's bell function, I would expect the xset to stop it, if you've already opened a terminal (and thereby run the command) beforehand.



    If that works, what you need to do is get the command run as part of starting/logging in under X. The traditional way to do this is via a .xsession or .xinitrc file; however, these files (scripts) were traditionally expected to run your window manager/desktop environment session program, as the final line via exec, and if you just go dropping in a script containing nothing but xset, you might find yourself unable to login under X (rather, immediately getting logged out when you do). Figuring out the right thing to do here is going to be somewhat specific to the OS/distro's X and desktop environment setup, so I feel like I'm leaving this answer somewhat incomplete, but as a source of direction for where to look.






    share|improve this answer
























      up vote
      1
      down vote













      The xset command you're using operates on the X server/X session, not the terminal, so .bashrc or similar is not the right place to put it. If Nautilus is really beeping via the X server's bell function, I would expect the xset to stop it, if you've already opened a terminal (and thereby run the command) beforehand.



      If that works, what you need to do is get the command run as part of starting/logging in under X. The traditional way to do this is via a .xsession or .xinitrc file; however, these files (scripts) were traditionally expected to run your window manager/desktop environment session program, as the final line via exec, and if you just go dropping in a script containing nothing but xset, you might find yourself unable to login under X (rather, immediately getting logged out when you do). Figuring out the right thing to do here is going to be somewhat specific to the OS/distro's X and desktop environment setup, so I feel like I'm leaving this answer somewhat incomplete, but as a source of direction for where to look.






      share|improve this answer






















        up vote
        1
        down vote










        up vote
        1
        down vote









        The xset command you're using operates on the X server/X session, not the terminal, so .bashrc or similar is not the right place to put it. If Nautilus is really beeping via the X server's bell function, I would expect the xset to stop it, if you've already opened a terminal (and thereby run the command) beforehand.



        If that works, what you need to do is get the command run as part of starting/logging in under X. The traditional way to do this is via a .xsession or .xinitrc file; however, these files (scripts) were traditionally expected to run your window manager/desktop environment session program, as the final line via exec, and if you just go dropping in a script containing nothing but xset, you might find yourself unable to login under X (rather, immediately getting logged out when you do). Figuring out the right thing to do here is going to be somewhat specific to the OS/distro's X and desktop environment setup, so I feel like I'm leaving this answer somewhat incomplete, but as a source of direction for where to look.






        share|improve this answer












        The xset command you're using operates on the X server/X session, not the terminal, so .bashrc or similar is not the right place to put it. If Nautilus is really beeping via the X server's bell function, I would expect the xset to stop it, if you've already opened a terminal (and thereby run the command) beforehand.



        If that works, what you need to do is get the command run as part of starting/logging in under X. The traditional way to do this is via a .xsession or .xinitrc file; however, these files (scripts) were traditionally expected to run your window manager/desktop environment session program, as the final line via exec, and if you just go dropping in a script containing nothing but xset, you might find yourself unable to login under X (rather, immediately getting logged out when you do). Figuring out the right thing to do here is going to be somewhat specific to the OS/distro's X and desktop environment setup, so I feel like I'm leaving this answer somewhat incomplete, but as a source of direction for where to look.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jul 3 at 15:35









        R..

        1,500913




        1,500913




















            up vote
            0
            down vote













            To mute Gnome alerts:



            $ dconf write /org/gnome/desktop/sound/event-sounds "false" 


            Equivalently:



            $ gsettings set org.gnome.desktop.sound event-sounds false





            share|improve this answer






















            • Oops, this duplicates Stephen Kitt's answer. Consider this the tl;dr version.
              – Camille Goudeseune
              Jul 3 at 19:20














            up vote
            0
            down vote













            To mute Gnome alerts:



            $ dconf write /org/gnome/desktop/sound/event-sounds "false" 


            Equivalently:



            $ gsettings set org.gnome.desktop.sound event-sounds false





            share|improve this answer






















            • Oops, this duplicates Stephen Kitt's answer. Consider this the tl;dr version.
              – Camille Goudeseune
              Jul 3 at 19:20












            up vote
            0
            down vote










            up vote
            0
            down vote









            To mute Gnome alerts:



            $ dconf write /org/gnome/desktop/sound/event-sounds "false" 


            Equivalently:



            $ gsettings set org.gnome.desktop.sound event-sounds false





            share|improve this answer














            To mute Gnome alerts:



            $ dconf write /org/gnome/desktop/sound/event-sounds "false" 


            Equivalently:



            $ gsettings set org.gnome.desktop.sound event-sounds false






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Jul 3 at 20:39

























            answered Jul 3 at 19:19









            Camille Goudeseune

            1198




            1198











            • Oops, this duplicates Stephen Kitt's answer. Consider this the tl;dr version.
              – Camille Goudeseune
              Jul 3 at 19:20
















            • Oops, this duplicates Stephen Kitt's answer. Consider this the tl;dr version.
              – Camille Goudeseune
              Jul 3 at 19:20















            Oops, this duplicates Stephen Kitt's answer. Consider this the tl;dr version.
            – Camille Goudeseune
            Jul 3 at 19:20




            Oops, this duplicates Stephen Kitt's answer. Consider this the tl;dr version.
            – Camille Goudeseune
            Jul 3 at 19:20

















             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452978%2fhow-to-completely-turn-off-system-beep-sounds-forever-for-good-for-real%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay