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 336165 - "Manage Sheets ..." dialogue box crashes Gnumeric
"Manage Sheets ..." dialogue box crashes Gnumeric
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Sheet Objects
1.6.x
Other All
: Normal major
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2006-03-27 09:18 UTC by Daniel Holbach
Modified: 2006-12-03 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Holbach 2006-03-27 09:18:45 UTC
Forwarded from: https://launchpad.net/distros/ubuntu/+source/gnumeric/+bug/36704

OS Version: Dapper Drake
Kernel Package: linux-image-2.6.15-19-amd64-k8
Program: Gnumeric
Package Version: 1.6.3-0ubuntu1

How to recreate the problem:
1. open Edit > Sheet > Manage Sheets...
2. select "Add"
3. crash

Testing Notes
1. Tested "Insert" and "Append" functions directly. It did not reproduce the problem.
2. Also tested on a similarly configured (Dapper) Thinkpad T40P. It did not reproduce the problem.



Starting program: /usr/bin/gnumeric
[Thread debugging using libthread_db enabled]
[New Thread 46912592856112 (LWP 6167)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912592856112 (LWP 6167)]
IA__gdk_color_copy (color=0x7fff00000000) at gdkcolor.c:131
131     gdkcolor.c: Datei oder Verzeichnis nicht gefunden.
        in gdkcolor.c

Thread 1 (Thread 46912592856112 (LWP 6167))

  • #0 IA__gdk_color_copy
    at gdkcolor.c line 131
  • #1 boxed_proxy_collect_value
    from /usr/lib/libgobject-2.0.so.0
  • #2 gtk_list_store_set_valist_internal
    at gtkliststore.c line 827
  • #3 IA__gtk_list_store_set_valist
    at gtkliststore.c line 877
  • #4 IA__gtk_list_store_set
    at gtkliststore.c line 920
  • #5 cb_add_clicked
    at ../../../src/dialogs/dialog-sheet-order.c line 512
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 gtk_real_button_released
    at gtkbutton.c line 1380
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 gtk_button_button_release
    at gtkbutton.c line 1273
  • #16 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 gtk_widget_event_internal
    at gtkwidget.c line 3732
  • #22 IA__gtk_propagate_event
    at gtkmain.c line 2208
  • #23 IA__gtk_main_do_event
    at gtkmain.c line 1445
  • #24 gdk_event_dispatch
    at gdkevents-x11.c line 2291
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #29 main
    at ../../src/main-application.c line 483

Comment 1 Morten Welinder 2006-03-27 14:51:04 UTC
Confirmed.  We have a 64-bit issue in that code. 

Change...
			    BACKGROUND_COLOUR, 0,
			    FOREGROUND_COLOUR, 0,
...to...
			    BACKGROUND_COLOUR, NULL,
			    FOREGROUND_COLOUR, NULL,

around line 522 in src/dialogs/dialog-sheet-order.c

Fixed in cvs.
Comment 2 Daniel Holbach 2006-03-27 16:05:26 UTC
Morten - you rock! :-)
Comment 3 Uri David Akavia 2006-12-03 11:26:52 UTC
I have encountered this bug today (3-Dec-2006).
If this bug should already be fixed in 1.6.3, I will wait for 1.7.x (or compile my own).
If not, please tell me and I will reopen the bug.
Comment 4 Morten Welinder 2006-12-03 14:08:14 UTC
The original report was for 1.6.3 which is the last in the 1.6.x series so
far.  (And likely to remain so since all efforts are going into 1.7.x by
now.)