Bug 866697

Summary: [abrt] evolution-3.6.1-1.fc18: camel_nntp_raw_commandv: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Michael S. <misc>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ff4d0f77b45ddffd31f25a70a275fe49c4a5e3ea
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-18 09:39:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: smolt_data
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: build_ids
none
File: open_fds
none
File: var_log_messages none

Description Michael S. 2012-10-15 22:16:34 UTC 
Description of problem:
Evolution refreshed itself, and I think this would be related to my gmane nntp account ( anonymous one ) since the backtrace speak of nntp.

Version-Release number of selected component:
evolution-3.6.1-1.fc18

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.15
backtrace_rating: 4
cmdline:        evolution
crash_function: camel_nntp_raw_commandv
kernel:         3.6.1-1.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 camel_nntp_raw_commandv at /usr/lib64/evolution-data-server/camel-providers/libcamelnntp.so
: #1 camel_nntp_raw_command_auth at /usr/lib64/evolution-data-server/camel-providers/libcamelnntp.so
: #2 camel_nntp_command at /usr/lib64/evolution-data-server/camel-providers/libcamelnntp.so
: #3 nntp_folder_refresh_info_online at /usr/lib64/evolution-data-server/camel-providers/libcamelnntp.so
: #4 disco_refresh_info_sync at /lib64/libcamel-1.2.so.40
: #5 camel_folder_refresh_info_sync at /lib64/libcamel-1.2.so.40
: #6 camel_nntp_folder_new at /usr/lib64/evolution-data-server/camel-providers/libcamelnntp.so
: #7 disco_store_get_folder_sync at /lib64/libcamel-1.2.so.40
: #8 camel_store_get_folder_sync at /lib64/libcamel-1.2.so.40
: #9 e_mail_session_uri_to_folder_sync at /usr/lib64/evolution/3.6/libemail-engine.so
Comment 1 Michael S. 2012-10-15 22:16:36 UTC 
Created attachment 627746 [details]
File: core_backtrace
Comment 2 Michael S. 2012-10-15 22:16:38 UTC 
Created attachment 627747 [details]
File: environ
Comment 3 Michael S. 2012-10-15 22:16:40 UTC 
Created attachment 627748 [details]
File: limits
Comment 4 Michael S. 2012-10-15 22:16:42 UTC 
Created attachment 627749 [details]
File: backtrace
Comment 5 Michael S. 2012-10-15 22:16:44 UTC 
Created attachment 627750 [details]
File: smolt_data
Comment 6 Michael S. 2012-10-15 22:16:45 UTC 
Created attachment 627751 [details]
File: cgroup
Comment 7 Michael S. 2012-10-15 22:16:48 UTC 
Created attachment 627752 [details]
File: maps
Comment 8 Michael S. 2012-10-15 22:16:51 UTC 
Created attachment 627753 [details]
File: dso_list
Comment 9 Michael S. 2012-10-15 22:16:53 UTC 
Created attachment 627754 [details]
File: proc_pid_status
Comment 10 Michael S. 2012-10-15 22:16:55 UTC 
Created attachment 627755 [details]
File: build_ids
Comment 11 Michael S. 2012-10-15 22:16:56 UTC 
Created attachment 627756 [details]
File: open_fds
Comment 12 Michael S. 2012-10-15 22:16:59 UTC 
Created attachment 627757 [details]
File: var_log_messages
Comment 13 Milan Crha 2012-10-17 07:19:12 UTC 
Thanks for a bug report. You are right with the NNTP account and refresh, that's basically what I see in the backtrace too - evolution was refreshing one of your NNTP folders, when it crashed. There are missing debuginfo packages for evolution-data-server and evolution, unfortunately, thus the backtrace is missing detailed information from the crash. Could you install debuginfo packages (of the same version as your binary packages are), please?

Was this just a one-time crash, or you got it multiple times? If the later, then it'll be nice to get the backtrace with detailed information.
Comment 14 Michael S. 2012-10-17 08:17:28 UTC 
Nope, this occurs each time. i disabled nntp to fix for now, and i will generate a new backtrace later.
Comment 15 Milan Crha 2012-10-18 09:39:48 UTC 
Thanks for the update. I'm trying to reproduce this, while I found other issues with NNTP. I'm testing further, but meanwhile, I found upstream bug [1] about the same, thus I'm moving this there. Feel free to CC there yourself, as any further updates will be done there.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=685482