GNOME Bugzilla – Bug 444852
crash in ?? / g_hash_table_insert / ?? / gdk_pixmap_new / gdk_window_begin_paint_region
Last modified: 2007-12-16 21:50:33 UTC
What were you doing when the application crashed? Deleting memos. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 140062720 vsize: 140062720 resident: 39247872 share: 22265856 rss: 39247872 rss_rlim: 4294967295 CPU usage: start_time: 1181154739 rtime: 1953 utime: 1806 stime: 147 cutime:59 cstime: 19 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208326432 (LWP 17647)] [New Thread -1293603952 (LWP 17877)] [New Thread -1277838448 (LWP 17672)] [New Thread -1255834736 (LWP 17669)] (no debugging symbols found) 0x00cda402 in __kernel_vsyscall ()
+ Trace 138851
Thread 1 (Thread -1208326432 (LWP 17647))
----------- .xsession-errors (132 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (evolution:17647): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:17647): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:17647): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) (evolution:17647): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8916260' (evolution:17647): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8916380' (evolution:17647): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) (evolution:17647): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x89164a0' (evolution:17647): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x89165c0' --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 447786 has been marked as a duplicate of this bug. ***
*** Bug 446502 has been marked as a duplicate of this bug. ***
*** Bug 448606 has been marked as a duplicate of this bug. ***
*** Bug 453504 has been marked as a duplicate of this bug. ***
*** Bug 451356 has been marked as a duplicate of this bug. ***
*** Bug 461132 has been marked as a duplicate of this bug. ***
*** Bug 457608 has been marked as a duplicate of this bug. ***
*** Bug 473855 has been marked as a duplicate of this bug. ***
*** Bug 474245 has been marked as a duplicate of this bug. ***
*** Bug 477064 has been marked as a duplicate of this bug. ***
*** Bug 482087 has been marked as a duplicate of this bug. ***
(evolution:17647): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8916260' This is bug #447591, which is fixed now. *** This bug has been marked as a duplicate of 447591 ***
*** Bug 503397 has been marked as a duplicate of this bug. ***