Unable to read system logs

Bug #1879741 reported by John Tanner on 2020-05-20
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-logs (Ubuntu)
Low
Unassigned
Focal
Undecided
Unassigned

Bug Description

* Impact
A warning 'Unable to read system logs' is always displayed even when the logs are opened without issue

* Test Case
start gnome-logs, check that there is no warning displayed and that the log are available

* Regression potential
The change is in the code checking the journal files so check that if the log are correctly found and opened, they shouldn't be change in how they are handled once they are loaded

------------------------------------------

1) Ubuntu 20.04 LTS
2) Gnome Logs 3.34.0-1
3) Open Gnome Logs and expect to be able to read all logs from the system
4) Gnome Logs opens and at the top there is an error message "Unable to read system logs" - screenshot attached.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-logs 3.34.0-1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 20 17:04:21 2020
InstallationDate: Installed on 2020-05-17 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-logs
UpgradeStatus: No upgrade log present (probably fresh install)

Sebastien Bacher (seb128) wrote :

Thank you for your bug repot, does using 'journalctl' on a command line works for your users?

Changed in gnome-logs (Ubuntu):
importance: Undecided → Low

journalctl at the command line works fine for all users.

Sebastien Bacher (seb128) wrote :

Indeed, good finding, thank you

Changed in gnome-logs (Ubuntu):
status: New → Fix Committed
description: updated
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-logs - 3.36.0-2

---------------
gnome-logs (3.36.0-2) unstable; urgency=medium

  * debian/patches/git_log_permissions.patch:
    - Improve the check for reading system journal, fixes the misleading
      warning displayed as a banner (lp: #1879741)

 -- Sebastien Bacher <email address hidden> Thu, 21 May 2020 15:26:10 +0200

Changed in gnome-logs (Ubuntu):
status: Fix Committed → Fix Released
Steve Langasek (vorlon) wrote :

seems like a lot of complexity in that patch to check for a subdir instead of just reversing the order of precedence to look for /var/log/journal first, but ok.

Changed in gnome-logs (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed verification-needed-focal

Hello John, or anyone else affected,

Accepted gnome-logs into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-logs/3.34.0-1ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.