gnome-system-log unable to open most log files

Bug #780355 reported by Mannex on 2011-05-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)

Bug Description

Binary package hint: gnome-utils

Starting gnome-system-log results in a window with "Could not open the following files:" at the start, followed by most of the log files. The first two for example are as follows:

/var/log/Xorg.1.log: Error stating file '/var/log/Xorg.1.log': No such file or directory
/var/log/lpr.log.1: Error stating file '/var/log/lpr.log.1': No such file or directory

Indeed, the files do not exist. So, why is system-log looking for them?

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gnome-system-log 2.32.0-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Tue May 10 00:29:18 2011
ExecutablePath: /usr/bin/gnome-system-log
SourcePackage: gnome-utils
UpgradeStatus: No upgrade log present (probably fresh install)
 (process:2861): Gtk-WARNING **: Locale not supported by C library.
 (process:4791): Gtk-WARNING **: Locale not supported by C library.

Mannex (russ-mannex) wrote :
Mannex (russ-mannex) wrote :

The problem here is that a system restoration was made from a backup, and the two OS versions were different. In the process, the default ~/.gconf/apps/gnome-system-log/%gconf.xml file was overwritten with an older version. Apparently, the 10.10 log files were named a little differently. Not having easy recourse to the default file settings (and also not wanting to necessarily set the file completely to default settings), I did the following:

cp ~/.gconf/apps/gnome-system-log/%gconf.xml ~/.gconf/apps/gnome-system-log/oldgconf.xml
gedit ~/.gconf/apps/gnome-system-log/%gconf.xml &
gksudo gedit /root/.gconf/apps/gnome-system-log/%gconf.xml &

Having both versions of the file open in the editor, I copied root's listing of which files to open and pasted them over the settings in my .xml file. A reboot later, and all is well.

This should be re-evaluated as NOTABUG.

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

Other bug subscribers