Bug 521073 - Calculator error should be more readable, better error parsing should be implemented
Summary: Calculator error should be more readable, better error parsing should be impl...
Alias: None
Product: Fedora
Classification: Fedora
Component: sugar-calculator
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-09-03 13:34 UTC by Miroslav Vadkerti
Modified: 2010-12-05 06:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-05 06:29:44 UTC
Type: ---

Attachments (Terms of Use)
mixed up screen after a long input in calculator (26.68 KB, image/png)
2009-09-03 13:34 UTC, Miroslav Vadkerti
no flags Details

Description Miroslav Vadkerti 2009-09-03 13:34:05 UTC
Created attachment 359679 [details]
mixed up screen after a long input in calculator

Description of problem:
If you start calculator activity and hit several times Enter, you get an error:

Error at 0: Parse error

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start calculator activity
2. hit Enter button several times
3. observe output
Actual results:
Error at 0: Parse error

Expected results:
No error, blank screen.

Additional info:
Also the input filtering could be better, try to enter a very long number and hit Enter -> the screen gets mixed up. See attached screenshot.

Comment 1 Steven M. Parrish 2009-09-26 22:38:21 UTC
Thanks for the report.  This is an issue that needs to be addressed by the upstream developers.  Please file a report at http://trac.sugarlabs.org/ and once done please add the upstream info to this report.

Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team

Comment 2 Miroslav Vadkerti 2009-09-29 04:46:32 UTC
Reported to upstream developers - see http://bugs.sugarlabs.org/ticket/1446

Comment 3 Bug Zapper 2009-11-16 11:57:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:

Comment 5 Bug Zapper 2010-11-04 10:13:38 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 6 Bug Zapper 2010-12-05 06:29:44 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.