This bug was fixed in the package gnome-shell - 3.36.3-1ubuntu1~20.04.2
---
gnome-shell (3.36.3-1ubuntu1~20.04.2) focal; urgency=medium
* No change backport to focal
gnome-shell (3.36.3-1ubuntu2) groovy; urgency=medium
* d/p/shell-mime-sniffer-Ignore-invalid-file-content-type.pa
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873692
Title:
Do Not Disturb se
Hi, I have now installed gnome-shell/focal-proposed,now
3.36.3-1ubuntu1~20.04.2 amd64 [installed] and the patch works as
expected. The setting of Do Not Disturb persists across login sessions.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hello Jeremy, or anyone else affected,
Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.3-1ubuntu1~20.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
This bug was fixed in the package gnome-shell - 3.36.3-1ubuntu2
---
gnome-shell (3.36.3-1ubuntu2) groovy; urgency=medium
* d/p/shell-mime-sniffer-Ignore-invalid-file-content-type.patch:
- gnome-shell-sniffer, don't crash when opening files with invalid content
type (LP: #1
** Changed in: gnome-shell (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Description: Ubuntu 20.04 LTS
- Release: 20.04
- gnome-control-center:
- Installed: 1:3.36.1-1ubuntu5
- Candidate: 1:3.36.1-1ubuntu5
- Version table:
- *** 1:3.36.1-1ubuntu5 500
- 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
-
** No longer affects: gnome-control-center
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2804
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2804
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2804
Importance: Unknown
S
The issue was in gnome-shell and a fix has been commited to git now
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubun
Thanks, it looks right indeed
** Changed in: gnome-control-center (Ubuntu)
Status: New => Triaged
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/961
Importance: Unknown
Status: Unknown
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Done (https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/961).
Hopefully I submitted it correctly.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #961
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/961
--
You received this bug notification bec
Could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-
control-center/-/issues ? They are better placed to tell how the feature
is supposed to be working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Thinking about it, it's probably rather a gnome-shell issue. gnome-
control-center is only a frontend and not active/doing anything unless
you open/use it so it can't be responsible for resetting the value at
login
** Package changed: gnome-control-center (Ubuntu) => gnome-shell
(Ubuntu)
** Chang
I have a feeling you are right that it may not be gnome-control-center
doing this as setting the default value of show-banners in
/usr/share/glib2.0/schemas to false ends up being ignored at login.
It is unclear to me what the desired behaviour is from those
discussions, but my expectation is that
Thanks for your report! I can confirm it. When "Do Not Disturb" is
enabled, this dconf value is set:
$ gsettings get org.gnome.desktop.notifications show-banners
false
But something always sets it to "true" at login. (That something is
reasonably not gnome-control-center, btw, since it's not laun
16 matches
Mail list logo