Bug 150117 - Language change is impossible for unlocking session when screensaver is running
Summary: Language change is impossible for unlocking session when screensaver is running
Status: RESOLVED DUPLICATE of bug 332496
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-23 14:28 UTC by Pavel Gurevich
Modified: 2015-01-23 14:41 UTC (History)
2 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 Pavel Gurevich 2007-09-23 14:28:09 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

After screensaver has started, the only way to change language in password entry dialog is using mouse or navigating via <Tab>. This is especially relevant for non-Latin languages like Russian where the specified shortcut (the underlined letter) stop working. It is not handy at all and there should be a better way of changing language to improve usability.

Thank you!
Comment 1 Oswald Buddenhagen 2007-11-01 20:43:00 UTC
it's beyond me what you imagine we could do about this ...
Comment 2 Pavel Gurevich 2007-11-02 18:31:57 UTC
Well, enabling the standard (Ctrl-Alt-K) or a configurable custom shortcut would suffice.

Thanks!
Comment 3 Andriy Rysin 2007-11-07 04:36:19 UTC
Well I don't think we want to enable global shortcuts in screensaver, plus even if we did it would not update the keyboard layout button screensaver uses in KDE3. Alternative is for screensaver to take over keyboard layout shortcut and react to it locally switching layouts.
Though I don't think anybody will consider this for KDE3 especially taking to account that there's easy workarounds: clicking with mouse or tabbing to the button and pressing with space...
Comment 4 Johannes Rohr 2012-07-01 07:35:55 UTC
I was just hit by this bug as well. It didn't even occur to me, that the two-letter code for the active keymap to the right of the lock dialogue might be clickeable. So I thought, that I'm simply lost here and thus I switched to the console and killed the screensaver process from there.

So it would already be a huge improvement if it would appear as a drop-down menu or something similar, indicating that this is an interactive UI element and not a mere indicator as I thought until reading this report.
Comment 5 Martin Flöser 2015-01-23 14:41:46 UTC

*** This bug has been marked as a duplicate of bug 332496 ***