Bug 178480 - kdm keyboard layout, change keyboard.
Summary: kdm keyboard layout, change keyboard.
Status: RESOLVED INTENTIONAL
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-22 16:26 UTC by robert lindgren
Modified: 2015-01-23 14:59 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description robert lindgren 2008-12-22 16:26:01 UTC
Version:           4.1.85 (using Devel)
OS:                Linux
Installed from:    Compiled sources

When the screen is locked, and multiple keyboard layout are available, there is no way to change the layout with the keyboard, one has to use the mouse. This is a regression compared with 3.5.x.

Now when I think of it it might not be kdm's fault? Not sure if the looked screen thingie is part of kdm or not.
Comment 1 Andriy Rysin 2010-11-20 00:30:56 UTC
I think kdm never had a (explicit) way to switch keyboard layouts. The problem is that kdm has very tight code base due to security limitations and it's not even qt application so embedding kde keyboard switcher would be a problem.
Comment 2 Oswald Buddenhagen 2010-11-20 01:22:21 UTC
i don't think you fully understood kdm's architecture, andriy ... ;)

anyway, that's besides the point. the "thing" embedded into the unlock dialog should be operable with the keyboard ... which it actually is: after a lot of tabbing, i can press space to toggle it. dunno what other options exist (or are supposed to), but what i've discovered so far is a bit suboptimal. i think in kde3 times i managed to put the switcher into a sensible tabbing order at least.

i also wonder whether the layout indicator shouldn't be always shown if multiple layouts are configured, irrespective of the tray visibility setting.
Comment 3 Andriy Rysin 2010-11-20 02:05:04 UTC
I can totally believe that, I think I just have seen the comment with such statements on layout indicator in kdm from somebody many years ago and never checked if it was or still is true :)

Not sure why the tabbing order would be a problem, I think by default it should follow the widget creation order. Even if not I think the order can be forced.

Irregardless of that you can switch layout with standard xkb shortcut (i.e. Ctrl+Shift  or whatever is configured in kcm - but not the KDE shortcut as I think kde shortcuts won't work there). It also should react to mouse-click as a toggle - in the end it's just a button.

As to whether it should be visible even if not configured to be visible - it's easy to change but we need to think a bit if it's a good idea to do what they user said they don't want...
Comment 4 Andriy Rysin 2010-11-20 02:06:14 UTC
I can totally believe that, I think I just have seen the comment with such statements on layout indicator in kdm from somebody many years ago and never checked if it was or still is true :)

Not sure why the tabbing order would be a problem, I think by default it should follow the widget creation order. Even if not I think the order can be forced.

Irregardless of that you can switch layout with standard xkb shortcut (i.e. Ctrl+Shift  or whatever is configured in kcm - but not the KDE shortcut as I think kde shortcuts won't work there). It also should react to mouse-click as a toggle - in the end it's just a button.

As to whether it should be visible even if not configured to be visible - it's easy to change but we need to think a bit if it's a good idea to do what they user said they don't want...
Comment 5 Martin Flöser 2015-01-23 14:59:34 UTC
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.