[Bug 1190837] New: gnome logs unable to read system logs
https://bugzilla.suse.com/show_bug.cgi?id=1190837 Bug ID: 1190837 Summary: gnome logs unable to read system logs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: gnome-bugs@suse.de Reporter: pureacetone@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I'm getting "Unable to read system logs" message from gnome logs. Journalctl works flawlessly and I can read the logs from yast without any problems. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1190837 https://bugzilla.suse.com/show_bug.cgi?id=1190837#c1 Jonathan Kang <songchuan.kang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |songchuan.kang@suse.com --- Comment #1 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Roi C. from comment #0)
I'm getting "Unable to read system logs" message from gnome logs. Journalctl works flawlessly and I can read the logs from yast without any problems.
This is working as intended. When you see "Unable to read system logs", click the "help" button next to it to see why that's happening. Normal users can only view journal from the current user. To view system journal, you'll need administrator permission or be in the "systemd-journal" user group. You can view those logs from yast because you have input your root password when opening yast. By default, "journalctl" works and only shows logs from the current user. You can try "journalctl -k" and see what this command shows you. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1190837 https://bugzilla.suse.com/show_bug.cgi?id=1190837#c2 Roi C. <pureacetone@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Roi C. <pureacetone@gmail.com> --- Adding the user to systemd-journal group does the trick. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com