https://bugs.kde.org/show_bug.cgi?id=497561
--- Comment #4 from jordy.swigg...@gmail.com --- Also see this thread i posted back when i was first writing the script: https://discuss.kde.org/t/qdbus-kreadconfig5-method-to-find-screen-lock-setting-status-and-lock-timer/18400/2 Kind regards On Mon, Dec 16, 2024, 18:51 Jordy Swiggers <jordy.swigg...@gmail.com> wrote: > Hi Nicolas, > > First of all thank you for taking the time to reply. > > The thing is that i have been using both commands in a custom Intune > compliancy script for several months, up until very recently they were most > definitely returning "true" and "5". > > The whole script is based around the lock enabled being true and the lock > delay less than or equal to 10. > > Kind regards, Jordy > > > On Mon, Dec 16, 2024, 18:33 Nicolas Fella <bugzilla_nore...@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=497561 >> >> Nicolas Fella <nicolas.fe...@gmx.de> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| |nicolas.fe...@gmx.de >> >> --- Comment #2 from Nicolas Fella <nicolas.fe...@gmx.de> --- >> This is working as designed. Only non-default values are written to the >> config >> file, so querying a value that is at the default will return nothing. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
