[Bug 1879741] Re: Unable to read system logs

2020-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-logs - 3.34.0-1ubuntu1 --- gnome-logs (3.34.0-1ubuntu1) focal; urgency=medium * debian/patches/git_log_permissions.patch: - Improve the check for reading system journal, fixes the misleading warning displayed as a banner (lp: #187974

[Bug 1879741] Re: Unable to read system logs

2020-06-01 Thread Sebastien Bacher
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879741 Title: Unable to read sy

[Bug 1879741] Re: Unable to read system logs

2020-06-01 Thread John Tanner
Proposed version working fine :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879741 Title: Unable to read system logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubu

[Bug 1879741] Re: Unable to read system logs

2020-05-22 Thread Steve Langasek
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-foca

[Bug 1879741] Re: Unable to read system logs

2020-05-21 Thread Launchpad Bug Tracker
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) -- Seb

[Bug 1879741] Re: Unable to read system logs

2020-05-21 Thread Sebastien Bacher
** Description changed: + * 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

[Bug 1879741] Re: Unable to read system logs

2020-05-21 Thread Sebastien Bacher
Indeed, good finding, thank you ** Changed in: gnome-logs (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879741 Title: Unable to read system logs To ma

[Bug 1879741] Re: Unable to read system logs

2020-05-21 Thread John Tanner
Possibly fixed here: https://gitlab.gnome.org/GNOME/gnome- logs/-/issues/52 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879741 Title: Unable to read system logs To manage notifications about thi

[Bug 1879741] Re: Unable to read system logs

2020-05-21 Thread John Tanner
journalctl at the command line works fine for all users. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-logs/-/issues #52 https://gitlab.gnome.org/GNOME/gnome-logs/-/issues/52 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https

[Bug 1879741] Re: Unable to read system logs

2020-05-21 Thread Sebastien Bacher
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne