Closed nedrichards closed 6 years ago
bot, build
Build is at: https://flathub.org/builds/#/builders/2/builds/4796
bot, build
this latest commit to also update to the 3.30 runtime has a few more CLI warnings than the previous version:
flatpak run org.gnome.Calendar
(process:3): libecal-CRITICAL **: 12:03:01.626: e_cal_util_get_system_timezone: assertion 'location != NULL' failed
** (process:3): CRITICAL **: 12:03:01.627: e_cal_data_model_set_timezone: assertion 'zone != NULL' failed
** (gnome-calendar:3): CRITICAL **: 12:03:01.797: e_cal_data_model_set_timezone: assertion 'zone != NULL' failed
** (gnome-calendar:3): CRITICAL **: 12:03:01.797: e_cal_data_model_set_timezone: assertion 'zone != NULL' failed
(gnome-calendar:3): GLib-CRITICAL **: 12:03:01.801: g_variant_get_type: assertion 'value != NULL' failed
(gnome-calendar:3): GLib-CRITICAL **: 12:03:01.801: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
(gnome-calendar:3): GLib-CRITICAL **: 12:03:01.801: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
(gnome-calendar:3): libecal-CRITICAL **: 12:03:01.958: e_cal_util_get_system_timezone: assertion 'location != NULL' failed
(gnome-calendar:3): libecal-CRITICAL **: 12:03:01.958: e_cal_util_get_system_timezone: assertion 'location != NULL' failed
(gnome-calendar:3): GLib-GIO-WARNING **: 12:03:02.526: Failed to get the 'connectivity' property
(gnome-calendar:3): GLib-GIO-WARNING **: 12:03:02.527: Failed to get the 'metered' property
(gnome-calendar:3): GLib-GIO-WARNING **: 12:03:02.527: Failed to get the 'available' property
(gnome-calendar:3): Utils-WARNING **: 12:03:02.698: Locale is NULL, assuming Saturday and Sunday as non workdays
Beforehand on 3.28 we just got the:
(gnome-calendar:3): Utils-WARNING **: 12:03:02.698: Locale is NULL, assuming Saturday and Sunday as non workdays
I could try enabling libdb in e-d-s if that makes a difference (looks like that's been dropped from the latest runtime), but I thought that was just for ebook which shouldn't make a difference to Calendar. But other than the CLI warnings this appears to 'just work' on my machine.
Tested locally, works fine