Bug 1065559

Summary: [abrt] evolution-data-server-3.10.2-2.fc20: g_signal_emit_by_name: Process /usr/libexec/evolution-source-registry was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dan <pyroman13>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, mbarnes, mcrha, pyroman13, stevenvdschoot
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/edcc0d037e3ff0a33963a97c5b683aac4f68fcfb
Whiteboard: abrt_hash:f09560b645538993e969fb176b31cf58d31ebfa2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-23 18:12:52 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: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Dan 2014-02-14 23:17:24 UTC
Description of problem:
I attempt to use Add Link and Evolution simply crashes. I had it work for me one time with a basic link. It seems to always occur if there is an image. I want the image to be a link.

Version-Release number of selected component:
evolution-data-server-3.10.2-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 3
cmdline:        /usr/libexec/evolution-source-registry
crash_function: g_signal_emit_by_name
executable:     /usr/libexec/evolution-source-registry
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_signal_emit_by_name at gsignal.c:3426
 #3 on_notify_g_name_owner at gdbusobjectmanagerclient.c:1270
 #9 g_object_notify_by_spec_internal at gobject.c:1141
 #10 g_object_notify at gobject.c:1183
 #11 on_name_owner_changed at gdbusproxy.c:1361
 #12 emit_signal_instance_in_idle_cb at gdbusconnection.c:3743
 #17 dbus_server_run_server at e-dbus-server.c:222
 #18 ffi_call_unix64 at ../src/x86/unix64.S:76
 #19 ffi_call at ../src/x86/ffi64.c:522
 #20 g_cclosure_marshal_generic_va at gclosure.c:1550

Comment 1 Dan 2014-02-14 23:17:28 UTC
Created attachment 863498 [details]
File: backtrace

Comment 2 Dan 2014-02-14 23:17:30 UTC
Created attachment 863499 [details]
File: cgroup

Comment 3 Dan 2014-02-14 23:17:32 UTC
Created attachment 863500 [details]
File: core_backtrace

Comment 4 Dan 2014-02-14 23:17:34 UTC
Created attachment 863501 [details]
File: dso_list

Comment 5 Dan 2014-02-14 23:17:35 UTC
Created attachment 863502 [details]
File: environ

Comment 6 Dan 2014-02-14 23:17:37 UTC
Created attachment 863503 [details]
File: exploitable

Comment 7 Dan 2014-02-14 23:17:38 UTC
Created attachment 863504 [details]
File: limits

Comment 8 Dan 2014-02-14 23:17:40 UTC
Created attachment 863505 [details]
File: maps

Comment 9 Dan 2014-02-14 23:17:41 UTC
Created attachment 863506 [details]
File: open_fds

Comment 10 Dan 2014-02-14 23:17:43 UTC
Created attachment 863507 [details]
File: proc_pid_status

Comment 11 Dan 2014-02-14 23:17:45 UTC
Created attachment 863508 [details]
File: var_log_messages

Comment 12 Milan Crha 2014-02-17 11:34:09 UTC
Thanks for a bug report. The place of your crash is not in evolution itself, it crashed in an evolution-source-registry process, which is part of evolution-data-server, which doesn't influence much in "Add Link" feature (I suppose it's in a new message composer).

As you indicated you can reproduce the crash on will, could you give me some exact steps for a reproducer, maybe with exact sample data, please? The more details you'll give the better, the best when you start your steps with "open a new message window (composer)" and then continue. Thanks in advance.

Comment 13 Dan 2014-06-23 18:12:52 UTC
I have since wiped this system, so I can not attempt to duplicate.