Bug#866171: gnome-logs: Launching gnome-logs provides an error "Unable to read system logs"

[Arcademan]

Package: gnome-logs
Version: 3.22.1-2
Severity: normal

Dear Maintainer,

Step 1: On a Gnome System (launch gnome-logs) from the main menu.

Step 2: After gnome-logs is launched you will notice that the program is
"Unable to read system logs".

Step 3 - Fix: Launching gnome-logs using "#sudo gnome-logs" corrects the issue:
so the application launcher will need either updated to use "sudo" or the user
will need permission to look in /var/logs/.



-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-logs depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gsettings-desktop-schemas                    3.22.0-1
ii  libc6                                        2.24-11+deb9u1
ii  libglib2.0-0                                 2.50.3-2
ii  libgtk-3-0                                   3.22.11-1
ii  libsystemd0                                  232-25

gnome-logs recommends no packages.

gnome-logs suggests no packages.

-- no debconf information
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log-error.png
Type: image/png
Size: 22234 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20170627/768b6ec5/attachment-0001.png>