After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 567169 - could not open files error displayed for no good reason
could not open files error displayed for no good reason
Status: RESOLVED WONTFIX
Product: gnome-system-log
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-system-log-maint
gnome-system-log-maint
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2009-01-09 16:14 UTC by Sebastien Bacher
Modified: 2020-09-26 09:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Sebastien Bacher 2009-01-09 16:14:05 UTC
when starting gnome-system-log on jaunty those error are displayed

"/var/log/XFree86.0.log: Error stating file '/var/log/XFree86.0.log': No such file or directory
/var/log/cron: Error stating file '/var/log/cron': No such file or directory
/var/log/maillog: Error stating file '/var/log/maillog': No such file or directory
/var/log/secure: Error stating file '/var/log/secure': No such file or directory
/var/log/sys.log: Error stating file '/var/log/sys.log': No such file or directory"

is there any reason to display those rather as errors? should the code just list all the logs available in this directory? XFree86.0.log not being available is not an error for example, the log is named Xorg.0.log
Comment 1 TJ 2009-02-19 07:08:46 UTC
Arrived here from Ubuntu bug #318689.

The cause seems to be a user profile that has been upgraded from an older distro release, where the contents of /var/log/ haven't been inherited. It can also happen where multiple release installations share a common /home/$USER/.

The gconf settings key "/apps/gnome-system-log/logfiles" contains a list of strings with the names of log-files the user has previously added.

 gconftool-2 -g /apps/gnome-system-log/logfiles

 [/var/log/kern.log.0,/var/log/messages,/var/log/acpid,/var/log/dmesg,/var/log/Xorg.0.log,/home/tj/.xsession-errors,/var/log/auth.log,/var/log/kern.log,/var/log/daemon.log,/var/log/syslog,/var/log/user.log]

The problem appears to be that when a log-file no longer exists it isn't removed from the list automatically but crucially, isn't listed in the side-pane either, so the user has no way to remove it.
Comment 2 Cosimo Cecchi 2009-03-02 15:32:37 UTC
This is fixed in trunk now, thanks for the report.

2009-03-02  Cosimo Cecchi  <cosimoc@gnome.org>

	* logview-app.c: (parse_syslog), (enumerate_job_finish),
	(enumerate_next_files_async_cb), (enumerate_children_async_cb),
	(logview_app_first_time_initialize), (logview_app_initialize):
	* logview-prefs.c: (logview_prefs_init): when starting the
	application for the first time, gather all the readable files from
	/var/log instead of hardcoding logfile names.
	We'll eventually, and hopefully, support a smarter parsing of
	/etc/logrotate.* and log rotated/compressed log grouping, but right
	now this is the best effort we can do (#567169).
Comment 3 Sebastien Bacher 2009-03-03 22:42:24 UTC
reopening, that fixes the first start issue but not case where logs available change on disk for example
Comment 4 Hernando Torque 2009-03-08 13:58:21 UTC
Wouldn't the easiest solution be to just let the user edit the log list from within the application?

Mockup: http://img.xrmb2.net/images/171545.png
Comment 5 André Klapper 2020-09-26 09:40:43 UTC
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.