Bug 709441 – [abrt] Crash under handle_mail_request, g_settings_binding_free

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 709441 - [abrt] Crash under handle_mail_request, g_settings_binding_free


Summary:	[abrt] Crash under handle_mail_request, g_settings_binding_free


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	3.10.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-10-04 17:44 UTC by Milan Crha
Modified:	2015-03-10 17:28 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Milan Crha 2013-10-04 17:44:22 UTC

Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1015443

Description of problem:
Had just resumed from suspend, Evo was refreshing all mail, crashed in the middle.

Version-Release number of selected component:
evolution-3.10.0-1.fc20

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/evolution
crash_function: _g_log_abort
executable:     /usr/bin/evolution
kernel:         3.12.0-0.rc3.git2.2.fc21.x86_64

The log message says:
   g_settings_binding_free: assertion failed: (!binding->running)

Core was generated by `/usr/bin/evolution'.
Program terminated with signal SIGABRT, Aborted.

+ Trace 232573

Thread 9 (Thread 0x7f6bef3a2a40 (LWP 2005))

#0 _IO_vfprintf_internal
#1 __GI___vasprintf_chk
#2 vasprintf
at /usr/include/bits/stdio2.h line 210
#3 g_vasprintf
at gprintf.c line 314
#4 g_string_append_vprintf
at gstring.c line 1164
#5 g_string_append_printf
#6 g_log_default_handler
#7 g_logv
at gmessages.c line 960
#8 g_log
at gmessages.c line 1025
#9 g_return_if_fail_warning
#10 g_object_notify_queue_thaw
at gobject.c line 263
#11 g_object_set_property
at gobject.c line 2330
#12 g_settings_binding_key_changed
at gsettings.c line 2418
#13 g_cclosure_marshal_VOID__STRINGv
at gmarshal.c line 1004
#14 _g_closure_invoke_va
at gclosure.c line 840
#15 g_signal_emit_valist
at gsignal.c line 3238
#16 g_signal_emit
at gsignal.c line 3386
#17 g_settings_real_change_event
at gsettings.c line 288
#18 ffi_call_unix64
at ../src/x86/unix64.S line 76
#19 ffi_call
at ../src/x86/ffi64.c line 522
#20 g_cclosure_marshal_generic_va
at gclosure.c line 1550
#21 _g_closure_invoke_va
at gclosure.c line 840
#22 g_signal_emit_valist
at gsignal.c line 3238
#23 g_signal_emit
at gsignal.c line 3386
#24 settings_backend_path_changed
at gsettings.c line 363
#25 g_settings_backend_invoke_closure
at gsettingsbackend.c line 271
#26 g_main_dispatch
at gmain.c line 3065
#27 g_main_context_dispatch
at gmain.c line 3641
#28 g_main_context_iterate
at gmain.c line 3712
#29 g_main_loop_run
at gmain.c line 3906
#30 gtk_main
at gtkmain.c line 1158
#31 main
at main.c line 683

Comment 1 Igor Gnatenko 2013-12-07 07:37:01 UTC

Got this bug on evolution-3.10.2-2.fc20.x86_64

Comment 2 Milan Crha 2015-03-10 17:28:38 UTC

No duplicate for a long time, I'm closing this. This also can be related to bug #745013