Summary: | when keyboard layout switching policy is window, screen saver password should be treated as own window | ||
---|---|---|---|
Product: | [Unmaintained] kscreensaver | Reporter: | Alon Bar-Lev <alon.barlev> |
Component: | kcheckpass | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | arysin, aspotashev, dhameoelin, mgraesslin, prodoomman |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alon Bar-Lev
2010-07-30 20:00:34 UTC
The layout of the unlock password dialog should be always kept as US. Imho (In reply to comment #1) > The layout of the unlock password dialog should be always kept as US. Imho Can't do US as many users don't use default variant for US layout and many users don't even use US for their default layout. (In reply to comment #2) > (In reply to comment #1) > > The layout of the unlock password dialog should be always kept as US. Imho > > Can't do US as many users don't use default variant for US layout and many > users don't even use US for their default layout. It's better to make the default KScreenSaver's layout configurable (separately from the KDE-wide default layout). Seems that switching to screensaver does not generate "window changed" event, so I am not sure how easy it is to provide separate layout for lock dialog. I guess there might be some "lock screen" event but that will take some time to research. So if anybody knows how to do that please let me know. *** This bug has been confirmed by popular vote. *** 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. |