It's either a bug or a poorly documented feature, so I think it should be
pursued. If the screensaver is configured to turn off after a certain
period, it should turn off after that period unless one opts out for things
like watching movies in a browser.
On Thu, Aug 2, 2018 at 6:28 AM, gf <email address hidden> wrote:
> Hi David. So, do you want to persue this issue or should we close the
> ticket?
> Take care
> :)
> G
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1625441
>
> Title:
> KDE screen lock intermittent
>
> Status in kscreenlocker package in Ubuntu:
> Incomplete
>
> Bug description:
> I have my KDE screen locker configured to "Lock screen automatically
> after" 1 minute. Sometimes it does, sometimes it doesn't. When it
> doesn't, I can lock manually with Ctrl-Alt-L. I upgraded from 14.04
> to 16.04.1 ~4 days ago, and it has stopped locking 3 or 4 times. It
> was working fine in 14.04. It's particularly annoying for me because I
> use my screen saver status and my workspace name to log my hours to
> various charge numbers for work. If the screen saver isn't on, I'm
> logging hours.
>
> I wasn't sure what component to file a bug against. I assume
> libkscreenlocker5 (there is no kscreenlocker package AFAICT).
>
> apt-cache policy libkscreenlocker5
> libkscreenlocker5:
> Installed: 5.5.5-0ubuntu1
> Candidate: 5.5.5-0ubuntu1
> Version table:
> *** 5.5.5-0ubuntu1 500
> 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64
> Packages
> 100 /var/lib/dpkg/status
>
> Other info:
> I've tried 5 minute locking intervals and changing the interval during
> the KDE session where locking isn't working... no change.
>
> I've looked through all of my workspaces to see if there might be some
> dialogue window or panel widget expecting user interaction that might
> be disabling the timeout mechanism or something like that. I didn't
> find anything of that sort, but I just closed all windows except the
> firefox window in which I'm typing this question (emacs, thunderbird,
> octave, gramps, google-chrome, konsole, + ???) and the screen saver
> worked after that. I'm not sure if that was coincidence or not. I
> re-opened an instance of every app that I remember having closed and
> the screen saver worked again.
>
> This is a new Ubuntu 16.04.1 64 bit installation that was converted to
> KDE by installing kde-desktop. The user account that I'm using has
> its home on another disk and that home directory has been on 12.04 and
> 14.04 systems.
>
> I'm not sure if this is anyway related, but I get a "System
> Notification Helper" popup window many hundreds of time per day that
> says "Software upgrade notifications are available". Perhaps that
> popup window is causing the screen locker to thing there is something
> going on.
>
> I'm not sure how to capture useful debugging information for something
> that isn't happening. Is there a way to query the screen locker and
> ask it what it thought happened that prevented it from locking?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/kscreenlocker/+
> bug/1625441/+subscriptions
>
It's either a bug or a poorly documented feature, so I think it should be
pursued. If the screensaver is configured to turn off after a certain
period, it should turn off after that period unless one opts out for things
like watching movies in a browser.
On Thu, Aug 2, 2018 at 6:28 AM, gf <email address hidden> wrote:
> Hi David. So, do you want to persue this issue or should we close the /bugs.launchpad .net/bugs/ 1625441 us.archive. ubuntu. com/ubuntu xenial/universe amd64 dpkg/status /bugs.launchpad .net/ubuntu/ +source/ kscreenlocker/ + +subscriptions
> ticket?
> Take care
> :)
> G
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> KDE screen lock intermittent
>
> Status in kscreenlocker package in Ubuntu:
> Incomplete
>
> Bug description:
> I have my KDE screen locker configured to "Lock screen automatically
> after" 1 minute. Sometimes it does, sometimes it doesn't. When it
> doesn't, I can lock manually with Ctrl-Alt-L. I upgraded from 14.04
> to 16.04.1 ~4 days ago, and it has stopped locking 3 or 4 times. It
> was working fine in 14.04. It's particularly annoying for me because I
> use my screen saver status and my workspace name to log my hours to
> various charge numbers for work. If the screen saver isn't on, I'm
> logging hours.
>
> I wasn't sure what component to file a bug against. I assume
> libkscreenlocker5 (there is no kscreenlocker package AFAICT).
>
> apt-cache policy libkscreenlocker5
> libkscreenlocker5:
> Installed: 5.5.5-0ubuntu1
> Candidate: 5.5.5-0ubuntu1
> Version table:
> *** 5.5.5-0ubuntu1 500
> 500 http://
> Packages
> 100 /var/lib/
>
> Other info:
> I've tried 5 minute locking intervals and changing the interval during
> the KDE session where locking isn't working... no change.
>
> I've looked through all of my workspaces to see if there might be some
> dialogue window or panel widget expecting user interaction that might
> be disabling the timeout mechanism or something like that. I didn't
> find anything of that sort, but I just closed all windows except the
> firefox window in which I'm typing this question (emacs, thunderbird,
> octave, gramps, google-chrome, konsole, + ???) and the screen saver
> worked after that. I'm not sure if that was coincidence or not. I
> re-opened an instance of every app that I remember having closed and
> the screen saver worked again.
>
> This is a new Ubuntu 16.04.1 64 bit installation that was converted to
> KDE by installing kde-desktop. The user account that I'm using has
> its home on another disk and that home directory has been on 12.04 and
> 14.04 systems.
>
> I'm not sure if this is anyway related, but I get a "System
> Notification Helper" popup window many hundreds of time per day that
> says "Software upgrade notifications are available". Perhaps that
> popup window is causing the screen locker to thing there is something
> going on.
>
> I'm not sure how to capture useful debugging information for something
> that isn't happening. Is there a way to query the screen locker and
> ask it what it thought happened that prevented it from locking?
>
> To manage notifications about this bug go to:
> https:/
> bug/1625441/
>