GNOME Bugzilla – Bug 497901
crash in e_passwords_ask_password (passwd = 0x0) at e-passwords.c:1122 ("Enter password for (null)")
Last modified: 2009-10-27 05:35:05 UTC
What were you doing when the application crashed? *) Neues Konto hinzufügen *) Microsoft Exchange *) Alle Felder inkl. OWA-URL ausgefüllt (https://unserExchangeServer/exchange/) *) Button "Legitimation" gedrückt 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: Clearlooks Icon Theme: gnome Memory status: size: 182886400 vsize: 182886400 resident: 40366080 share: 20381696 rss: 40366080 rss_rlim: 4294967295 CPU usage: start_time: 1195392205 rtime: 326 utime: 300 stime: 26 cutime:1 cstime: 2 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 0xb68346b0 (LWP 8959)] [New Thread 0xaf6d4b90 (LWP 9018)] [New Thread 0xb13f7b90 (LWP 8992)] [New Thread 0xb0bf6b90 (LWP 8991)] [New Thread 0xb23f9b90 (LWP 8988)] [New Thread 0xb2bfab90 (LWP 8987)] [New Thread 0xb33fbb90 (LWP 8986)] [New Thread 0xb53ffb90 (LWP 8985)] [New Thread 0xb3bfcb90 (LWP 8981)] [New Thread 0xb43fdb90 (LWP 8980)] [New Thread 0xb4bfeb90 (LWP 8978)] [New Thread 0xb5dd1b90 (LWP 8976)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 178514
----------- .xsession-errors --------------------- (evolution-2.10:8959): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:8959): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:8959): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3 (evolution-2.10:8959): 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:8959): Gtk-CRITICAL **: gtk_message_dialog_new: assertion `parent == NULL || GTK_IS_WINDOW (parent)' failed (evolution-2.10:8959): Gtk-CRITICAL **: gtk_window_set_title: assertion `GTK_IS_WINDOW (window)' failed (evolution-2.10:8959): Gtk-CRITICAL **: gtk_widget_ensure_style: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the 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 help fixing this by installing some debugging packages [1], start the application as normal, and try to 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] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Hello, I've installed all mentioned debugging packages except libgnome, where I couldn't find a -dbg package. Here is the new stacktrace with more information! Thanks for throwing an eye on this! 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: Clearlooks Icon Theme: gnome Memory status: size: 191221760 vsize: 191221760 resident: 40374272 share: 20365312 rss: 40374272 rss_rlim: 4294967295 CPU usage: start_time: 1195407547 rtime: 353 utime: 326 stime: 27 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb68746b0 (LWP 19916)] [New Thread 0xaf2ffb90 (LWP 19972)] [New Thread 0xb0c6cb90 (LWP 19949)] [New Thread 0xb146db90 (LWP 19947)] [New Thread 0xb1c6eb90 (LWP 19946)] [New Thread 0xb246fb90 (LWP 19945)] [New Thread 0xb2cd0b90 (LWP 19944)] [New Thread 0xb34d1b90 (LWP 19943)] [New Thread 0xb3cd2b90 (LWP 19942)] [New Thread 0xb44f2b90 (LWP 19938)] [New Thread 0xb54ffb90 (LWP 19937)] [New Thread 0xb4cfeb90 (LWP 19935)] [New Thread 0xb5e11b90 (LWP 19933)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 178551
Thread 1 (Thread 0xb68746b0 (LWP 19916))
----------- .xsession-errors --------------------- (evolution-2.10:19916): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:19916): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:19916): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3 (evolution-2.10:19916): 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:19916): Gtk-CRITICAL **: gtk_message_dialog_new: assertion `parent == NULL || GTK_IS_WINDOW (parent)' failed (evolution-2.10:19916): Gtk-CRITICAL **: gtk_window_set_title: assertion `GTK_IS_WINDOW (window)' failed (evolution-2.10:19916): Gtk-CRITICAL **: gtk_widget_ensure_style: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
*** Bug 499879 has been marked as a duplicate of this bug. ***
*** Bug 509314 has been marked as a duplicate of this bug. ***
*** Bug 506991 has been marked as a duplicate of this bug. ***
Please look at http://bugzilla.gnome.org/show_bug.cgi?id=424450 Could be similar issue.
*** Bug 508047 has been marked as a duplicate of this bug. ***
*** Bug 505787 has been marked as a duplicate of this bug. ***
Did you get similar crash any time later ? Can you please try in 2.24.x / 2.26.x and report back, thanks.
I'm currently running 2.26.0 No problems with this version.