GNOME Bugzilla – Bug 499879
crash in Evolution: Hit the authenticate but...
Last modified: 2008-01-14 12:38:52 UTC
What were you doing when the application crashed? Hit the authenticate button while adding an exchange account Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 124981248 vsize: 124981248 resident: 33357824 share: 20267008 rss: 33357824 rss_rlim: 4294967295 CPU usage: start_time: 1196134256 rtime: 714 utime: 664 stime: 50 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb67df6b0 (LWP 22971)] [New Thread 0xb2f8eb90 (LWP 23029)] [New Thread 0xb37b3b90 (LWP 22999)] [New Thread 0xb40b4b90 (LWP 22998)] [New Thread 0xb50b6b90 (LWP 22994)] [New Thread 0xb58b7b90 (LWP 22993)] [New Thread 0xb616db90 (LWP 22992)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 179776
----------- .xsession-errors (6 sec old) --------------------- (evolution-2.10:22653): Bonobo-WARNING **: Activation exception 'Failed to activate 'OAFIID:GNOME_Spell_Control:0.3'' Setting up initial mail tree addressbook_migrate (0.0.0) evolution-shell-Message: Killing old version of evolution-data-server... (evolution-2.10:22971): 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?) BBDB spinning up... (evolution-2.10:22971): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3 (evolution-2.10:22971): Gtk-CRITICAL **: gtk_message_dialog_new: assertion `parent == NULL || GTK_IS_WINDOW (parent)' failed (evolution-2.10:22971): Gtk-CRITICAL **: gtk_window_set_title: assertion `GTK_IS_WINDOW (window)' failed (evolution-2.10:22971): Gtk-CRITICAL **: gtk_widget_ensure_style: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
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
After I installed the various dbg packages bug-buddy stopped trapping the crash. The program was nice enough to crash under gdb in the same spot so I an including what I thought was interesting from that experience; ---------------------------------------------------------------------- (evolution:4050): Gtk-CRITICAL **: gtk_message_dialog_new: assertion `parent == NULL || GTK_IS_WINDOW (parent)' failed (evolution:4050): Gtk-CRITICAL **: gtk_window_set_title: assertion `GTK_IS_WINDOW (window)' failed (evolution:4050): Gtk-CRITICAL **: gtk_widget_ensure_style: assertion `GTK_IS_WIDGET (widget)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb681ea40 (LWP 4050)] 0xb7c8f86a in ep_ask_password (msg=0x89e31b8) at e-passwords.c:778 778 e-passwords.c: No such file or directory. in e-passwords.c --------------------------------------------------------------------------
+ Trace 179901
Thread 1 (Thread 0xb681ea40 (LWP 4050))
Great job !! Awesome traces.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 497901 ***