Bug 489826

Summary:	Input Error if decimal values less than one entered without leading Zero
Product:	[Applications] kcalc	Reporter:	cat22 <erbenton>
Component:	general	Assignee:	Evan Teran <evan.teran>
Status:	RESOLVED FIXED
Severity:	normal	CC:	filip.kendes1, gabriel.barrantes.dev
Priority:	NOR
Version First Reported In:	24.05.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	fixed in 24.05.2

Description cat22 2024-07-06 12:00:40 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
if you try a simple calculation with 2 numbers and either of them is less than one then if you do not enter a leading zero before the decimal point you get an Input Error

STEPS TO REPRODUCE (hit AC before each step)
1.  Enter this: 16 x .2 =
     The result is Input Error
2. Enter this: 16 x 0.2 =
   The result is computed correctly and no error is reported
3. 

OBSERVED RESULT
Input Error

EXPECTED RESULT
Same as step 2

SOFTWARE/OS VERSIONS
Linux: openSuse Tumbleweed x86_64
KDE  Plasma 6.1.2 (as reported by "grep X-KDE-PluginInfo-Version /usr/share/xsessions/plasma6.desktop" )
Qt: 5.15.14 ( as reported by "qtpaths --qt-version" )
From kcalc About:
KDE Frameworks Version:  6.3.0
Qt Version:  built against 6.7.2

Comment 1 Filip 2024-07-06 12:42:12 UTC

Created attachment 171420 [details]
fixed in 24.05.2

Comment 2 Filip 2024-07-06 12:43:22 UTC

This should be fixed in 24.05.2. Can you wait for that version of the KCalc in your distro and see if it's fixed? If not please report the issue again.

Comment 3 cat22 2024-07-06 17:51:35 UTC

openSuse Tumbleweed updates frequently so once they are aware of this change it should be quickly available.
I will keep an eye out and report back when I see and test 24.05.02
Thanks for the quick response to fix this.

Comment 4 Filip 2024-07-06 18:15:48 UTC

I can't take credit for this personally because I didn't fix it. Someone much smarter than me did it. Hopefully it will be resolved for you when you update it.

Comment 5 cat22 2024-07-09 07:33:36 UTC

This issue  is  fixed. BUT I found another issue. I'll file it rather than belabor it here