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:
** 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 Desktop
Packages, which is subscribed to gnome-logs in Ubuntu.
https://bugs.launchpad.net/bugs/1879741
Title:
Proposed version working fine :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-logs in Ubuntu.
https://bugs.launchpad.net/bugs/1879741
Title:
Unable to read system logs
Status in gnome-logs package in Ubuntu:
Fix Released
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
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)
--
** 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
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 Desktop
Packages, which is subscribed to gnome-logs in Ubuntu.
https://bugs.launchpad.net/bugs/1879741
Title:
Unable to
Possibly fixed here: https://gitlab.gnome.org/GNOME/gnome-
logs/-/issues/52
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-logs in Ubuntu.
https://bugs.launchpad.net/bugs/1879741
Title:
Unable to read system logs
Status in
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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to gnome-logs in Ubuntu.
10 matches
Mail list logo