After entering filter it crashed and cannot restart

[Talji Mera]

I reported this on https://answers.launchpad.net/ubuntu/+source/gnome-system-log/+question/295921 but was asked to report it as a bug.

I am using Ver. 3.9.90-4. When I entered filter for a single item (e.g. A) there is no problem. But after entering filter for mutiple item (e.g. A|B|C) it crashed and cannot restart. When I started from terminal I got the following message.

(process:6957): GLib-GObject-CRITICAL **: g_param_spec_boxed: assertion 'G_TYPE_IS_BOXED (boxed_type)' failed

(process:6957): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed

(process:6957): GLib-GObject-CRITICAL **: g_param_spec_boxed: assertion 'G_TYPE_IS_BOXED (boxed_type)' failed

(process:6957): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed

(process:6957): GLib-GObject-CRITICAL **: g_param_spec_boxed: assertion 'G_TYPE_IS_BOXED (boxed_type)' failed

(process:6957): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed

(process:6957): GLib-GObject-WARNING **: g_object_set_valist: object class 'GtkTextTag' has no property named 'paragraph-background-gdk'

(process:6957): GLib-GObject-WARNING **: g_object_set_valist: object class 'GtkTextTag' has no property named 'paragraph-background-gdk'

(process:6957): GLib-GObject-WARNING **: g_object_set_valist: object class 'GtkTextTag' has no property named 'paragraph-background-gdk'

(gnome-system-log:6957): GLib-GIO-ERROR **: g_menu_item_set_detailed_action: Detailed action name 'win.filter_general protection' has invalid format
Trace/breakpoint trap

[Talji Mera (ttjimera)]

After some probing, I think the problem is with the name of the filter and not the regular expression. Putting a space in the name caused the application to crash. The solution is replace the space with a hyphen. This was not a problem with version 3.4.1 which I used previously.

[Sebastien Bacher (seb128)]

Thank you for your bug report, that seems similar to https://bugzilla.gnome.org/show_bug.cgi?id=763843 which is fixed in the upstream git trunk