XKB layout variants not shown in the menu of respective language but under Others

[Dee Winthrop]

[Impact]

The GUI in gnome-control-center for adding input sources is broken. The XKB layout variants should be visible in the menu of respective language, but instead they are all shown under "Others".

The issue has a potential to cause confusion for a lot of users.

[Test Plan]

1. Open Settings -> Region & Language and press the + button
   to open the window for adding input sources.

2. Click "English (United States)".

-> Find far fewer options than expected

3. Install the gnome-desktop3 binaries from hirsute-proposed and
   relogin (or possibly reboot).

4. Repeat 1. and 2.

-> Find the expected input source options

[Where problems could occur]

The fix is a cherry picked oneliner which was committed upstream on February 16 in order to address this issue. Very hard to see how it would affect anything else adversely.

[Original description]

Ubuntu 21-04 installed from scratch (on dual-boot) a few days before stable release.

To be able to switch to a language that requires a keyboard different than my own, I used the GUI's "language and region" settings > "manage installed languages" > install/remove languages. I found "Russian" and it was added. Next i pressed the + sign. Selecting "Russian (Russian Federation)" yielded 2 keyboards: "Russian", "Russian (Polyglot and Reactionary)".

Neither keyboard was "phonetic". The phonetic keyboard has been with the standard Ubuntu installs for at least ten years.

According to Gunnar Hjalmarsson "Ubuntu 21.04 is shipped with the same version of the xkb-data package as in 20.04 and 20.10, so nothing has changed. And multiple variants are available, including the one named Russian (phonetic)." So this should be fairly easy to fix, no?

I find that the language settings are a little too complicated for me to tamper with on the terminal, but I am including the information I was able to collect:

~$ locale -a
C
C.UTF-8
en_AG
en_AG.utf8
...
nb_NO.utf8
POSIX
ru_RU.utf8
ru_UA.utf8

$ setxkbmap -print -verbose
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+inet(evdev)
geometry: pc(pc105)
xkb_keymap {
 xkb_keycodes { include "evdev+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+us+inet(evdev)" };
 xkb_geometry { include "pc(pc105)" };
};

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 23 13:51:25 2021
InstallationDate: Installed on 2021-04-19 (3 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

[Gunnar Hjalmarsson (gunnarhj)]

I asked a question at <https://askubuntu.com/q/1333206>. Let's keep talking there until we have concluded that you likely stumbled upon a bug.

[Gunnar Hjalmarsson (gunnarhj)]

Well, this is indeed an ugly bug, and it affects not only Russian.

Downgrading g-c-c does not help, so it's probably not really a g-c-c bug. Still keeping it as a g-c-c bug pending further investigation.

[Gunnar Hjalmarsson (gunnarhj)]

The issue is present also in an "Ubuntu on Xorg" session.

[Gunnar Hjalmarsson (gunnarhj)]

Downgrading the packages built by the gnome-desktop3 source package to the groovy version fixes the issue.

[Sebastien Bacher (seb128)]

It's weird that downgrading gnome-desktop binaries fixes the issue since there is no actual changes to the source between the versions, it was mostly just version bumps for the GNOME about dialog...

[Gunnar Hjalmarsson (gunnarhj)]

@Seb: I tested with the groovy version of gnome-desktop.

[Gunnar Hjalmarsson (gunnarhj)]

Here is a quick-and-dirty solution:

https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-desktop3

Those patches are in Debian too, and the issue is present also on Debian testing. Probably a reason for a last minute change there.

[Brian Murray (brian-murray)]

Hello Dee, or anyone else affected,

Accepted gnome-desktop3 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-desktop3/3.38.5-1ubuntu2~21.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Gunnar Hjalmarsson (gunnarhj)]

I verified the test plan using version 3.38.5-1ubuntu2~21.04.1 of
- libgnome-desktop-3-19
- gnome-desktop3-data
- gir1.2-gnomedesktop-3.0
from hirsute-proposed.

[Dee Winthrop (deewi)]

I "enabled proposed" as explained on https://wiki.ubuntu.com/Testing/EnableProposed, updated software and I'm afraid the results are discouraging:

