SRU 3.36.6
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
Focal |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
yaru-theme (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
Focal |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) |
Bug Description
[ Impact ]
That's the current GNOME stable update, including some fixes and translation updates
https:/
Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU.
The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release.
In fact:
- Ubuntu's GNOME shell uses a Yaru theme based on upstream
gnome-shell This theme basically takes the shell's data/ directory,
applies some diffs and generates a gresource file out of it, that it's
then loaded on startup (in place of the upstream one).
- GNOME Shell applied some fixes to the theme (se its data/
directory diffs)
- In order to get those fixes in Ubuntu main session we have to sync
the upstream changes applied to such dir to yaru's src/gnome-shell
path
- You can easily compare the diffs applied there to match the ones
happening in its upstream counterpart.
The yaru-theme's `gnome-
to allow three way merges when updating to new versions of gnome-shell,
and it is not used for generating the final packages at all
[ Test case ]
The update is part of GNOME stable updates
https:/
GNOME Shell and its components should continue working
[ Regression potential ]
There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates
CVE References
summary: |
- Update to 3.36.6 and SRU it + SRU 3.36.6 |
Changed in yaru-theme (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in gnome-shell (Ubuntu Focal): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in yaru-theme (Ubuntu Focal): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
importance: | Undecided → Medium |
status: | New → In Progress |
description: | updated |
description: | updated |
summary: |
- SRU 3.36.6 + SRU 3.36.6/3.36.7 |
Changed in gnome-shell (Ubuntu Focal): | |
status: | Incomplete → In Progress |
Changed in gnome-shell (Ubuntu): | |
status: | In Progress → Invalid |
Changed in gnome-shell (Ubuntu): | |
status: | Invalid → Fix Released |
tags: | added: upgrade-software-version |
On gnome-shell, we now understand there are complications with API breakage in microreleases, so we need a plan for reverse dependency shell extensions to mitigate potential regressions. Discussion at https:/ /discourse. ubuntu. com/t/scope- of-gnome- mru/18041. I don't think we can proceed with the gnome-shell microrelease update until we have a plan for this.
I don't think it makes sense to proceed with yaru-theme either until this is resolved, since I understand that's based on the gnome-shell update that is not concluded yet.
I don't understand why yaru-theme needs to be updated, either. I see that this has been done for yaru-theme once before, but I've found no explanation as to why. The current queue diff has:
diff --git a/debian/ README. source b/debian/ README. source README. source shell/upstream` directory is just for documentation and
new file mode 100644
index 0000000..84c9d3c
--- /dev/null
+++ b/debian/
@@ -0,0 +1,3 @@
+The `gnome-
+to allow three way merges when updating to new versions of gnome-shell,
+and it is not used for generating the final packages at all
If this isn't used for generating the final packages at all, why do you propose to make users download an update?