Bug 118609 - gnucash stacked barchart legend problem - reversed order of the legend
gnucash stacked barchart legend problem - reversed order of the legend
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: Guppi (Show other bugs)
1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-03-18 03:48 EST by Krzysztof Dubowik
Modified: 2014-03-16 22:43 EDT (History)
1 user (show)

See Also:
Fixed In Version: 0.40.3-18
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-23 16:25:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Proposed patch (2.58 KB, patch)
2004-03-18 04:25 EST, Krzysztof Dubowik
no flags Details | Diff
Spec file for building fixed RPM (4.29 KB, text/plain)
2004-03-18 04:26 EST, Krzysztof Dubowik
no flags Details

  None (edit)
Description Krzysztof Dubowik 2004-03-18 03:48:00 EST
Description of problem:
Guppi has a bug when working under gnucash. When doubleclicking on 
the account name on a stacked barchart GnuCash opens a wrong register 
window or zooms a wrong account. Please see gnucash bugzilla for 
reference: 
http://bugzilla.gnome.org/show_bug.cgi?id=135381
http://bugzilla.gnome.org/show_bug.cgi?id=102268


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

How reproducible:
Always

Steps to Reproduce:
See gnucash bugzilla - bug #135381

Additional info:

There is a patch available in gnucash. I have tested that nad it 
works. I attach the patch file and the spec file I modified from 
Guppi-0.40.3-16.src.rpm
Comment 1 Krzysztof Dubowik 2004-03-18 04:25:20 EST
Created attachment 98643 [details]
Proposed patch
Comment 2 Krzysztof Dubowik 2004-03-18 04:26:03 EST
Created attachment 98644 [details]
Spec file for building fixed RPM
Comment 3 Bill Nottingham 2004-03-23 16:25:23 EST
Added, will be in 0.40.3-18. Thanks!

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