After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773445 - The calculator's history, in 3.22.0 is now non-selected-able
The calculator's history, in 3.22.0 is now non-selected-able
Status: RESOLVED FIXED
Product: gnome-calculator
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gcalctool maintainers
gcalctool maintainers
https://bugs.launchpad.net/ubuntu/+so...
Depends on:
Blocks:
 
 
Reported: 2016-10-24 22:53 UTC by Toby Lunn
Modified: 2016-11-07 22:25 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22



Description Toby Lunn 2016-10-24 22:53:09 UTC
The calculator's history, in 3.22.0 is now non-selected-able, in 3.18.x this use to be possible was the change intentional?
If not can the change be reverted.

The previous Ubuntu version 3.18 that allowed the use to select a previous calculation to repeat it or edit it then calculate it again. It also allowed the user to select the answer of a previous calculation.
Comment 1 Robert Roth 2016-10-25 03:54:37 UTC
(In reply to Toby Lunn from comment #0)
> The calculator's history, in 3.22.0 is now non-selected-able, in 3.18.x this
> use to be possible was the change intentional?
> If not can the change be reverted.
> 
> The previous Ubuntu version 3.18 that allowed the use to select a previous
> calculation to repeat it or edit it then calculate it again. It also allowed
> the user to select the answer of a previous calculation.

Thank you for taking the time to report the issue. This is a known issue, fixed already in the latest development version, I just did not have the time to backport it to the stable release, but will find the time this week to push a 3.22.2 stable release 
Please note that 3.22.1 is the current stable version, so the distribution will have to package the new version for you to get the update.
Comment 2 Toby Lunn 2016-10-25 11:37:37 UTC
Thanks for the info...
Comment 3 Robert Roth 2016-11-07 22:25:36 UTC
I have just prepared and rolled a 3.22.2 tarball including the fix for this issue.

This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.