Bug 475477

Summary:	Can't write 3 digits numbers in "switch off after"
Product:	[Applications] systemsettings	Reporter:	Enrico <enricobe>
Component:	kcm_powerdevil	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	kde, natalie_clarius, nate
Priority:	NOR	Keywords:	qt6
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Enrico 2023-10-11 16:42:59 UTC

SUMMARY
***
Hello,
in the Energy Saving page I can't write 3-digits numbers in the "When screen is locked, switch off after:" field.
I can write 99 and go up with the arrows, but I can't write 100
***


STEPS TO REPRODUCE
1. Open Energy Saving page
2. Write 100 on "When screen is locked, switch off after:" field

OBSERVED RESULT
Can't write

EXPECTED RESULT
I should be able to write 100 or any other 3-digits number or I should not be able to go over 99 with the arrows

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-33-generic (64-bit)

Comment 1 Nate Graham 2023-10-12 20:48:12 UTC

That's right, it's limited to 2-digit numbers.

May I ask why you feel the need to go beyond that?

Comment 2 Enrico 2023-10-13 05:43:57 UTC

I run into this "issue" because the lockscreen always broke in a previous version of Neon Unstable, asking for loginctl unlock-session, so I tried to change the energy settings values and run into that little bug.

I think the user should (1) be able to enter a 3-digits number, or (2) should not be able to go over 2-digits number (99) with the arrows buttons
Anyway it's not a big issue and probably affects only few users, so I totally understand if you prefer to focus on something else.
It's a consistency issue more than a bug

Comment 3 Nate Graham 2023-10-13 19:07:23 UTC

So you're trying to use this setting to work around another bug? Do I have this right?

Comment 4 Enrico 2023-10-13 19:32:48 UTC

Yes :-)

Comment 5 Nate Graham 2023-10-13 19:56:45 UTC

Thanks for confirming. I'm afraid we don't support attempts to work around our own bugs. :) I'd recommend that you submit a bug report about the actual issue itself, rather than making a request for a workaround for the issue. If we're going to be making changes, we should just fix the underlying issue itself! Thanks for your understanding.