Bug 189064 - Wish: "Enable Passwordless Logins" applies to wake from Sleep, Hibernate
Summary: Wish: "Enable Passwordless Logins" applies to wake from Sleep, Hibernate
Status: RESOLVED INTENTIONAL
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR minor
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-07 20:10 UTC by Jeffrey
Modified: 2016-04-24 20:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey 2009-04-07 20:10:42 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When I set up "Enable Passwordless Logins" i would like this to also apply to the system when it is waking from sleep or hibernate, and not only to a new session.

KDE 4.2 rocks, thanks a lot developers and the rest!
Comment 1 Oswald Buddenhagen 2009-06-01 13:12:10 UTC
i assume you mean auto-login not password-less-login, as the latter should just work.
but if you want to auto-login after wakeup anyway, i wonder why you would log out before suspending in the first place?

please reopen if you can come up with convincing use cases.
Comment 2 Jeffrey 2009-06-01 15:51:49 UTC
I suppose that both would be good options, but currently I have a computer set up to auto-login upon bootup.  I've also set that account (within KDE SystemSettings) to be able to login from KDM without a password.

When the computer wakes from sleep or hibernate, there is a locked KDE session, much like when stopping a screensaver that has been instructed to lock the computer.  This (waking from sleep or hibernate) is where I'd like to be able to password-less-login.  I believe my initial request is still valid.
Comment 3 Oswald Buddenhagen 2009-06-01 15:57:13 UTC
ahhh ... then *say* that you mean the screen locker which comes up after resuming. :-D

yeah, this inconsistency is actually a minor bug.
Comment 4 Jeffrey 2009-11-02 21:26:01 UTC
Will this minor bug be fixed for KDE 4.4?
Comment 5 Lamarque V. Souza 2011-04-09 09:33:16 UTC
In KDE SC 4.6 you can disable the sceen locker when resuming. Just right-click on the battery plasmoid -> Engergy save configuration -> uncheck "Lock screen on resume".
Comment 6 Jeffrey 2011-04-11 17:31:17 UTC
> Just right-click on the battery plasmoid -> Engergy save configuration -> uncheck "Lock screen on resume".

Could this be in a better place, rather than within the Battery Settings?  That seems completely unintuitive.  This should be set in the same place as either the Screen Saver or the KDM Auto Login place (or both perhaps).
Comment 7 Lamarque V. Souza 2011-04-11 19:02:15 UTC
Well, it is located there because the other suspend/resume settings are there. Most users may not be interested in kdm auto-login feature at all, so it does not make sense to find this setting there. Another complicator is the fact that kdm run as root and the screen locker run as normal user. The kdm auto-login feature means auto-login when opening a new KDE session. When the session is already opened, which is the screen locker case, kdm auto-login does not apply. Maybe we should change the documentation or add a warning about that.

Screensaver and lock screen are two different features, although many people likes to lock screen when screensaver is launched they do not need to work together. For example, I do not use screensaver at all, but when travelling I set my notebook to lock screen when resuming. Since I am interesting in configuring a setting for after the resume cicle, for me is intuitive to find this setting where the suspend/resume settings are.
Comment 8 Martin Flöser 2015-01-26 07:57:06 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.
Comment 9 rtdvrs 2016-04-24 20:25:37 UTC
Excellent way to fix software; bump the version number and excrete more bits.