Bluetooth keyboard not respecting locale setting at login

Bug #853416 reported by FreeMinded
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE Base Workspace
Unknown
Medium
kde-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I use a bluetooth keyboard and mouse (Logitech DiNovo). It works great exept that at login (using KDM) the keyboard is always set to US keymap. After the login it gets the correct keymap. Also using a USB keyboard at login works (correct keymap).
This is valid for Kubuntu 11.10 and has been an issue since at least 10.04.

Happy to provide additional information.

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluedevil (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Zinn (michaelgzinn) wrote :

I have this problem, too.

I'm on Ubuntu 11.10, using a German locale with US Dvorak layout that I also modified with xmodmap. I'm using a tiny Apple Bluetooth Keyboard which has the standard US QWERTY layout printed on it.

On the log in screen, it seems to be either US layout or German layout on the bluetooth keyboard (not sure, I can't see what I type). USB keyboards have the correct layout always. Also, once you logged in, the lock screen has the correct layout.

Revision history for this message
FreeMinded (pascal-planetmages) wrote :

I just talked to my favorite KDE developer tonight about this bug. He suposed that the problem is actually KDM not handling Bluetooth inputs correctly. Therefor I'll add KDM as package as well.

affects: bluedevil (Ubuntu) → kde-workspace (Ubuntu)
Revision history for this message
In , Sylvain-audouin (sylvain-audouin) wrote :

On session opening on KDM my bluetooth keyboard is in QWERTY.
On KDE my keyboard is in AZERTY (couse i am french). All is configured in KDE & KDM settings in french.
If i lock my session, my keybord in KDM is in AZERTY for unloking.
If i close my session then re-open it my keyboard is back in QWERTY only on KDM.
If i connect another keybord (wired) it is in AZERTY in KDM/KDE, but my bluetooth keyboard get azerty only if i first press any button on the wired keyboard.

Reproducible: Always

Steps to Reproduce:
1.set up KDM in FR, Use a bluetooth keyboard in KDM it works in QWERTY

Actual Results:
The keyboard is QWERTY even-if all is setup in FR in KDE/KDM

Expected Results:
I just want my bluetooth keyboard work in AZERTY on KDM

Revision history for this message
Harald Sitter (apachelogger) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

Changed in kde-workspace (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
In , FreeMinded (pascal-planetmages) wrote :

Same problem here with german keyboard layout.
Kubuntu 12.04+

See bug report on lauchpad: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/853416

Revision history for this message
FreeMinded (pascal-planetmages) wrote :

Thanks Harald for looking at this bug.
There is actually a report on b.k.o: https://bugs.kde.org/show_bug.cgi?id=303407

Changed in kdebase-workspace:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
In , Chr-asn92-forpub (chr-asn92-forpub) wrote :

Reproduced also with a clean Debian 8.4 install.
Note kdm is not the only display manager to have the problem because I am able to reproduce it with "lightdm" and "xdm". "gdm3" is ok with bluetooth keyboard.

Changed in kdebase-workspace:
status: New → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.