Bug 742504 - qtiplot-0.9.8.3 crashes when rescaling a graph
Summary: qtiplot-0.9.8.3 crashes when rescaling a graph
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: qtiplot
Version: 16
Hardware: i386
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-30 10:51 UTC by aeschulz
Modified: 2011-12-26 22:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-26 22:22:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description aeschulz 2011-09-30 10:51:20 UTC
Description of problem:
QtiPlot crashes when resizing a graph

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

How reproducible:
Reproducible

Steps to Reproduce:
1. Open QtiPlot
2. Make a table with two rows and fill in randon values, e.g.:

  1   30
  2   10
  3   40
  5   81

3. Plot a 2D-Line Graph
4. Open another table
5. Click again into the graph
6. Right-click on the y-axis, select "Scale" and change to "from" and the "to" values
7. Program crashes without further notice 
  
Actual results:
Program crashes

Expected results:
Graph is plotted with the new scale

Additional info:
QtiPlot as several errors in this build, compare bug 740816

Comment 1 aeschulz 2011-11-10 12:18:51 UTC
Problem is still present in Fedora 16

Comment 2 Alex Lancaster 2011-12-26 22:22:17 UTC
It looks like the package was retired and orphaned back in July 2011.  See:

http://pkgs.fedoraproject.org/gitweb/?p=qtiplot.git;a=blob;f=dead.package;h=6c90bdc8768fc421bae28dabe5c08e13cbcd8a84;hb=3ca38e44a89aff4416c25f82f3df0455fbc6f82b

and:

https://admin.fedoraproject.org/pkgdb/acls/name/qtiplot

So it was never explicitly built for f16, in any case.  I'm going to close this as WONTFIX, if you can convince another maintainer to pickup the package, then feel free to re-open the bug.


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