<div style="font-family:Arial, Helvetica, sans-serif; font-size:12px; color:#00000">(Sorry, it's my first bug report on Debian: I am doing mistakes, like a duplicate message already)<br>
<br>
"If your backtick key is a "dead key" grave accent (like the key printed<br>
with ` in some other national and international keyboard layouts) then<br>
À is the expected result."<br>
=> It's the case in the French keyboard grave accent and backtick are the same under the <span style="white-space:pre-wrap">7 key <a href="https://en.wikipedia.org/wiki/AZERTY#/media/File:KB_France.svg">https://en.wikipedia.org/wiki/AZERTY#/media/File:KB_France.svg</a></span><br>
=> Please note that ^e gives ê correctly<br>
but `A doesn't<br>
<br>
Have you rebooted since upgrading libglib2.0-0 to version<br>
2.74.6-2+deb12u2?<br>
=> Yes<br>
<br>
Are any warning messages logged in the systemd Journal, from either the<br>
application you are using, or ibus?<br>
=> No problem found<br>
<br>
Or if you run an affected application from a terminal (gnome-terminal<br>
or xterm or similar), are any warning messages logged in that terminal?<br>
=> gedit, terminal, any programming IDE encounter aren't complaining against any problem, but they are able to type ê but not À.<br>
<br>
The fact that some of you can't reproduce the problem I'm encountering easily doesn't surprise me,<br>
as #1070745 tricked most US keyboard users, at least, and was able to pass most tests, leading to a faulty release without being detected.<br>
If the trouble of dead keys not working was immediately detectable, I guess that the release would have been fixed of the dead keys problem before being sent to public.<br>
<br>
<span style="white-space:pre-wrap">im-config shows:</span></div>
<pre class="message">Current configuration for the input method:
* Default mode defined in /etc/default/im-config: 'auto'
* Active configuration: 'missing' (normally missing)
* Normal automatic choice: 'ibus' (normally ibus or fcitx5)
* Override rule: 'zh_CN,fcitx5:zh_TW,fcitx5:zh_HK,fcitx5:zh_SG,fcitx5'
* Current override choice: '' (Locale='fr_FR')
* Current automatic choice: 'ibus'
* Number of valid choices: 1 (normally 1)
* Desktop environment: 'GNOME'
The configuration set by im-config is activated by re-starting the system.
La sélection explicite n'est pas nécessaire pour permettre la configuration automatique si la sélection active est default/auto/cjkv/missing.
My guess is that the problem has for cause something around what you're writing:
With most keyboards, most languages, `A doesn't give À
But with some, like the French one that has the backtick for grave accent too, it should return À
When you did the fix that repaired most of the #1070745, didn't you forget to enable/check the rules for keyboards having backtick for grave accent?
I don't know how to write this idea, having very low knowledge about Debian's internal. But I feel that it could be something like that.
Regards,
Marc Le Bihan
</pre>
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Simon McVittie" <smcv@debian.org><br>
A : "Marc Le Bihan" <grunt2@laposte.net>,1072720@bugs.debian.org,team@security.debian.org<br>
Envoyé: vendredi 7 Juin 2024 14:37<br>
Objet : Re: Bug#1072720: libglib2.0-0: Following fix #1070745, typing `A keys doesn't type an À anymore<br>
<div class="gl_quoted">On Fri, 07 Jun 2024 at 13:12:52 +0100, Simon McVittie wrote:<br>
> On Fri, 07 Jun 2024 at 04:50:47 +0200, Marc Le Bihan wrote:<br>
> > * What exactly did you do (or not do) that was effective (or<br>
> > ineffective)?<br>
> > Typing the backtick followed by a wovel: `A<br>
> ><br>
> > * What was the outcome of this action?<br>
> > `A<br>
> ><br>
> > * What outcome did you expect instead?<br>
> > À<br>
><br>
> What desktop environment, what keyboard layout and what input method<br>
> are you using? And what application are you typing this into?<br>
<br>
It would be helpful to run the "im-config" tool, and copy/paste the text<br>
that it displays into a reply to this bug report. What I get in a test<br>
virtual machine is:<br>
<br>
Current configuration for the input method:<br>
* Default mode defined in /etc/default/im-config: 'auto'<br>
* Active configuration: 'missing' (normally missing)<br>
* Normal automatic choice: 'ibus' (normally ibus or fcitx5)<br>
* Override rule: 'zh_CN,fcitx5:zh_TW,fcitx5:zh_HK,fcitx5:zh_SG,fcitx5'<br>
* Current override choice: '' (Locale='en_GB')<br>
* Current automatic choice: 'ibus'<br>
* Number of valid choices: 1 (normally 1)<br>
* Desktop environment: 'GNOME'<br>
The configuration set by im-config is activated by re-starting the system.<br>
Explicit selection is not required to enable the automatic<br>
configuration, if the active one is default/auto/cjkv/missing.<br>
<br>
but your result is presumably different.<br>
<br>
I attempted to reproduce this problem in a virtual machine with:<br>
<br>
* Debian 12<br>
* GNOME<br>
* German keyboard layout (configured in Settings → Keyboard → Input Sources):<br>
https://en.wikipedia.org/wiki/QWERTZ#/media/File:German-Keyboard-Layout-T2-Version1-large.png<br>
* gnome-text-editor or Libreoffice Writer as the application<br>
<br>
GNOME uses ibus as its input method for most languages, including English<br>
and German. ibus is the input method that was affected by #1070745.<br>
<br>
I was unable to reproduce the bug with this combination of settings:<br>
<br>
When I press the key that would be printed with acute [´] and grave [`]<br>
accents on a German keyboard (2 positions to the right of the [0] key),<br>
the application displays the accent with an underline (acute accent<br>
´ U+00B4 if I do not use Shift, or grave accent/backtick ` U+0060 if I use<br>
Shift). When I press Shift+[A], the underlined accent gets replaced by<br>
Á or À, as appropriate.<br>
<br>
If I want to type `A with that keyboard layout, I have to press:<br>
Shift+[`], Space, Shift+[A].<br>
<br>
I do not regularly use keyboard layouts that include dead keys, but to<br>
the best of my knowledge, what I described is the expected behaviour<br>
for keyboard layouts that include dead keys. If you would have expected<br>
something different, please describe it.<br>
<br>
If this is not the result that you see, please describe what is different<br>
about your system or how I can reproduce the problem.<br>
<br>
Thanks,<br>
smcv</div>
</div>