← Back to team overview

kernel-packages team mailing list archive

[Bug 1529049] Re: Switch bluetooth keyboard from qwerty to azerty


Just remember, there are serveral users, who are using their system with
diffrent language settings for the Display Language and the Keyboard
Character Map. For example I am using my UbuntuPhone with english
Display Language but I have a german Keyboard (qwertz). I. e. simply
choosing the character map by the systems Display Language will not be

So I think the best way of integration would be to add a settings menu for connected bluetooth keyboards. I'm trying to explain in detail what I mean:
If I open settings>bluetooth, then I can see my already paired bluetooth keyboard device. Then I can tap to the device and I can see the devices menu with information about Name, Type, Status and Signal Strenth and so on... It would be the best to add in this menu a further entry  tochange the Keyboard character map. 

Nevertheless, the Display Language setting should affect the default
Keyboard chracter map.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.

  Switch bluetooth keyboard from qwerty to azerty

Status in ubuntu-keyboard:
Status in bluez package in Ubuntu:

Bug description:
  Trying convergence, I've noticed that :

  When a bluetooth keyboard is paired, the keyboard is by default in
  Qwerty (even if it's an Azerty keyboard and the settings of UT are on
  French Azerty keyboard layout)

  We should have an option to set the Azerty / Qwerty option in bluetooth settings.
  Or a better solution could be that the bluetooth keyboard layout is set to the default keyboard layout we have put in Language settings.

  Does someone know a way to set correctly the layout of the bluetooth
  keyboard ? (I've tried : 'loadkeys fr' in terminal but this didn't
  work, I suspect that the default layout was already on fr but the
  bluetooth keyboard doesn't detect it)

  Device : mako rc-proposed last revision of 24 dec 2015

To manage notifications about this bug go to: