Summary: | kblankscrn.kss starts on each login | ||
---|---|---|---|
Product: | [Unmaintained] kscreensaver | Reporter: | RussianNeuroMancer <russianneuromancer> |
Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | drf |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
RussianNeuroMancer
2010-04-29 13:19:30 UTC
did you by any chance configure auto-login and check the "lock session" box? an alternative explanation would be a messed up power saving profile. > did you by any chance configure auto-login and check the "lock session" box? No, auto-login not configured, lock session box not checked, screensaver not enabled. > an alternative explanation would be a messed up power saving profile. What you mean? (In reply to comment #3) > What you mean? > system settings => power management => edit profiles I know, but what you mean when say "messed up"? e.g., "when system is idle for more than" "0m" "lock screen". an alternative would be "general settings" => "lock screen on resume" and it tries to "do something" immediately after logging in, but fails and only the lock is left behind. No, I check all profile - all is fine, looks like default profiles. that's weird. try "ps xuf". is it obvious what launched the process? if not, replace the executable with a script which calls that command and check ~/.xsession-errors after a re-start. The problem is not reproduced for me in Kubuntu 10.04 LTS release. Probably this bug is fixed after update from Beta to Release version of Kubuntu 10.04 LTS. |