Your message dated Wed, 29 May 2013 06:25:37 +1000
with message-id <[email protected]>
and subject line Done: gnumeric: Segmentation fault upon pasting into various
graph attribute fields
has caused the Debian Bug report #615992,
regarding gnumeric: Segmentation fault upon pasting into various graph
attribute fields
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
615992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615992
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnumeric
Version: 1.10.8-1squeeze5
Severity: normal
Bug can be easily reproduced:
1. start gnumeric
2. click "Insert a Chart" button
3. Choose "column" for "Plot type" (various other types crash too, but not
"XY" type)
4. Click "Insert", and drag across any region to insert the graph
5. Double click graph
6. In the attribute list, choose "Series 1"
7. Choose Data tab
8. Copy the "Values" field (should be something like 'Sheet1!$A$1')
9. Paste this into the "(Labels):" field --> SegFault crash
Also crashes with real graphs and legitimate pastes (the above example uses a
blank graph as a simple means to reproduce crash). Also crashes pasting into
Absolute error bar "Values" field.
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Package: gnumeric
Version: 1.10.9-1
Closing old bug that was fixed long ago...
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
--- End Message ---
