More freeze break requests for gnome-shell
- From: Florian Müllner <fmuellner gnome org>
- To: release-team <release-team gnome org>
- Subject: More freeze break requests for gnome-shell
- Date: Fri, 06 Mar 2020 17:34:53 +0100
Hey everyone!
Tarballs are almost due (hi Michael!), but there are still a couple of
things we would like to include.
I hope bundling the requests in a single mail is OK:
1. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1068
We currently crash on startup if any of the top-icons extensions is
enabled.
The merge request that addresses the issue is not overly complex,
but still
beyond a trivial one line fix.
However I'd still argue that it is preferable to land, as:
- it has been confirmed to fix the crash, and not crashing is
clearly an improvement
- all code changes are limited to our legacy status icon support, so
it's perfectly
safe for everyone who is *not* using any of those extensions
2. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1069
ibus support is currently broken in the Xorg session. The fix is a
trivial one-liner
("do in the xorg session what we are already doing for xwayland")
3. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1065
If gnome-settings-daemon's xsettings service fails to start, we
currently end up without
X11 support in the wayland session. The fix is again trivial (don't
treat gsd-xsettings
failure as fatal for Xwayland startup)
4. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1110
On multi-monitor systems, popup windows may pop up on the wrong
monitor (or completely
off-screen). The fix should be easy and safe.
5. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1074
Two small additions to the Extensions D-Bus API. Those are pure
additions, so they have
no effect on any existing users of the API (like the "new"
Extensions app, the browser
integration or Tweaks).
The reason for wanting this in 3.36.0 is that I want to improve(*)
on the Extensions app
in 3.36.1 (and ultimately make it available on Flathub), but it
feels wrong to add new API
in a stable release and rely on it.
(*) all under-the-hood: No UI or string changes
6. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1063
This is a simple request from Ubuntu for a small improvement for
session modes (non-default
GNOME-based sessions like "Ubuntu" or "Classic").
Similar to the above, the reason why I want this in 3.36.0 is that
landing it in 3.36.1 would
open the potential for session modes that are supposed to work on
"3.36", but fail with 3.36.0.
On the other hand it would be sad to delay the improvement for a
whole six months.
Those are the important ones in my opinion. There are a couple more
nice-to-have issues that are low-impact, but have trivial and safe
patches available:
7. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1071
Settings now has a dedicated "Location Services" panel, but the
location submenu
in the shell's top-right menu still launches the "Privacy" panel.
8. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1059
The title of app folders in the overview is hard to read when using
the light theme variant
(like Ubuntu does). Not an issue as far as upstream is concerned,
but the fix is trivial
and safe
9. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1057
The drag handles of the volume/brightness sliders has a small
graphical glitch
at 0; this was supposed to be addressed in 3.35.92, but there's
still a minor
glitch left. Again not the end of the world, but the fix is trivial
and safe
(it's effectively a one-line fix, although the patch hides that a
bit by renaming
a variable)
Apologies for that late flood of requests (they have been piling up
until earlier today).
Regards,
Florian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]