Bug 1178627

Summary: [abrt] gnome-shell: g_time_zone_ref(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Milan Zink <mzink>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: ali+rhbugzilla, fmuellner, iweiss, kubrick, moshe, otaylor, social, soc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7dd2aabb5aa991e302ee09bd1a2117178dbfbc6d
Whiteboard: abrt_hash:07372d98b885f1a3ae1ed70c6017de218bf11fac
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 06:55:02 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: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Milan Zink 2015-01-05 07:33:56 UTC 
Version-Release number of selected component:
gnome-shell-3.14.2-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: g_time_zone_ref
executable:     /usr/bin/gnome-shell
kernel:         3.17.6-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            24473

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_time_zone_ref at gtimezone.c:267
 #1 g_date_time_alloc at gdatetime.c:429
 #2 g_date_time_from_instant at gdatetime.c:524
 #3 g_date_time_new_from_timeval at gdatetime.c:647
 #4 g_date_time_new_now at gdatetime.c:705
 #5 update_clock at gnome-wall-clock.c:350
 #6 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #7 _g_closure_invoke_va at gclosure.c:831
 #10 g_settings_real_change_event at gsettings.c:277
 #11 ffi_call_unix64 at ../src/x86/unix64.S:76

Potential duplicate: bug 1162473
Comment 1 Milan Zink 2015-01-05 07:33:59 UTC 
Created attachment 976199 [details]
File: backtrace
Comment 2 Milan Zink 2015-01-05 07:34:00 UTC 
Created attachment 976200 [details]
File: cgroup
Comment 3 Milan Zink 2015-01-05 07:34:01 UTC 
Created attachment 976201 [details]
File: core_backtrace
Comment 4 Milan Zink 2015-01-05 07:34:03 UTC 
Created attachment 976202 [details]
File: dso_list
Comment 5 Milan Zink 2015-01-05 07:34:04 UTC 
Created attachment 976203 [details]
File: environ
Comment 6 Milan Zink 2015-01-05 07:34:05 UTC 
Created attachment 976204 [details]
File: exploitable
Comment 7 Milan Zink 2015-01-05 07:34:06 UTC 
Created attachment 976205 [details]
File: limits
Comment 8 Milan Zink 2015-01-05 07:34:08 UTC 
Created attachment 976206 [details]
File: maps
Comment 9 Milan Zink 2015-01-05 07:34:09 UTC 
Created attachment 976207 [details]
File: open_fds
Comment 10 Milan Zink 2015-01-05 07:34:10 UTC 
Created attachment 976208 [details]
File: proc_pid_status
Comment 11 Milan Zink 2015-01-05 07:34:12 UTC 
Created attachment 976209 [details]
File: var_log_messages
Comment 12 kubrick@fgv6.net 2015-03-27 16:22:10 UTC 
Another user experienced a similar problem:

Alt-tab to switch program

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        gnome-shell --sm-client-id 10360e90c1586dc4d6142598229375607600000027630000
crash_function: g_time_zone_ref
executable:     /usr/bin/gnome-shell
kernel:         3.19.1-201.fc21.x86_64
package:        gnome-shell-3.14.3-1.fc21
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Red Hat Production Operations 2015-05-26 14:57:46 UTC 
For me it seems to occur after returning from the lock screen.
Comment 14 Red Hat Production Operations 2015-06-09 17:08:16 UTC 
The previous comment was from moshe (was logged in via the wrong account)
Comment 15 Fedora End Of Life 2015-11-04 11:31:31 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 Fedora End Of Life 2015-12-02 06:55:06 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.