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 476467 - Crash when pressing OK in the page setup dialog
Crash when pressing OK in the page setup dialog
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Printing
git master
Other All
: Normal critical
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
: 514886 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-13 07:22 UTC by sum1
Modified: 2008-02-07 00:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sum1 2007-09-13 07:22:05 UTC
Version: r15884
OS: Ubuntu Gutsy

I'm using an alpha version of Ubuntu, so this may not be a Gnumeric bug.

Steps to reproduce:
- Run Gnumeric
- File > Page Setup
- Press OK

Backtrace;
Program received signal SIGSEGV, Segmentation fault.

Thread NaN (LWP 27244)

  • #0 glade_xml_get_widget
    from /usr/lib/libglade-2.0.so.0
  • #1 do_fetch_scale
    at dialog-printer-setup.c line 1898
  • #2 fetch_settings
    at dialog-printer-setup.c line 1998
  • #3 cb_do_print_ok
    at dialog-printer-setup.c line 1698
  • #4 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 ??
  • #8 ??

Partial Valgrind output:
==6415== Invalid read of size 4
==6415==    at 0x41CB23C: do_fetch_page (dialog-printer-setup.c:1869)
==6415==    by 0x41CB84E: fetch_settings (dialog-printer-setup.c:1997)
==6415==    by 0x41CA94D: cb_do_print_ok (dialog-printer-setup.c:1698)
==6415==    by 0x4CB0C08: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CA3771: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CB42FC: (within /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CB5806: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CB59C8: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x47FEEF6: gtk_button_clicked (in /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x480105D: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4CB0C08: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CA1F88: (within /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==  Address 0x626E614 is 12 bytes inside a block of size 452 free'd
==6415==    at 0x402237F: free (vg_replace_malloc.c:233)
==6415==    by 0x4D0B8C0: g_free (in /usr/lib/libglib-2.0.so.0.1400.0)
==6415==    by 0x41CAAAE: cb_do_print_destroy (dialog-printer-setup.c:1738)
==6415==    by 0x4CF0487: g_datalist_clear (in /usr/lib/libglib-2.0.so.0.1400.0)
==6415==    by 0x4CA7D3F: (within /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x491ABAE: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4A386BB: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4A4ABA2: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4CA5AEB: g_object_unref (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CA5E37: g_object_run_dispose (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x491A4F1: gtk_object_destroy (in /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4A37F14: gtk_widget_destroy (in /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415== 
==6415== Invalid read of size 4
==6415==    at 0x41CB249: do_fetch_page (dialog-printer-setup.c:1869)
==6415==    by 0x41CB84E: fetch_settings (dialog-printer-setup.c:1997)
==6415==    by 0x41CA94D: cb_do_print_ok (dialog-printer-setup.c:1698)
==6415==    by 0x4CB0C08: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CA3771: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CB42FC: (within /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CB5806: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CB59C8: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x47FEEF6: gtk_button_clicked (in /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x480105D: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4CB0C08: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CA1F88: (within /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==  Address 0x626E7B4 is 428 bytes inside a block of size 452 free'd
==6415==    at 0x402237F: free (vg_replace_malloc.c:233)
==6415==    by 0x4D0B8C0: g_free (in /usr/lib/libglib-2.0.so.0.1400.0)
==6415==    by 0x41CAAAE: cb_do_print_destroy (dialog-printer-setup.c:1738)
==6415==    by 0x4CF0487: g_datalist_clear (in /usr/lib/libglib-2.0.so.0.1400.0)
==6415==    by 0x4CA7D3F: (within /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x491ABAE: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4A386BB: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4A4ABA2: (within /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4CA5AEB: g_object_unref (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x4CA5E37: g_object_run_dispose (in /usr/lib/libgobject-2.0.so.0.1400.0)
==6415==    by 0x491A4F1: gtk_object_destroy (in /usr/lib/libgtk-x11-2.0.so.0.1106.0)
==6415==    by 0x4A37F14: gtk_widget_destroy (in /usr/lib/libgtk-x11-2.0.so.0.1106.0)

(gnumeric:6415): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkToggleButton'

(gnumeric:6415): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
Comment 1 Morten Welinder 2007-09-13 14:21:55 UTC
Confirmed with very recent build.
Comment 2 Morten Welinder 2007-09-14 01:29:08 UTC
The problem is in dialog-printer-setup.c, function cb_do_print_ok.
The wbc_gtk_detach_guru that was commented out really is needed.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 3 Andreas J. Guelzow 2008-02-07 00:04:49 UTC
*** Bug 514886 has been marked as a duplicate of this bug. ***