Having removed "Russian phonetic" (which had been added from "others"), I added Russian from "Manage installed languages", then clicked the + sign but that simply closed the settings. I repeated the process a few times after rebooting. The plus sign merely shut down the entire settings GUI.

Clicking the + sign should normally have opened up all the languages I had added in "Manage installed languages" and their variants.

[Sebastien Bacher (seb128)]

Could you start gnome-control-center from a cmdline and copy here any error that is printed when the settings are closing?

[Dee Winthrop (deewi)]

No erorr messae! The settings GUI opened promptly and the language
settings worked perfectly.

On 28.04.2021 15:59, Sebastien Bacher wrote:
> Could you start gnome-control-center from a cmdline and copy here any
> error that is printed when the settings are closing?
>

[Dee Winthrop (deewi)]

Sorry - that was wrong.
(I was using the wrong PC)
Error:
"Segmentation fault (core dumped)"

[Dee Winthrop (deewi)]

And the settings closed when I pressed the +

[Sebastien Bacher (seb128)]

it makes sense that it's segfault, do you have a report in /var/crash you could submit with ubuntu-bug? If not could you follow the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash to get a gdb backtrace?

[Dee Winthrop (deewi)]

There were two files. The other one _usr_bin_gnome-control-center.1000
was 8.3 MB. do you need that?

On 28.04.2021 16:27, Sebastien Bacher wrote:
> it makes sense that it's segfault, do you have a report in /var/crash
> you could submit with ubuntu-bug? If not could you follow the
> instructions on https://wiki.ubuntu.com/DebuggingProgramCrash to get a
> gdb backtrace?
>

[Dee Winthrop (deewi)]

Sorry, I see that what I sent you is probably useless. I'll try the gdb
backtrace procedure.

On 28.04.2021 16:27, Sebastien Bacher wrote:
> it makes sense that it's segfault, do you have a report in /var/crash
> you could submit with ubuntu-bug? If not could you follow the
> instructions on https://wiki.ubuntu.com/DebuggingProgramCrash to get a
> gdb backtrace?
>

[Sebastien Bacher (seb128)]

yes, use ubuntu-bug on it and it should create a report then share the url or reference

[Dee Winthrop (deewi)]

$ gdb gnome-control-center
returns;
Reading symbols from gnome-control-center...

(No debugging symbols found in gnome-control-center)

(gdb)

In ubuntu-bug : I did not know what to call it. This is the link:
https://bugs.launchpad.net/ubuntu/+bug/1926473

On 28.04.2021 16:27, Sebastien Bacher wrote:
> it makes sense that it's segfault, do you have a report in /var/crash
> you could submit with ubuntu-bug? If not could you follow the
> instructions on https://wiki.ubuntu.com/DebuggingProgramCrash to get a
> gdb backtrace?
>

[Sebastien Bacher (seb128)]

Getting a backtrace manually isn't trivial, you need to install the debug packages yourself and get the backtrace following https://wiki.ubuntu.com/Backtrace by typing commands on the gdb prompt

The easiest way is to use apport as documented on the wikipage pointed previously

Did you try to $ ubuntu-bug /var/crash/_usr_bin_gnome-control-center.1000 ?

[Gunnar Hjalmarsson (gunnarhj)]

On 2021-04-28 15:09, Dee Winthrop wrote:
> I "enabled proposed" as explained on
> https://wiki.ubuntu.com/Testing/EnableProposed, updated software

Did you update also other packages from hirsute-proposed but those I mentioned in comment #11?

Did you relogin/reboot after the update?

> Clicking the + sign should normally have opened up all the languages
> I had added in "Manage installed languages" and their variants.

Right.

[Dee Winthrop (deewi)]

Yes, I updated all. shouldn't I have done that? I did reboot several times.

On 28.04.2021 21:07, Gunnar Hjalmarsson wrote:
> On 2021-04-28 15:09, Dee Winthrop wrote:
>> I "enabled proposed" as explained on
>> https://wiki.ubuntu.com/Testing/EnableProposed, updated software
>
> Did you update also other packages from hirsute-proposed but those I
> mentioned in comment #11?
>
> Did you relogin/reboot after the update?
>
>> Clicking the + sign should normally have opened up all the languages
>> I had added in "Manage installed languages" and their variants.
>
> Right.
>

