unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <marius@gnu.org>, 45109@debbugs.gnu.org
Subject: bug#45109: GNOME: unable to change alert "beep" sound since staging merge
Date: Sat, 06 Mar 2021 19:20:27 -0500	[thread overview]
Message-ID: <874khn24rd.fsf@netris.org> (raw)
In-Reply-To: <87k0tt406e.fsf@gnu.org>

Hi Marius,

Marius Bakke <marius@gnu.org> writes:

> Mark H Weaver <mhw@netris.org> skriver:
>
>> 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.
>
> There were not a lot of GNOME-related changes in that merge.  From a
> quick glance of...
>
>   git shortlog --format='%h %s' --no-merges -n fe5c9051cc..e827f40479
>
> ...a likely culprit is:
>
>   62df18d305 gnu: dconf: Update to 0.36.0.
>
> Can you check if reverting it makes a difference?

Reverting that update does seem to have fixed the problem.  I've been
running my Guix system with dconf-0.34 since you made this suggestion
last December, and the problem where I'm *unable* to change my GNOME
alert sound has never happened since.  (It still occasionally resets to
the default "drip" alert sound, as I noted in my original report, but at
least I can change it back easily).

I will soon switch back to dconf-0.36 to see if the problem returns.

     Thanks,
       Mark




  parent reply	other threads:[~2021-03-07  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 23:36 bug#45109: GNOME: unable to change alert "beep" sound since staging merge Mark H Weaver
2020-12-08  0:21 ` 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 [this message]
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=874khn24rd.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=45109@debbugs.gnu.org \
    --cc=marius@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).