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 1049954 - [abrt] gnome-shell-3.8.1-3.fc19: calendar_sources_init: Process /usr/libexec/gnome-shell-calendar-server was killed by signal 5 (SIGTRAP)
Summary: [abrt] gnome-shell-3.8.1-3.fc19: calendar_sources_init: Process /usr/libexec/...
Keywords:
Status: CLOSED DUPLICATE of bug 1017824
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.0
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL: http://faf-report.itos.redhat.com/rep...
Whiteboard: abrt_hash:2255b55fcf7e9d17776d9898b20...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-08 14:29 UTC by Michal Toman
Modified: 2015-05-07 13:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 960787
Environment:
Last Closed: 2015-05-07 13:41:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michal Toman 2014-01-08 14:29:56 UTC
+++ This bug was initially created as a clone of Bug #960787 +++

Version-Release number of selected component:
gnome-shell-3.8.1-3.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-shell-calendar-server
crash_function: calendar_sources_init
executable:     /usr/libexec/gnome-shell-calendar-server
kernel:         3.9.0-301.fc19.i686.PAE
runlevel:       N 5
uid:            1000
var_log_messages: May  8 08:08:31 localhost abrt[1994]: Saved core dump of pid 1686 (/usr/libexec/gnome-shell-calendar-server) to /var/tmp/abrt/ccpp-2013-05-08-08:08:31-1686 (35536896 bytes)

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 calendar_sources_init at calendar-server/calendar-sources.c:190
 #3 g_type_create_instance at gtype.c:1917
 #4 g_object_constructor at gobject.c:1855
 #7 calendar_sources_get at calendar-server/calendar-sources.c:276
 #8 app_new at calendar-server/gnome-shell-calendar-server.c:773
 #9 on_bus_acquired at calendar-server/gnome-shell-calendar-server.c:989
 #10 connection_get_cb at gdbusnameowning.c:480
 #11 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #12 complete_in_idle_cb at gsimpleasyncresult.c:789

Potential duplicate: bug 878146

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:14 ---

Created attachment 744946 [details]
File: backtrace

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:18 ---

Created attachment 744947 [details]
File: cgroup

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:20 ---

Created attachment 744948 [details]
File: core_backtrace

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:22 ---

Created attachment 744949 [details]
File: dso_list

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:24 ---

Created attachment 744950 [details]
File: environ

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:27 ---

Created attachment 744951 [details]
File: limits

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:29 ---

Created attachment 744952 [details]
File: maps

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:32 ---

Created attachment 744953 [details]
File: open_fds

--- Additional comment from mikhail.v.gavrilov on 20130508T02:10:34 ---

Created attachment 744954 [details]
File: proc_pid_status

--- Additional comment from rdrijsen on 20130508T19:02:03 ---

Problem occurred during start up

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-shell-calendar-server
crash_function: calendar_sources_init
executable:     /usr/libexec/gnome-shell-calendar-server
kernel:         3.9.0-0.rc8.git0.2.fc19.x86_64
package:        gnome-shell-3.8.1-1.fc19
reason:         Process /usr/libexec/gnome-shell-calendar-server was killed by signal 5 (SIGTRAP)
runlevel:       unknown
uid:            1000

Comment 1 Michal Toman 2014-01-08 14:29:58 UTC
The same problem has been detected in Red Hat Enterprise Linux 7. The following packages are affected:

gnome-shell-3.8.4-14.el7.x86_64
gnome-shell-3.8.4-16.el7.x86_64
gnome-shell-3.8.4-17.el7.x86_64

Comment 3 RHEL Program Management 2014-03-22 06:17:18 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 Michal Domonkos 2015-05-07 13:41:02 UTC
Same backtrace as in 1017824, closing as a duplicate.

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


Note You need to log in before you can comment on or make changes to this bug.