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 473728 - crash in Gnumeric Spreadsheet: setting page-size as 'de...
crash in Gnumeric Spreadsheet: setting page-size as 'de...
Status: RESOLVED DUPLICATE of bug 449836
Product: Gnumeric
Classification: Applications
Component: General
1.7.x
Other All
: High critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2007-09-04 22:29 UTC by adam-bugbuddy
Modified: 2007-09-05 02:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description adam-bugbuddy 2007-09-04 22:29:02 UTC 
Version: 1.7.10

What were you doing when the application crashed?
setting page-size as 'default'


Distribution: Fedora Core release 3 (Heidelberg)
Gnome Release: 2.18.3 2007-07-13 (GARNOME)
BugBuddy Version: 2.18.1

System: Linux 2.6.16.20 #2 SMP Mon Jun 5 22:37:40 EDT 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 60801000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 320847872 vsize: 320847872 resident: 174075904 share: 17350656 rss: 174075904 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188942250 rtime: 3899 utime: 3700 stime: 199 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/ita/gar64/bin/gnumeric'

Using host libthread_db library "/lib64/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47563454632160 (LWP 13068)]
0x00002b423a351f44 in waitpid () from /lib64/tls/libpthread.so.0

+ Trace 160508

  • #0 waitpid
    from /lib64/tls/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 IA__g_utf8_validate
    at gutf8.c line 1567
  • #4 gconf_value_list_from_primitive_list
    at gconf-internals.c line 1239
  • #5 gconf_engine_set_list
    at gconf.c line 3479
  • #6 gconf_client_set_list
    at gconf-client.c line 1815
  • #7 go_conf_set_str_list
    at gnumeric-gconf.c line 159
  • #8 gnm_gconf_set_printer_header
    at gnumeric-gconf.c line 1957
  • #9 print_info_save
    at print-info.c line 375
  • #10 cb_do_print_ok
    at dialog-printer-setup.c line 1774
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 gtk_real_button_released
    at gtkbutton.c line 1484
  • #16 IA__g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #18 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #19 IA__g_signal_emit
    at gsignal.c line 2243
  • #20 gtk_button_button_release
    at gtkbutton.c line 1377
  • #21 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #22 IA__g_closure_invoke
    at gclosure.c line 490
  • #23 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #24 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #25 IA__g_signal_emit
    at gsignal.c line 2243
  • #26 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #27 IA__gtk_propagate_event
    at gtkmain.c line 2341
  • #28 IA__gtk_main_do_event
    at gtkmain.c line 1575
  • #29 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #30 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #31 g_main_context_iterate
    at gmain.c line 2677
  • #32 IA__g_main_loop_run
    at gmain.c line 2881
  • #33 bonobo_main
    at bonobo-main.c line 311
  • #34 main
    at main-application.c line 531 

Thread 1 (Thread 47563454632160 (LWP 13068)):
#-1 0x00002b423a351f44 in waitpid () from /lib64/tls/libpthread.so.0
No symbol table info available.
Comment 1 Andreas J. Guelzow 2007-09-05 02:21:33 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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