[Bug 2030788] Re: localectl doesn't work in mantic

[James Falcon]

The localectl change in systemd breaks cloud-init as it uses "localectl
set-x11-keymap".

The commit message says "Integration is not set up for now, but GDM
needs to query the configured values. Allow reading, but disallow
setting keymaps."

Is this integration expected to be setup before Mantic releases? If so,
would that fix our behavior? If not, do we need to switch to writing
/etc/vconsole.conf?

Also, it appears that bug referenced in the commit message (#1038762)
does not exist. Is this a typo or a private bug?

** Summary changed:

- localectl doesn't work in mantic
+ "localectl set-x11-keymap" doesn't work in mantic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2030788

Title:
  "localectl set-x11-keymap" doesn't work in mantic

Status in cloud-init package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On the raspi arm64 server image, I used to use cloud-init's keyboard
  module to set my keyboard to GB by default. However, on mantic
  localectl (which the keyboard module uses) is now reporting:

    $ localectl set-x11-keymap gb pc105
    Setting X11 and console keymaps is not supported in Debian

  So ... how do I get my £ key by default now? Or should this be filed
  against systemd as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2030788/+subscriptions