[Dee Winthrop (deewi)]

Now that I think I finally found out how to send the /var/crash report,
I'm no longer getting a report when I run gnome-control-center from
command line. The one I have is from 16.13 even though I added 'Crash'
to the "problem" line in /etc/apport/crashdb.conf

What I can do is to reinstall and see what happens then. Let me know if
you want me to do that.

On 28.04.2021 21:56, Gunnar Hjalmarsson wrote:
> ** Changed in: gnome-desktop3 (Ubuntu)
> Status: In Progress => Fix Committed
>

[Sebastien Bacher (seb128)]

Try cleaning /var/crash and it should generate a new one

[Dee Winthrop (deewi)]

Nope. I delete the files, ran gnome-control-center, rebooted and...

VLT-WX0:/var/crash$ ls -l

total 0

On 28.04.2021 22:57, Sebastien Bacher wrote:
> Try cleaning /var/crash and it should generate a new one
>

[Dee Winthrop (deewi)]

I think I should reinstall Hirsute. Takes less than 30 minutes.

On 28.04.2021 23:16, Katjana Edwardsen wrote:
> Nope. I delete the files, ran gnome-control-center, rebooted and...
>
> VLT-WX0:/var/crash$ ls -l
>
> total 0
>
>
>
> On 28.04.2021 22:57, Sebastien Bacher wrote:
>> Try cleaning /var/crash and it should generate a new one
>>

[Gunnar Hjalmarsson (gunnarhj)]

On 2021-04-28 22:36, Dee Winthrop wrote:
> Yes, I updated all. shouldn't I have done that?

No, to verify a change to a particular package it's advisable to only update the binaries of that package.

But what you did may possibly help us identify some other issue. ;)

> I did reboot several times.

Ok.

[Dee Winthrop (deewi)]

Meanwhile, I have reinstalled. I have done nothing else except enable
this email address and add "Russian" in my language settings.

Clicking the + sign no longer crashes the GUI, but opens "Add an input
source". I have the choice of English and Russian (Russian Federation).
(Norwegian keyboard is already default.)

Running gnome-congrol-center from command line does not generate any
error message and there is nothing in /var/cahe.

On 28.04.2021 23:27, Gunnar Hjalmarsson wrote:
> On 2021-04-28 22:36, Dee Winthrop wrote:
>> Yes, I updated all. shouldn't I have done that?
> No, to verify a change to a particular package it's advisable to only
> update the binaries of that package.
>
> But what you did may possibly help us identify some other issue. ;)
>
>> I did reboot several times.
> Ok.
>

[Dee Winthrop (deewi)]

Since you mention "other issues", I would like to point to bug 1926083
(broken autocorrect) which I now tested again on default language (US
English) Could it be related?

On 28.04.2021 23:27, Gunnar Hjalmarsson wrote:
> On 2021-04-28 22:36, Dee Winthrop wrote:
>> Yes, I updated all. shouldn't I have done that?
>
> No, to verify a change to a particular package it's advisable to only
> update the binaries of that package.
>
> But what you did may possibly help us identify some other issue. ;)
>
>> I did reboot several times.
>
> Ok.
>

[Dee Winthrop (deewi)]

Finally, I'm attaching a screenshot of "proposed" updates. I have not
installed them.

On 28.04.2021 23:27, Gunnar Hjalmarsson wrote:
> On 2021-04-28 22:36, Dee Winthrop wrote:
>> Yes, I updated all. shouldn't I have done that?
> No, to verify a change to a particular package it's advisable to only
> update the binaries of that package.
>
> But what you did may possibly help us identify some other issue. ;)
>
>> I did reboot several times.
> Ok.
>

[Gunnar Hjalmarsson (gunnarhj)]

No, that's most likely unrelated.

[Gunnar Hjalmarsson (gunnarhj)]

I would suggest that you open a terminal window and run:

sudo apt install libgnome-desktop-3-19 gnome-desktop3-data gir1.2-gnomedesktop-3.0

Then disable hirsute-proposed and run:

sudo apt update

Finally relogin or reboot, and hopefully you'll notice an improvement. :)

