unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 45109@debbugs.gnu.org
Subject: bug#45109: GNOME: unable to change alert "beep" sound since staging merge
Date: Mon, 07 Dec 2020 18:36:10 -0500	[thread overview]
Message-ID: <87ft4hdw8q.fsf@netris.org> (raw)

Since the recent merge of the 'staging' branch into 'master' on 28 Nov
2020, I'm no longer able to configure the alert sound in GNOME.  That's
a pity, since I find the default "drip" sound extremely unpleasant.

In more detail:

To configure the alert sound, I first open GNOME Settings by clicking on
the gear icon in the pull-down menu on the right side of GNOME Shell's
top bar.  From there, I navigate to the "Sound" section and scroll to
the bottom of that section, where I'm given a choice of 4 options for
the "Alert Sound".

For as long as I can remember, and even today, this pane *does* remember
my preferred Alert Sound (sonar), and correctly highlights it as my
selected choice.  However, the default "drip" sound is the one that is
actually used by applications, e.g. by GNOME Terminal and Emacs.

Note that even before the recent staging merge, periodically (maybe once
a week or so), I would log in and find that the dreaded "drip" sound was
being used as my alert sound.  Each time, I was able to fix it by going
back to the Sound section of GNOME Settings, and clicking again on my
preferred alert sound (although it was already selected as my configured
alert sound).  Now, since the recent staging merge, that no longer
works.

If anyone can suggest a way to successfully change my alert sound, I
would be grateful.

       Mark




             reply	other threads:[~2020-12-07 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 23:36 Mark H Weaver [this message]
2020-12-08  0:21 ` bug#45109: GNOME: unable to change alert "beep" sound since staging merge Marius Bakke
2020-12-09  0:27   ` Mark H Weaver
2020-12-15  0:11     ` Mark H Weaver
2020-12-17 14:01       ` Bengt Richter
2021-03-07  0:20   ` Mark H Weaver
2021-03-11 11:27     ` Mark H Weaver
2020-12-08  8:39 ` Bengt Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ft4hdw8q.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=45109@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).