As installed according to Gnome default from 13.2RC1 DVD, Gnome-clocks floods the user journal with some 2000 errors/s like that
...
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:04 linux-a2yg.site org.gnome.clocks[1850]: (gnome-clocks:2924): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Oct 31 22:51:34 linux-a2yg.site org.freedesktop.Tracker1[1850]: (tracker-store:2059): GLib-CRITICAL **: Source ID 276 was not found when attempting to remove it
Oct 31 22:51:34 linux-a2yg.site org.freedesktop.Tracker1[1850]: (tracker-store:2059): GLib-CRITICAL **: Source ID 279 was not found when attempting to remove it
Oct 31 23:02:34 linux-a2yg.site org.gnome.Calculator.SearchProvider[1850]: Error: ErrorCode.INVALID
Oct 31 23:02:35 linux-a2yg.site org.gnome.Calculator.SearchProvider[1850]: ** (org.gnome.Calculator.SearchProvider:3144): WARNING **: (search-provider.c:528):search_provider_get_result_identifier: runtime check
Oct 31 23:02:35 linux-a2yg.site org.gnome.Caribou.Daemon[1850]: ** (caribou:2010): WARNING **: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.43 was not provided by any .service files
Oct 31 23:02:35 linux-a2yg.site org.gnome.ControlCenter.SearchProvider[1850]: ** (process:3145): WARNING **: Ignoring broken panel dconf-editor (missing desktop file)
Oct 31 23:02:35 linux-a2yg.site org.gnome.ControlCenter.SearchProvider[1850]: ** (process:3145): WARNING **: Ignoring broken panel alacarte (missing desktop file)
Oct 31 23:02:35 linux-a2yg.site org.gnome.ControlCenter.SearchProvider[1850]: ** (process:3145): WARNING **: Ignoring broken panel gpk-prefs (missing desktop file)
Oct 31 23:02:35 linux-a2yg.site org.gnome.ControlCenter.SearchProvider[1850]: ** (process:3145): WARNING **: Ignoring broken panel tracker-preferences (missing desktop file)
...
After starting Gnome-clocks for the first time and setting up a “home city” to display at least one clock, it quiets down but occasional bursts of 1-2 seconds still occur.
On laptops with slow disk (SATA-I) and journal-on-disk (as per 13.2RC1 default installation) this slows the boot process to the point that the system seems almost unbootable and keeps worsening with usage because of a growing journal (more than 200MB seen on this test system).
Maybe this is just a setting for RC1 testing, but it would be very annoying to an ordinary laptop user.