Previously it was impossible to compose characters on higher levels of
some keyboard layouts as pressing the level selection key would just
exit compose mode.
Examples for affected keyboard layouts include the Latvian
apostrophe-variant "lv(apostrophe)" (latched third level), the extended
German keyboard layout "de(e1)" (latched fifth level) as well as the
multilingual Canadian keyboard layout "ca(multix)" and the German
neo-layout "de(neo)" and its descendants (shifted fifth level).
To reproduce, set a compose key and select the Latvian apostrophe layout.
Notice that you now can input [ by pressing first the ' and then the 8-key.
Then pressing <compose>'8'8 should produce ⟦, but prior to this patch it
did not.
Some locations have to be mounted, but their mounts are not user-visible
(e.g. smb-browse). Though this is maybe a bit weird, it is how it works
for years. The problem is that the commit 267ea755, which tries to get the
default location for opening, caused regression as it doesn't expect such
possibility. Before this commit, such locations were opened without any
issue, but nothing happens currently after clicking to "Connect" except of
clearing the "Connect to Server" entry. Let's fallback to the original
location if the mount was not found to fix this regression.
Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1811
This adds a missing error trap to prevent crashes. The X11 functions
called here cannot normally fail, but it seems they can fail in certain
configurations of the NVIDIA proprietary driver.
LP: #1911036
- d/p/imcontext-Look-for-Compose-file-in-the-right-place.patch,
d/p/Revert-Compose-sequence-changes.patch,
d/p/imcontext-Eat-key-events-during-preedit.patch:
Fix input regressions
- d/p/label-Fix-reacting-to-screen-resolution-changes.patch:
Redraw labels when "large text" setting changes
- d/p/spinbutton-Interpret-localized-digits.patch:
Interpret non-ASCII digits in spinbutton
- d/p/gdk-wayland-Defer-processing-of-globals-closures.patch:
Improve compatibility with non-GNOME compositors
- d/p/wayland-Improve-font-setting-fallback.patch,
d/p/wayland-Improve-font-setting-fallback-more.patch:
Improve default font settings
- d/p/scale-Fix-sporadic-criticals.patch:
Fix a use-after-free
- d/p/scrolledwindow-Always-add-other-scrollbar-size.patch:
Make sure to allocate enough space for scrollbars
- d/p/scrolledwindow-Cancel-overshoot-on-dimension-changes.patch:
Cancel overshoot handling if size changes during kinetic scrolling
- d/p/Fix-a-possible-crash-in-gtk_show_uri.patch:
Fix a possible crash if showing a URI with no basename
- d/p/x11-Be-quiet-on-exit-by-default.patch:
Don't log lots of messages when X11 server terminates
- Translation updates
... if we're not using indicators and the policy may be visible. Not
doing this if the policy may be invisible is incorrect as we need to
reserve the space anyway in case the scrolledwindow is allocated at
minimum size and the child size increases to show the scrollbar.
Some applications need to access gdk_quartz_window_get_nsview,
gdk_quartz_window_get_nswindow, and gdk_quartz_event_get_nsevent
so move these from the private gdkquartz-gtk-only.h to a new
header gdkquartz-cocoa-access.h. Don't include this header in
gdkquartz.h so that user code that doesn't need to access these
functins isn't required to compile with Objective C/C++.
Closes https://gitlab.gnome.org/GNOME/gtk/-/issues/1737
We can just group the code for the desktop GL codepath and the EGL
codepath a bit so that we can just have a single location where we
return TRUE upon a successful setup of our WGL/EGL context, and avoid
the C4715 warning that is considered an error when building with
GLib-2.68.x or later using Visual Studio, when we are building without
EGL support.
Avoid passing through random key press or release
events while we are showing preedit. That prevents
'accidents' like typing Ctrl-. bringing up the
Emoji chooser during preedit, or hitting Ctrl-a
after the Compose key moving the 'dot' around in
vim in terminals.
The condition we check for to catch X servers going away
may not be accurate anymore, and the warning shows up in
logs, causing customers to be concerned. So, be quiet by
default, unless the user explicitly asked for a message.
GtkBox is not going away, so there's not point in making things more
confusing for those who are still porting their code from GTK2 to GTK3
10 years after GTK 3.0 was released.
Fixes: #3854
