GNOME: unable to change alert "beep" sound since staging merge

  • Open
  • quality assurance status badge
Details
3 participants
  • Bengt Richter
  • Marius Bakke
  • Mark H Weaver
Owner
unassigned
Submitted by
Mark H Weaver
Severity
normal
M
M
Mark H Weaver wrote on 8 Dec 2020 00:36
(address . bug-guix@gnu.org)
87ft4hdw8q.fsf@netris.org
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
M
M
Marius Bakke wrote on 8 Dec 2020 01:21
87k0tt406e.fsf@gnu.org
Mark H Weaver <mhw@netris.org> skriver:

Toggle quote (4 lines)
> 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?
-----BEGIN PGP SIGNATURE-----

iQFDBAEBCgAtFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl/OxxkPHG1hcml1c0Bn
bnUub3JnAAoJEKKgbfKjOlT62BIH/jDCOrFN35vDpnHW/iWbjpKpKa6jfoBrQ1Wd
rA+Rh2G3JrX2IExiIxJbW3mFVQ/BtSIPzl/FMTbDkR6z022oeJVI4/NMDWcNwyEP
8pcw2V+vWKabYWpNpT9iDvwSIJfHMjQ+L5KaxyZEi0oc0XsWFarNj5et7nbw5tZJ
mWRsEO8vq6RHzZQWp0nPVZF9ClL40WUxU/Xz6kQlWVWHUrzrRKoIO5kmhVRjMupU
/2qvsfowrk0VAq+eaSDsrEhu5M3YR0tSl+Co54GCt9USDKgv15aih69Hbnccp0zK
5VO8Faa2KAatsdJ+ifFtpBTwuVTYdKf4M3k48jeWobILbOp+QA4=
=f1E/
-----END PGP SIGNATURE-----

B
B
Bengt Richter wrote on 8 Dec 2020 09:39
(name . Mark H Weaver)(address . mhw@netris.org)(address . 45109@debbugs.gnu.org)
20201208083927.GA16114@LionPure
Attachment: file
M
M
Mark H Weaver wrote on 9 Dec 2020 01:27
(name . Bengt Richter)(address . bokr@bokr.com)
87o8j3ygan.fsf@netris.org
Hi Marius and Bengt,

Thanks very much for your suggestions. I initially tried Marius's idea
to revert the dconf update, which seemed to work, but now I find that
I'm unable to reproduce the problem, even with my original
post-staging-merge system where I first encountered it.

I'm not sure what happened here, but I'm closing this bug.
Sorry for the noise.

Mark
Closed
M
M
Mark H Weaver wrote on 15 Dec 2020 01:11
(name . Bengt Richter)(address . bokr@bokr.com)
87lfe0nd0d.fsf@netris.org
reopen 45109
thanks

Earlier, I wrote:
Toggle quote (5 lines)
> I initially tried Marius's idea to revert the dconf update, which
> seemed to work, but now I find that I'm unable to reproduce the
> problem, even with my original post-staging-merge system where I first
> encountered it.

I spoke too soon. Now the problem is happening again, after another
system upgrade and reboot. I don't have time right now to investigate
further, but I'm reopening the bug.

Thanks,
Mark
B
B
Bengt Richter wrote on 17 Dec 2020 15:01
(name . Mark H Weaver)(address . mhw@netris.org)
20201217140104.GA7201@LionPure
Hi Mark, and who may be interested,

On +2020-12-14 19:11:51 -0500, Mark H Weaver wrote:
Toggle quote (16 lines)
> reopen 45109
> thanks
>
> Earlier, I wrote:
> > I initially tried Marius's idea to revert the dconf update, which
> > seemed to work, but now I find that I'm unable to reproduce the
> > problem, even with my original post-staging-merge system where I first
> > encountered it.
>
> I spoke too soon. Now the problem is happening again, after another
> system upgrade and reboot. I don't have time right now to investigate
> further, but I'm reopening the bug.
>
> Thanks,
> Mark

The same happened again to me -- i.e., my alert sound preference got reset.
This was after a pureos (debian based) update.
uname -a =-> Linux LionPure 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux

man 7 dconf =-> mentions that gsettings wraps unstable api gconf, so I poked
a little, but no time right now. HTH someone else go further :)

Toggle snippet (14 lines)
$ gsettings list-recursively |egrep 'sound|beep'
org.gnome.desktop.sound input-feedback-sounds false
org.gnome.desktop.sound theme-name '__custom'
org.gnome.desktop.sound allow-volume-above-100-percent false
org.gnome.desktop.sound event-sounds true
org.gnome.rhythmbox.plugins seen-plugins ['fmradio', 'mpris', 'daap', 'rb', 'artsearch', 'replaygain', 'webremote', 'lyrics', 'dbus-media-server', 'im-status', 'rblirc', 'notification', 'grilo', 'audioscrobbler', 'soundcloud', 'sendto', 'mtpdevice', 'pythonconsole', 'ipod', 'magnatune']
org.gnome.desktop.a11y.keyboard slowkeys-beep-press false
org.gnome.desktop.a11y.keyboard bouncekeys-beep-reject false
org.gnome.desktop.a11y.keyboard slowkeys-beep-reject false
org.gnome.desktop.a11y.keyboard feature-state-change-beep false
org.gnome.desktop.a11y.keyboard slowkeys-beep-accept false
org.gnome.desktop.a11y.keyboard stickykeys-modifier-beep false

As you recall from previously (here I've re-selected sonar.ogg :),
Toggle snippet (9 lines)
$ find ~/ -name '*__custom*'
/home/bokr/.local/share/sounds/__custom
$ find ~/ -name '*__custom*'|xargs ls -l
total 4
lrwxrwxrwx 1 bokr bokr 48 Dec 17 08:52 bell-terminal.ogg -> /usr/share/sounds/gnome/default/alerts/sonar.ogg
lrwxrwxrwx 1 bokr bokr 48 Dec 17 08:52 bell-window-system.ogg -> /usr/share/sounds/gnome/default/alerts/sonar.ogg
-rw-r--r-- 1 bokr bokr 61 Dec 10 12:11 index.theme

BTW, do you or anyone know if there is a CRUD[1]-log that can be enabled,
to log *EVERY* CRUD change to any persistent storage during system
(debian in this case) updates? That can't be a new idea ;)
(Maybe it's hard in the context of something signed that runs privileged
to do updates before rebooting to grub? )

Also, is there a standard policy somewhere for preserving/migrating content state
when installing a replacement storage box for the content?

If it is too much work to write migration code when storage internals or apis
change, couldn't it just be policy to mark the old box as box.old_NNN instead
of deleting/overwiting it, and emit (and log) a simple hint?


--
Regards,
Bengt Richter
M
M
Mark H Weaver wrote on 7 Mar 2021 01:20
874khn24rd.fsf@netris.org
Hi Marius,

Marius Bakke <marius@gnu.org> writes:

Toggle quote (17 lines)
> 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
M
M
Mark H Weaver wrote on 11 Mar 2021 12:27
8735x2vsjm.fsf@netris.org
Earlier, I wrote:
Toggle quote (2 lines)
> I will soon switch back to dconf-0.36 to see if the problem returns.

Shortly after switching back to dconf-0.36, the problem has indeed
returned. So, in summary, the problem has *never* happened to me with
dconf-0.34, but happens quite frequently with dconf-0.36.

Mark
?