gnome-system-log crashed during start

Bug #1248684 reported by disto2 on 2013-11-06
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-system-log (Ubuntu)

Bug Description

gnome-system-log can't start

i've upgradet from 12.04 to 13.10 couple of days ago.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-system-log 3.8.1-1svn1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 6 20:29:15 2013
InstallationDate: Installed on 2013-10-28 (9 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: gnome-system-log
UpgradeStatus: No upgrade log present (probably fresh install)

disto2 (disto2) wrote :
disto2 (disto2) wrote :

When starting gnome-system-log from terminal i get the following message:

(gnome-system-log:1062): GLib-GIO-ERROR **: g_menu_item_set_detailed_action: Detailed action name 'win.filter_DPKG remove' has invalid format
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-system-log (Ubuntu):
status: New → Confirmed
Bart (bart2pub) wrote :

same for me after making a filter.

Bart (bart2pub) wrote :

Found the bug: gnome-system-log crashes when you make a filter and put a space in the name and click 'Apply'.
Would be nice if it would give a warning instead.

The filter settings are saved as a gsettings scheme: org.gnome.gnome-system-log.filters. You can edit them with dconf-editor (org>gnome>gnome-system-log>filters). Replace the space in the name of the filter with a dash (or some other character), and gnome-system-log will work again.

Be aware that there is another bug with gnome-system-log in ubuntu 13.10. It won't launch when you use a Gtk+ Shimmer theme.

Rob Hills (rhills) wrote :

I created a filter using a Regex expression. Following this, gnome-system-log crashes each time I try to start it, with the following error message:

(gnome-system-log:6811): GLib-GIO-ERROR **: g_menu_item_set_detailed_action: Detailed action name 'win.filter_Vesper Marine' has invalid format

My filter was simply this:


I don't do much Regex and I was trying to do a case-insensitive search. Anyway, hopefully this will help developers to reproduce the but.

Hồng Quân (ng-hong-quan) wrote :

I don't have filter and already reset all setting to default, via dconf-editor, but System Log still crashes.

$ gnome-system-log
[1] 16096 segmentation fault (core dumped) gnome-system-log

Ubuntu 14.10
gnome-system-log 3.9.90-2

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers