Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1186744

Summary: [abrt] gnome-shell: icaltimezone_load_builtin_timezone(): gnome-shell-calendar-server killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Koten <jkoten>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: jkoten, mcrha, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2add8f0b579fd1ccfa1be2502da866d89c51a645
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-19 09:49:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: machineid
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jiri Koten 2015-01-28 13:07:17 UTC
Description of problem:
Configured Gmail account through GOA.
In evolution added event to my google's Calendar.

Version-Release number of selected component:
gnome-shell-3.8.4-45.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-shell-calendar-server
crash_function: icaltimezone_load_builtin_timezone
executable:     /usr/libexec/gnome-shell-calendar-server
kernel:         3.10.0-225.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1004

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 icaltimezone_load_builtin_timezone at icaltimezone.c:1766
 #1 icaltimezone_ensure_coverage at icaltimezone.c:462
 #2 icaltimezone_get_utc_offset at icaltimezone.c:818
 #3 icaltimezone_convert_time at icaltimezone.c:773
 #4 icaltime_as_timet_with_zone at icaltime.c:415
 #5 get_time_from_property at calendar-server/gnome-shell-calendar-server.c:124
 #6 get_ical_start_time at calendar-server/gnome-shell-calendar-server.c:177
 #7 calendar_appointment_init at calendar-server/gnome-shell-calendar-server.c:387
 #8 calendar_appointment_new at calendar-server/gnome-shell-calendar-server.c:466
 #9 app_load_events at calendar-server/gnome-shell-calendar-server.c:679

Comment 1 Jiri Koten 2015-01-28 13:07:20 UTC
Created attachment 985128 [details]
File: backtrace

Comment 2 Jiri Koten 2015-01-28 13:07:22 UTC
Created attachment 985129 [details]
File: core_backtrace

Comment 3 Jiri Koten 2015-01-28 13:07:25 UTC
Created attachment 985130 [details]
File: dso_list

Comment 4 Jiri Koten 2015-01-28 13:07:26 UTC
Created attachment 985131 [details]
File: environ

Comment 5 Jiri Koten 2015-01-28 13:07:28 UTC
Created attachment 985132 [details]
File: exploitable

Comment 6 Jiri Koten 2015-01-28 13:07:30 UTC
Created attachment 985133 [details]
File: limits

Comment 7 Jiri Koten 2015-01-28 13:07:32 UTC
Created attachment 985134 [details]
File: machineid

Comment 8 Jiri Koten 2015-01-28 13:07:34 UTC
Created attachment 985135 [details]
File: maps

Comment 9 Jiri Koten 2015-01-28 13:07:36 UTC
Created attachment 985136 [details]
File: open_fds

Comment 10 Jiri Koten 2015-01-28 13:07:38 UTC
Created attachment 985137 [details]
File: proc_pid_status

Comment 11 Jiri Koten 2015-01-28 13:07:40 UTC
Created attachment 985138 [details]
File: var_log_messages

Comment 14 Milan Crha 2015-05-19 09:49:41 UTC
This is the same issue as bug #1209787, thus I mark it as a duplicate of it.

*** This bug has been marked as a duplicate of bug 1209787 ***