Bug 1387272 - [abrt] evolution: raise(): evolution-alarm-notify killed by SIGTRAP
Summary: [abrt] evolution: raise(): evolution-alarm-notify killed by SIGTRAP
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 25
Hardware: armv7l
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b5e358aad37ce791115842c8359...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 14:01 UTC by Sam Tygier
Modified: 2016-10-25 12:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-25 06:25:40 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (31.26 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: cgroup (229 bytes, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: core_backtrace (7.13 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: dso_list (18.94 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: environ (1.02 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: limits (1.29 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: maps (65.97 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: mountinfo (3.34 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: namespaces (102 bytes, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: open_fds (1.03 KB, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: proc_pid_status (972 bytes, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
File: var_log_messages (28 bytes, text/plain)
2016-10-20 14:01 UTC, Sam Tygier 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Sam Tygier 2016-10-20 14:01:09 UTC 
Version-Release number of selected component:
evolution-3.22.0-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/evolution-alarm-notify
crash_function: raise
executable:     /usr/libexec/evolution/evolution-alarm-notify
global_pid:     1536
kernel:         4.8.0-0.rc7.git0.1.fc25.armv7hl
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 raise at ../sysdeps/unix/sysv/linux/raise.c:58
 #1 g_node_insert_before at gnode.c:306
Comment 1 Sam Tygier 2016-10-20 14:01:15 UTC 
Created attachment 1212525 [details]
File: backtrace
Comment 2 Sam Tygier 2016-10-20 14:01:17 UTC 
Created attachment 1212526 [details]
File: cgroup
Comment 3 Sam Tygier 2016-10-20 14:01:19 UTC 
Created attachment 1212527 [details]
File: core_backtrace
Comment 4 Sam Tygier 2016-10-20 14:01:20 UTC 
Created attachment 1212528 [details]
File: dso_list
Comment 5 Sam Tygier 2016-10-20 14:01:22 UTC 
Created attachment 1212529 [details]
File: environ
Comment 6 Sam Tygier 2016-10-20 14:01:24 UTC 
Created attachment 1212530 [details]
File: limits
Comment 7 Sam Tygier 2016-10-20 14:01:26 UTC 
Created attachment 1212531 [details]
File: maps
Comment 8 Sam Tygier 2016-10-20 14:01:27 UTC 
Created attachment 1212532 [details]
File: mountinfo
Comment 9 Sam Tygier 2016-10-20 14:01:29 UTC 
Created attachment 1212533 [details]
File: namespaces
Comment 10 Sam Tygier 2016-10-20 14:01:30 UTC 
Created attachment 1212534 [details]
File: open_fds
Comment 11 Sam Tygier 2016-10-20 14:01:32 UTC 
Created attachment 1212535 [details]
File: proc_pid_status
Comment 12 Sam Tygier 2016-10-20 14:01:33 UTC 
Created attachment 1212536 [details]
File: var_log_messages
Comment 13 Milan Crha 2016-10-25 06:25:40 UTC 
Thanks for a bug report. The backtrace is somewhat corrupt. Could it be that this crash happened soon after an update of the evolution package? It seems to me that the running binary was from a previous version, while the package has been updated. Please reopen, if you manage to reproduce this crash, ideally with added steps and/or comments for the reproducer to explain what was happening at the time of the crash. Thanks in advance.
Comment 14 Sam Tygier 2016-10-25 12:08:11 UTC 
That's quite possible. I'll see if I can reproduce it.
Note You need to log in before you can comment on or make changes to this bug.