[Dee Winthrop (deewi)]

$ sudo apt install libgnome-desktop-3-19 gnome-desktop3-data
gir1.2-gnomedesktop-3.0
[sudo] password for ###
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
gnome-desktop3-data is already the newest version (3.38.5-1ubuntu1).
libgnome-desktop-3-19 is already the newest version (3.38.5-1ubuntu1).
0 upgraded, 0 newly Shoulinstalled, 0 to remove and 0 not upgraded.
gir1.2-gnomedesktop-3.0: command not found

should I: apt install gir1.2-gnomedesktop-3.0  ?

On 29.04.2021 01:29, Gunnar Hjalmarsson wrote:
> I would suggest that you open a terminal window and run:
>
> sudo apt install libgnome-desktop-3-19 gnome-desktop3-data
> gir1.2-gnomedesktop-3.0
>
> Then disable hirsute-proposed and run:
>
> sudo apt update
>
> Finally relogin or reboot, and hopefully you'll notice an improvement.
> :)
>

[Dee Winthrop (deewi)]

I see that gir1.2-gnomedesktop-3.0 is already installed.

On 29.04.2021 01:29, Gunnar Hjalmarsson wrote:
> I would suggest that you open a terminal window and run:
>
> sudo apt install libgnome-desktop-3-19 gnome-desktop3-data
> gir1.2-gnomedesktop-3.0
>
> Then disable hirsute-proposed and run:
>
> sudo apt update
>
> Finally relogin or reboot, and hopefully you'll notice an improvement.
> :)
>

[Gunnar Hjalmarsson (gunnarhj)]

I got the impression that you had enabled hirsute-proposed...

These steps should do it:

1. Open Software & Updates and check Pre-released updates in the Developer Options tab.

2. sudo apt update

3. sudo apt install libgnome-desktop-3-19 gnome-desktop3-data gir1.2-gnomedesktop-3.0

(note: That's one single line, even if Launchpad breaks it up.)

4. Open Software & Updates and uncheck Pre-released updates in the Developer Options tab.

5. sudo apt update

6. Relogin/reboot.

[Dee Winthrop (deewi)]

YES!!!

Thank you thank your thank you:-)

On 29.04.2021 10:55, Gunnar Hjalmarsson wrote:
> I got the impression that you had enabled hirsute-proposed...
>
> These steps should do it:
>
> 1. Open Software & Updates and check Pre-released updates in the
> Developer Options tab.
>
> 2. sudo apt update
>
> 3. sudo apt install libgnome-desktop-3-19 gnome-desktop3-data
> gir1.2-gnomedesktop-3.0
>
> (note: That's one single line, even if Launchpad breaks it up.)
>
> 4. Open Software & Updates and uncheck Pre-released updates in the
> Developer Options tab.
>
> 5. sudo apt update
>
> 6. Relogin/reboot.
>

[Gunnar Hjalmarsson (gunnarhj)]

Good to hear that you now see the difference. And thank *you* for calling our attention to it — first at Ask Ubuntu and then here. That will make it possible to get the fix out to everyone early (in about a week).

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-desktop3 - 3.38.5-1ubuntu2

---------------
gnome-desktop3 (3.38.5-1ubuntu2) impish; urgency=medium

  * d/p/xkbinfo-Update-iso639Ids-correctly-in-evdev.patch:
    - Fix issue in g-c-c GUI for adding input source (LP: #1925792)

 -- Gunnar Hjalmarsson <email address hidden> Wed, 28 Apr 2021 21:46:04 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-desktop3 - 3.38.5-1ubuntu2~21.04.1

---------------
gnome-desktop3 (3.38.5-1ubuntu2~21.04.1) hirsute; urgency=medium

  * d/p/xkbinfo-Update-iso639Ids-correctly-in-evdev.patch:
    - Fix issue in g-c-c GUI for adding input source (LP: #1925792)

 -- Gunnar Hjalmarsson <email address hidden> Mon, 26 Apr 2021 14:03:17 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for gnome-desktop3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Sebastien Bacher (seb128)]

One follow up here, the segfault mentioned in the discussion was probably bug #1933022 which happens when the show-all-sources gsettings configuration is set and is fixed upstream now