GNOME Bugzilla – Bug 578692
Crash in camel_pop3_engine_command_new at camel-pop3-engine.c line 256
Last modified: 2015-04-29 12:47:53 UTC
What were you doing when the application crashed? Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Fri Mar 13 18:08:45 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 102203392 vsize: 102203392 resident: 31272960 share: 18751488 rss: 31272960 rss_rlim: 4294967295 CPU usage: start_time: 1239448623 rtime: 132 utime: 119 stime: 13 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb65cd6d0 (LWP 11736)] [New Thread 0xb2d80b90 (LWP 11820)] [New Thread 0xb529ab90 (LWP 11786)] [New Thread 0xb5caeb90 (LWP 11784)] 0xb7f3f424 in __kernel_vsyscall ()
+ Trace 214375
Thread 2 (Thread 0xb2d80b90 (LWP 11820))
----------- .xsession-errors --------------------- (evolution:11736): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed (evolution:11736): camel-CRITICAL **: camel_store_get_folder: assertion `CAMEL_IS_STORE (store)' failed (evolution:11736): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed (evolution:11736): evolution-mail-CRITICAL **: mail_tools_folder_to_url: assertion `CAMEL_IS_FOLDER (folder)' failed e-data-server-ui-Message: Received a password from keyring 'login'. But looking for the password from 'default' keyring e-data-server-ui-Message: Received a password from keyring 'login'. But looking for the password from 'default' keyring (evolution:11736): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:11736): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I'm not sure here. The second signal handler call looks like bug 578692, bug 582086, bug 458647, bug 458570.
Similar downstream bug report from 3.0.3: https://bugzilla.redhat.com/show_bug.cgi?id=737536
This is a crash that was reported against version 3.0. I'm sorry that this report did not receive investigation/attention when you filed it, but manpower is and was limited. Is this still a problem in a recent version (3.12)? If not, this report should probably be closed as OBSOLETE nowadays as codebases change... :-/
Hi pjuetten, I am closing this bug report as no updated information has been provided. Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.
*** Bug 668272 has been marked as a duplicate of this bug. ***