switching branches with gitg open results in console spam: GLib-CRITICAL **: 11:23:32.669: g_date_time_difference: assertion 'begin != NULL' failed
If I open gitg from the console
gitg &
and then continue working using command-line git in the same repo (git pull seems to be a good trigger), the console will get spammed with dozens if not hundreds of messages like:
(gitg:1045952): GLib-CRITICAL **: 11:23:45.638: g_date_time_difference: assertion 'begin != NULL' failed
It happens a lot when working with my kernel repo: https://gitlab.com/belegdol/kernel-ark/. This is on Fedora 33 x86_64 and gitg-3.32.1-7.fc33.x86_64.