Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1782541 - [abrt] evolution-data-server: g_strsplit(): evolution-alarm-notify killed by SIGSEGV
Summary: [abrt] evolution-data-server: g_strsplit(): evolution-alarm-notify killed by ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 31
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:0381eef8657f37d216a30a0a2bd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-11 19:56 UTC by Ugis
Modified: 2020-11-24 17:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 17:57:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (77.35 KB, text/plain)
2019-12-11 19:56 UTC, Ugis 		no flags Details
File: core_backtrace (37.01 KB, text/plain)
2019-12-11 19:56 UTC, Ugis 		no flags Details
File: cpuinfo (2.32 KB, text/plain)
2019-12-11 19:56 UTC, Ugis 		no flags Details
File: dso_list (20.00 KB, text/plain)
2019-12-11 19:56 UTC, Ugis 		no flags Details
File: environ (1.89 KB, text/plain)
2019-12-11 19:56 UTC, Ugis 		no flags Details
File: exploitable (82 bytes, text/plain)
2019-12-11 19:57 UTC, Ugis 		no flags Details
File: limits (1.29 KB, text/plain)
2019-12-11 19:57 UTC, Ugis 		no flags Details
File: maps (120.09 KB, text/plain)
2019-12-11 19:57 UTC, Ugis 		no flags Details
File: mountinfo (2.36 KB, text/plain)
2019-12-11 19:57 UTC, Ugis 		no flags Details
File: open_fds (2.13 KB, text/plain)
2019-12-11 19:57 UTC, Ugis 		no flags Details
File: proc_pid_status (1.33 KB, text/plain)
2019-12-11 19:57 UTC, Ugis 		no flags Details
View All

Description Ugis 2019-12-11 19:56:47 UTC 
Description of problem:
fails each time I login after turning on laptop

Version-Release number of selected component:
evolution-data-server-3.34.2-1.fc31

Additional info:
reporter:       libreport-2.11.3
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/gnome\x2dsession\x2dmanager.slice/gnome-session-manager
cmdline:        /usr/libexec/evolution-data-server/evolution-alarm-notify
crash_function: g_strsplit
executable:     /usr/libexec/evolution-data-server/evolution-alarm-notify
journald_cursor: s=f91cd1ef96344a56a125fb0661ec66f5;i=14cc0;b=2b2ddbab3ea7476091d3812a3783aa79;m=13fbc6a9;t=59972590285bb;x=ffbbdd57de1db2f5
kernel:         5.3.13-300.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_strsplit at ../glib/gstrfuncs.c:2387
 #1 e_client_util_parse_comma_strings at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/libedataserver/e-client.c:2306
 #3 e_client_set_capabilities at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/libedataserver/e-client.c:1133
 #4 client_ensure_capabilities at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/libedataserver/e-client.c:1015
 #5 e_client_check_capability at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/libedataserver/e-client.c:1087
 #6 e_reminder_watcher_get_alarm_summary at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/calendar/libecal/e-reminder-watcher.c:2582
 #7 e_reminder_watcher_describe_data at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/calendar/libecal/e-reminder-watcher.c:2662
 #8 e_alarm_notify_display at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/services/evolution-alarm-notify/e-alarm-notify.c:223
 #9 e_alarm_notify_procedure at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/services/evolution-alarm-notify/e-alarm-notify.c:466
 #10 e_alarm_notify_process at /usr/src/debug/evolution-data-server-3.34.2-1.fc31.x86_64/src/services/evolution-alarm-notify/e-alarm-notify.c:553
Comment 1 Ugis 2019-12-11 19:56:51 UTC 
Created attachment 1644110 [details]
File: backtrace
Comment 2 Ugis 2019-12-11 19:56:53 UTC 
Created attachment 1644111 [details]
File: core_backtrace
Comment 3 Ugis 2019-12-11 19:56:55 UTC 
Created attachment 1644112 [details]
File: cpuinfo
Comment 4 Ugis 2019-12-11 19:56:57 UTC 
Created attachment 1644113 [details]
File: dso_list
Comment 5 Ugis 2019-12-11 19:56:58 UTC 
Created attachment 1644114 [details]
File: environ
Comment 6 Ugis 2019-12-11 19:57:00 UTC 
Created attachment 1644115 [details]
File: exploitable
Comment 7 Ugis 2019-12-11 19:57:01 UTC 
Created attachment 1644116 [details]
File: limits
Comment 8 Ugis 2019-12-11 19:57:04 UTC 
Created attachment 1644117 [details]
File: maps
Comment 9 Ugis 2019-12-11 19:57:05 UTC 
Created attachment 1644118 [details]
File: mountinfo
Comment 10 Ugis 2019-12-11 19:57:06 UTC 
Created attachment 1644119 [details]
File: open_fds
Comment 11 Ugis 2019-12-11 19:57:08 UTC 
Created attachment 1644120 [details]
File: proc_pid_status
Comment 12 Milan Crha 2020-01-06 13:56:41 UTC 
Thanks for a bug report. That's a very odd place for a crash, it's one of the core functions of the glib2-2.62.3-1.fc31.x86_64 you've installed. The debugger shows all passed-in data as valid pointers, which makes me wonder how this could happen. Maybe it's another variant of bug #1761499, only exhibiting on a different place.

You said it crashes every time for you, that would be a perfect reproducer. Could you open a terminal and run from it, as a regular user:

   $ /usr/libexec/evolution-data-server/evolution-alarm-notify

please? Will it crash too? If it will, could you install valgrind and debuginfo packages for evolution-data-server, glib2 and gtk3:

   $ sudo dnf install valgrind evolution-data-server-debuginfo glib2-debuginfo gtk3-debuginfo --enablerepo=updates-debuginfo

Then verify the debuginfo package versions match those of the binary packages (otherwise the debugging information would not be usable):

   $ rpm -qa evolution-data-server\* glib2\* gtk3\* | sort

If they won't match, then try to use 'update' instead of 'install' command in the 'dnf' call above. After this, run the evolution-alarm-notify from a terminal like this (the second command is one long command, split into two lines; you can just copy&paste it):

   $ export GIGACAGE_ENABLED=0
   $ G_SLICE=always-malloc valgrind --num-callers=30 --aspace-minaddr=0x100000000 \
        /usr/libexec/evolution-data-server/evolution-alarm-notify &>~/log.txt

It will create a log.txt file in your home, which will contain output from the valgrind. It's possible the evolution-alarm-notify will not crash this time, because valgrind can avoid certain memory issues and log about them only. It will be significantly slower and the CPU usage will be higher due to all the memory checks valgrind does. Please check the log.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only), even I do not expect it to contain any such thing. Upload the log.txt file here, please, and I'll check whether it'll contain anything usable.
Comment 13 Milan Crha 2020-01-06 13:58:09 UTC 
*** Bug 1782845 has been marked as a duplicate of this bug. ***
Comment 14 Milan Crha 2020-01-07 11:37:23 UTC 
I do not know whether it's really it, but I guess it's like it's it. Could you give a try to the update mentioned in bug #1754321 comment #26, please?
Comment 15 Ben Cotton 2020-11-03 15:59:03 UTC 
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 16 Ben Cotton 2020-11-24 17:57:51 UTC 
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.