Bug 836972

Summary:	Gnome-calculator help says it does not support complex numbers but it does
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Simon <msimon>
Component:	gnome-calculator	Assignee:	Alexander Larsson <alexl>
Status:	CLOSED UPSTREAM	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.0	CC:	mclasen, rstrode, tpelka, vhumpa
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	821425	Environment:
Last Closed:	2015-09-03 18:04:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	821425
Bug Blocks:

Description Martin Simon 2012-07-02 11:15:41 UTC

+++ This bug was initially created as a clone of Bug #821425 +++

Description of problem:
GCalcTool help says it does not support complex numbers but it does. The help should stay actual after feature updates.

Version-Release number of selected component (if applicable):
gcalctool-6.4.1.1-1.fc17.i686

How reproducible:
100%

Steps to Reproduce:
1. Press F1
2. Click Number -> complex numbers
3.
  
Actual results:
Complex numbers are not supported in GCalctool.

Expected results:
The help that explain the work with complex numbers in gcalctool because in Advanced mode there are several functions using complex numbers.

Additional info:
There is probably more feature/help inconsistency, I did not investigate that at all.

Comment 3 Martin Simon 2013-07-29 09:22:53 UTC

The bug is still present in gnome-calculator-3.8.2-1.el7.x86_64

Comment 4 RHEL Program Management 2014-03-22 07:06:46 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 Matthias Clasen 2015-05-01 03:16:15 UTC

Still the case in current release. I've filed an upstream bug.

Comment 7 Matthias Clasen 2015-09-03 18:04:56 UTC

realistically, the only chance that we're ever going to fix this is if an upstream fix comes in as part of a rebase.