Bug 696621 – [abrt] Crash under check_midnight_refresh()

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 696621 - [abrt] Crash under check_midnight_refresh()


Summary:	[abrt] Crash under check_midnight_refresh()


Status:	RESOLVED OBSOLETE

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-03-26 09:57 UTC by Milan Crha
Modified:	2017-10-16 16:39 UTC

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

Description Milan Crha 2013-03-26 09:57:50 UTC

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

Version-Release number of selected component:
evolution-3.6.4-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/3.6/evolution-alarm-notify
crash_function: __memcmp_sse4_1
executable:     /usr/libexec/evolution/3.6/evolution-alarm-notify
kernel:         3.8.2-206.fc18.x86_64

+ Trace 231683

Thread 1 (Thread 0x7fc5638bca00 (LWP 1846))

#0 __memcmp_sse4_1
at ../sysdeps/x86_64/multiarch/memcmp-sse4.S line 975
#1 gvdb_table_check_name
at gvdb-reader.c line 294
#2 gvdb_table_lookup
at gvdb-reader.c line 341
#3 gvdb_table_get_value
at gvdb-reader.c line 653
#4 dconf_engine_read
at dconf-engine.c line 525
#5 g_settings_backend_read
at gsettingsbackend.c line 733
#6 g_settings_read_from_backend
at gsettings.c line 1040
#7 g_settings_get_value
at gsettings.c line 1080
#8 g_settings_get_boolean
at gsettings.c line 1785
#9 config_data_get_timezone
at config-data.c line 81
#10 check_midnight_refresh
at alarm-queue.c line 2013
#11 g_timeout_dispatch
at gmain.c line 4026
#12 g_main_dispatch
at gmain.c line 2715
#13 g_main_context_dispatch
at gmain.c line 3219
#14 g_main_context_iterate
at gmain.c line 3290
#15 g_main_context_iteration
at gmain.c line 3351
#16 g_application_run
at gapplication.c line 1624
#17 main
at notify-main.c line 116

Comment 1 Milan Crha 2014-04-10 15:24:27 UTC

Similar downstream bug report from evolution 3.10.4:
https://bugzilla.redhat.com/show_bug.cgi?id=1086176

Version-Release number of selected component:
evolution-3.10.4-2.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/3.10/evolution-alarm-notify
crash_function: calloc
executable:     /usr/libexec/evolution/3.10/evolution-alarm-notify
kernel:         3.13.7-200.fc20.x86_64

> (evolution-alarm-notify:1565): evolution-alarm-notify-WARNING **: alarm.c:255: Requested removal of nonexistent alarm!
> *** Error in `/usr/libexec/evolution/3.10/evolution-alarm-notify': corrupted double-linked list: 0x0000000001e17df0 ***
> /usr/libexec/evolution/3.10/evolution-alarm-notify(config_data_get_timezone+0x27)[0x40da97]

+ Trace 233456

Thread 1 (Thread 0x7ff112cdfa40 (LWP 1565))

#0 raise
from /lib64/libc.so.6
#1 abort
from /lib64/libc.so.6
#2 __libc_message
from /lib64/libc.so.6
#3 malloc_consolidate
from /lib64/libc.so.6
#4 _int_malloc
from /lib64/libc.so.6
#5 calloc
from /lib64/libc.so.6
#6 g_malloc0
from /lib64/libglib-2.0.so.0
#7 g_hash_table_resize
from /lib64/libglib-2.0.so.0
#8 g_hash_table_insert_node
from /lib64/libglib-2.0.so.0
#9 g_hash_table_insert_internal
from /lib64/libglib-2.0.so.0
#10 system_timezone_find
from /lib64/libecal-1.2.so.16
#11 config_data_get_timezone
#12 check_midnight_refresh
#13 g_timeout_dispatch
from /lib64/libglib-2.0.so.0
#14 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#15 g_main_context_iterate.isra.24
from /lib64/libglib-2.0.so.0
#16 g_main_context_iteration
from /lib64/libglib-2.0.so.0
#17 g_application_run
from /lib64/libgio-2.0.so.0
#18 main

Comment 2 Milan Crha 2017-10-16 16:39:11 UTC

I'm closing this as obsolete. It had been a long time since it happened the last time.