Version-Release number of selected component: evolution-data-server-3.5.92-1.fc18 Additional info: libreport version: 2.0.16 abrt_version: 2.0.15 backtrace_rating: 4 cmdline: /usr/libexec/evolution-source-registry crash_function: on_perform_prompt_complete kernel: 3.6.1-1.fc18.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 on_perform_prompt_complete at gcr-system-prompt.c:959 : #1 g_simple_async_result_complete at gsimpleasyncresult.c:775 : #2 g_dbus_connection_call_done at gdbusconnection.c:5339 : #3 g_simple_async_result_complete at gsimpleasyncresult.c:775 : #4 complete_in_idle_cb at gsimpleasyncresult.c:787 : #9 gcr_prompt_password at gcr-prompt.c:830 : #10 authentication_session_execute_sync at e-authentication-session.c:540 : #11 authentication_session_execute_thread at e-authentication-session.c:389 : #12 run_in_thread at gsimpleasyncresult.c:869 : #13 io_job_thread at gioscheduler.c:162
Created attachment 625746 [details] File: core_backtrace
Created attachment 625747 [details] File: environ
Created attachment 625748 [details] File: limits
Created attachment 625749 [details] File: backtrace
Created attachment 625750 [details] File: cgroup
Created attachment 625751 [details] File: smolt_data
Created attachment 625752 [details] File: maps
Created attachment 625753 [details] File: dso_list
Created attachment 625754 [details] File: proc_pid_status
Created attachment 625755 [details] File: open_fds
Created attachment 625757 [details] File: var_log_messages
Thanks for a bug report. This seems to be crashing in gcr code, thus I'm moving this there. By the way, are you able to reproduce this with 3.6.0/3.6.1, please? The 3.6.1 was released only yesterday, it'll take some time till it'll be available for Fedora 18.
(In reply to comment #12) > Thanks for a bug report. This seems to be crashing in gcr code, thus I'm > moving this there. By the way, are you able to reproduce this with > 3.6.0/3.6.1, please? The 3.6.1 was released only yesterday, it'll take some > time till it'll be available for Fedora 18. well IIRC it just happened once randomly. I'll report the bug if this happens again so you'll know.
Thanks for the update. I'm closing this for now, but feel free to reopen or file a new bug report. Thanks in advance.