[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting

2023-10-29 Thread Graham Perrin
https://bugs.kde.org/show_bug.cgi?id=440350

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting

2023-05-15 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=440350

--- Comment #44 from John Bennett  ---
(In reply to John Bennett from comment #43)
> Yep, and another fresh install later
> Works fine in Wayland.
> Doesn't work on initial install to X11, but works (generally) on a
> logout/login after...

That should be "Doesn't work on initial boot to X11, ."
Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting

2023-05-15 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=440350

John Bennett  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

--- Comment #43 from John Bennett  ---
Yep, and another fresh install later
Works fine in Wayland.
Doesn't work on initial install to X11, but works (generally) on a logout/login
after...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting

2022-12-11 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=440350

--- Comment #42 from John Bennett  ---
(In reply to John Bennett from comment #41)
> Complete fresh install of Tumbleweed
> (openSUSE-Tumbleweed-DVD-x86_64-Snapshot20221209-Media.iso), no screenlock
> enabled.
> 
> Add the:
> [Daemon]
> Timeout=1
> 
> to the file, logout/in, working so far.

Also (noticed this previously, as well), often (nearly always), after starting
the computer, screenlock doesn't work, but after logging out/in, it does..?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting

2022-12-10 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=440350

--- Comment #41 from John Bennett  ---
Complete fresh install of Tumbleweed
(openSUSE-Tumbleweed-DVD-x86_64-Snapshot20221209-Media.iso), no screenlock
enabled.

Add the:
[Daemon]
Timeout=1

to the file, logout/in, working so far.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting

2022-11-29 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=440350

--- Comment #40 from John Bennett  ---
Beginning to wonder what is going on here...
On occasions (don't believe ALL the time), turn the computer on, no screenlock,
log out/in, screenlock works. Files have not been changed, all looks good...
Beginning to think I will do a full/clean reinstall...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting

2022-11-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=440350

Nate Graham  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME
Summary|Screen never locks  |Screen never locks
   |automatically   |automatically due to
   ||something somewhere
   ||enforcing "never lock" as
   ||the default setting

--- Comment #39 from Nate Graham  ---
Then I am quite confused.

If this behavior happens with no override in ~/.config/kscreenlockerrc, that
means that *somewhere* the default has gotten set to "never lock".

We checked /etc/xdg/kscreenlockerrc and it's not there. Fabian says openSUSE
isn't changing this default in the code. Where else could it be coming from?

-- 
You are receiving this mail because:
You are watching all bug changes.