Description of problem:
This is reproducer of bug 1318615
Version-Release number of selected component:
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
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:1794
#7 _g_closure_invoke_va at gclosure.c:867
#10 g_settings_real_change_event at gsettings.c:386
#11 ffi_call_unix64 at ../src/x86/unix64.S:76
Created attachment 1173473 [details]
Created attachment 1173474 [details]
Created attachment 1173475 [details]
Created attachment 1173476 [details]
Created attachment 1173477 [details]
Created attachment 1173478 [details]
Created attachment 1173479 [details]
Created attachment 1173480 [details]
Created attachment 1173481 [details]
Created attachment 1173482 [details]
Created attachment 1173483 [details]
Created attachment 1173484 [details]
Created attachment 1173485 [details]
*** Bug 1318615 has been marked as a duplicate of this bug. ***
Some random gsettings key ("cursor-blink-timeout") changed on the schema org.gnome.desktop.interface, triggering the on_schema_change callback that calls update_clock. But priv->timezone is NULL at the time, and update_clock is not prepared to handle that case, causing the crash when it's passed to g_date_time_new_now.
Problem is, priv->timezone should never be NULL there and I don't see how it could have happened. priv->timezone is initialized in _init and can't possibly become invalid until the wall clock is finalized, but by that point the settings watch would have already been disconnected (by unreffing the GSettings object in dispose) and so on_schema_changed could never be called. It might be a bit safer to use g_signal_connect_object there, but it shouldn't matter since nothing else ever refs the GSettings object. So I don't see it.
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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'
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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
Thank you for reporting this bug and we are sorry it could not be fixed.