GNOME Bugzilla – Bug 627372
impossible to edit list of monitored logs within gnome-system-log
Last modified: 2020-09-26 09:40:58 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-utils/+bug/619898 "In gnome-system-log, it is impossible to view/edit the list of monitored logs. The problem comes up when some logfile disappears, while system log still attempts to open the file. This results in an error on startup, saying "Error stating file....". This error happens upon every start of gnome-system-log. Currently, there are two (quite suboptimal) ways of getting rid of it. (1) recreate the file, start system log, select that file, and choose File -> Close (2) open gconf editor, browse over to /apps/gnome-system-log, and edit the 'logfiles' value to remove the offending entry. This is a clear usability bug, since it should be possible to edit the list of log files that gnome-system-log attempts to open from within the application itself. There should be some menu item (maybe "Edit -> File List..." or something along those lines) that brings up a window with a list of currently-monitored files. Something like the mock-up attached to comment 4 on this bug thread here: https://bugzilla.gnome.org/show_bug.cgi?id=567169 Bug reports about this have been opened before,but the target of the bugs was the showing of error messages, rather than the usability problem of inability to edit file list. So I think this report brings the right focus to the problem at hand."
gnome-system-log is not under active development anymore and had its last code changes more than four years ago. Its codebase has been archived at https://gitlab.gnome.org/Archive/gnome-system-log/ Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again.