Description of problem: unable to see system messages with journalctl even though I am in the adm group. $ groups bittwister adm disk lp floppy games cdrom usb cdwriter audio video <snip> This worked on Mageia 3. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Clean install of Mageia-4-alpha1-LiveDVD-KDE4-x86_64-DVD.iso. Default runlevel: 3 Followed with: remove-unused-packages urpmi --downloader wget --auto --auto-update urpme --auto-orphans and reboot. 1. click up a terminal as user 2. journalctl | grep systemd Note, no lines shown 3. su - root 4. journalctl | grep systemd | head Reproducible: Steps to Reproduce:
CC: (none) => mageia
mageia 3 # dir -h /var/log/journal/$(cat /etc/machine-id) total 45M drwxr-xr-x 2 root root 4.0K Aug 11 21:02 . drwxr-xr-x 3 root root 4.0K May 20 08:57 .. -rw-r----- 1 root adm 12M Aug 12 13:13 system.journal -rw-r-----+ 1 root adm 4.0M Aug 12 13:02 user-1500.journal -rw-r-----+ 1 root adm 3.6M Aug 10 06:06 user-1505.journal mageia 4 # dir -h /var/log/journal/$(cat /etc/machine-id) total 12M drwxr-xr-x 2 root root 4.0K Aug 12 13:09 . drwxr-xr-x 3 root root 4.0K Aug 11 05:18 .. -rw-r----- 1 root root 4.8M Aug 12 13:15 system.journal -rw-r-----+ 1 root root 3.6M Aug 12 13:07 user-1500@cd3bcd3da8eb4528815a3d8880ea06de-0000000000000502-0004e3b6d8d65657.journal -rw-r-----+ 1 root root 3.6M Aug 12 13:14 user-1500.journal
(In reply to Bit Twister from comment #0) > This worked on Mageia 3. man systemd-journald indicates Distributions and administrators may choose to grant read access to all members of the "wheel" and "adm" system groups with a command such as the following: setfacl -Rnm g:wheel:rx,d:g:wheel:rx,g:adm:rx,d:g:adm:rx /var/log/journal/ Your decision to resolve this if Mageia Distribution is now leaving it up to the system administrator to issue the command. If so, I suggest a note in the errata document just to keep any further bug reports about it.
While I think errata is more for bugs in our distribution that could not be fixed prior to release, and this is a deliberate change in behaviour by upstream to not force behaviour on downstreams, the errata does seem like the best place to put it. Please feel free to edit the errata if you get a moment: https://wiki.mageia.org/en/Mageia_4_Errata
Added "User access to system log messages" to "Software Issues" of errata document.
Status: NEW => RESOLVEDCC: (none) => junknospamResolution: (none) => FIXED