Ask Your Question

Controlling access to logs

asked 2018-03-24 00:14:05 -0500

The Evil One gravatar image

If I call the log viewer from the Application menu I get a message "Unable to read system logs". If I invoke gnome-logs as root user in a terminal I get a message "Unable to read user logs"

To see everything I need to open the logviewer twice, once from activities and once from a terminal set to root and I am not sure that there are not some things still unseen.

How can I get access to all logs at once in one place?

Is it specified somewhere which logonids can access which logs?

Is it specified somewhere what events are logged or that could be logged but currently are not logged?

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2018-03-24 15:17:33 -0500

Aeyoun gravatar image

You know that little toolbar that tells you that you can’t read logs? The Help button on that toolbar takes you to a useful page.

All you need to do is to add your user to the systemd-journal group. The following command adds the user Jeff to that group:

usermod -a -G systemd-journal Jeff
edit flag offensive delete link more


Thank you Aeyoun have used this command and now the log viewer no longer has that pesky message and I get access to all logs.

The Evil One gravatar imageThe Evil One ( 2018-03-26 04:22:45 -0500 )edit

Question Tools

1 follower


Asked: 2018-03-24 00:14:05 -0500

Seen: 135 times

Last updated: Mar 24 '18