Version 3 vs 4
Version 3 vs 4
Content Changes
Content Changes
{nav icon=home, name=Main Page >
icon=wrench, name=Troubleshooting >
GNOME Logs not working}
GNOME Logs application cannot see any logs or crashing
---
== Problem ==
GNOME Logs does not display anything, or it doesn't start at all (running `gnome-logs` from terminal shows segfault).
== Cause ==
Probably your user does not have permissions to read //journal// logs..
== Solution ==
Add your user to the **systemd-journal** group:
{icon terminal}`sudo usermod -aG systemd-journal USERNAME`
where USERNAME is your username, you can find it by running
{icon terminal}`whoami`.
NOTE: For the group edit to get into effect, you must logout and login again.
{nav icon=home, name=Main Page >
icon=wrench, name=Troubleshooting >
GNOME Logs not working}
GNOME Logs application cannot see any logs or crashing
---
== Problem ==
GNOME Logs does not display anything, or it doesn't start at all (running `gnome-logs` from terminal shows segfault).
== Cause ==
Probably your user does not have permissions to read //journal// logs..
== Solution ==
Add your user to the **systemd-journal** group:
{icon terminal}`sudo usermod -aG systemd-journal USERNAME`
where USERNAME is your username, you can find it by running
{icon terminal}`whoami`.
NOTE: For the group edit to get into effect, you must restart.
{nav icon=home, name=Main Page >
icon=wrench, name=Troubleshooting >
GNOME Logs not working}
GNOME Logs application cannot see any logs or crashing
---
== Problem ==
GNOME Logs does not display anything, or it doesn't start at all (running `gnome-logs` from terminal shows segfault).
== Cause ==
Probably your user does not have permissions to read //journal// logs..
== Solution ==
Add your user to the **systemd-journal** group:
{icon terminal}`sudo usermod -aG systemd-journal USERNAME`
where USERNAME is your username, you can find it by running
{icon terminal}`whoami`.
NOTE: For the group edit to get into effect, you must logout and login againrestart.