Ubuntu
gnome-system-log package

After entering filter it crashed and cannot restart

Asked by Talji Mera

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

What is wrong here? I used the same filter in the previous version 3.4.1 without any problem.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-system-log Edit question
Assignee:
No assignee Edit question
Solved by:
Talji Mera
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

I suggest you report a bug.

Instead of some GUI thing, why don't you just grep all the files in /var/log? Learning how to do this will allows you to be able to do it on other Linux and even UNIX systems. Learning transferable skills is advantageous and not every system will have the log viewer, or even a desktop interface but you will be able to analyse your logs just the same.

Revision history for this message
Talji Mera (ttjimera) said : 		#2

I use grep when I need to. But I have a habit of leaving gnome-system-log and a conky "system dashboard"opened on my desktop. When anything happened on the system they are the first thing I look at to get an overview of what is happening. Then only I use other relevant tools to get the details including CLI if I have to.

Revision history for this message
Talji Mera (ttjimera) said : 		#3

I am trying to find where gnome-system-log keeps its config files so I can hopefully remove the filter I have entered. The application cannot start because for some reason the filter entered cause it to crash before it can come up. Does anyone know where these files are? Going through my home directory I cannot see anything relevant. The man page is also of no help.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#4

Try looking in dconf or in ~/.config

I'm not sure but maybe others can advise

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

If you run the application prefixed with sudo, is it OK?

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#6

What is the output of:

lsb_release -a; uname -a; apt-cache policy gnome-system-log

Thanks

Revision history for this message
Talji Mera (ttjimera) said : 		#7

I managed to remove the filter via dconf. The application is running now. Thanks.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#8

Awesome!

As I said before, using grep will allow you to work on more systems as the application may not always be installed or available to be installed.