Bug 710820 – Ctrl-Z - Immediate crash with no warning on undo row height

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 710820 - Ctrl-Z - Immediate crash with no warning on undo row height


Summary:	Ctrl-Z - Immediate crash with no warning on undo row height


Status:	RESOLVED DUPLICATE of bug 649139

Product:	Gnumeric
Classification:	Applications
Component:	Main System
Version:	1.10.x
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	Jody Goldberg
QA Contact:	Jody Goldberg

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-10-24 16:48 UTC by Gordon R. Burgess
Modified:	2013-10-24 20:40 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Gordon R. Burgess 2013-10-24 16:48:15 UTC

Steps to reproduce:

(1) open a new spreadsheet (or use one you've been working on for a while, if you like pain)

(2) use the mouse to reduce the height of a row to a minimum value

(3) type Ctrl-Z to undo

On my system this reproducibly causes Gnumeric to exit without a warning or a save.

HW: Lenovo notebook (W510) with 16GB ram; two 1080p monitors.
OS: RHEL6.4
Gnumeric: 1.10.14

BTW this is quickly becoming my favorite spreadsheet tool!

Comment 1 Morten Welinder 2013-10-24 17:06:30 UTC

I am unable to reproduce this with current versions.  Can you provide
a stack trace?

Comment 2 Gordon R. Burgess 2013-10-24 17:22:09 UTC

sorry for my cluelessness - can I start it in debug mode?  What do I need to do to generate a stack trace?

Comment 3 Morten Welinder 2013-10-24 18:18:33 UTC

Something like this:

gdb /path/to/gnumeric
run
# do the thing that causes a crash
where


The "where" command ought to produce a stack trace.

The info at "http://fedoraproject.org/wiki/StackTraces" might be relevant
even though you run RHEL.

Comment 4 Gordon R. Burgess 2013-10-24 19:11:59 UTC

Here it is - I installed the debugging symbols as suggested but still got the "Missing separate debuginfos" message...

(gdb) where

+ Trace 232666

#0 raise
from /lib64/libc.so.6
#1 abort
from /lib64/libc.so.6
#2 __libc_message
from /lib64/libc.so.6
#3 malloc_printerr
from /lib64/libc.so.6
#4 _int_free
from /lib64/libc.so.6
#5 colrow_set_states
from /usr/lib64/libspreadsheet-1.10.14.so
#6 colrow_restore_state_group
from /usr/lib64/libspreadsheet-1.10.14.so
#7 ??
from /usr/lib64/libspreadsheet-1.10.14.so
#8 command_undo
from /usr/lib64/libspreadsheet-1.10.14.so
#9 ??
from /usr/lib64/libspreadsheet-1.10.14.so
#10 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#11 ??
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /lib64/libgobject-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#17 ??
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit
from /lib64/libgobject-2.0.so.0
#20 gtk_accel_group_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_accel_groups_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#22 gtk_window_activate_key
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#25 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#26 ??
from /lib64/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#28 g_signal_emit
from /lib64/libgobject-2.0.so.0
#29 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#34 ??
from /lib64/libglib-2.0.so.0
#35 g_main_loop_run
from /lib64/libglib-2.0.so.0
#36 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#37 main

Comment 5 Morten Welinder 2013-10-24 19:54:39 UTC

Good enough.  This is a duplicate of an already-fixed bug, which is why I
don't see it.

A work-around until you can upgrade might be to run gnumeric like this:

    G_SLICE=always-malloc gnumeric

*** This bug has been marked as a duplicate of bug 649139 ***

Comment 6 Gordon R. Burgess 2013-10-24 20:40:22 UTC

Thanks - I will search the bug list next time before reporting - I'm using this tool (Gnumeric) a lot now - it's really not just a substitute - in general I like it better than running the name brand in a VM.  (assume you know that as you work on it)