Hi.
On Sun, Oct 27, 2019 at 12:17:37PM -0700, Berkhan Berkdemir wrote:
> Hello,
> A few days ago, I wanted to use GNOME Logs on a fresh Debian 10 installed
> machine. The package comes with the GNOME environment, so I didn't do
> apt install. However, what I got is just an error:
>
> root@my-hostname:~# cat /var/log/messages
> ...
> Oct 27 11:56:55 my-hostname gnome-logs[6048]: Error retrieving the sender
> timestamps: Cannot assign requested address
Harmless. A sign of a bad programming, but nothing more.
> Oct 27 11:56:55 my-hostname kernel: [31613.658716] gnome-logs[6048]:
> segfault at 17fffffff8 ip 0000555b08fbfb4f sp 00007ffcb3f3f9b0 error 4 in
> gnome-logs[555b08fb6000+e000]
That's interesting. I was able to reproduce your problem. An abridged
stacktrace from the core dump is:
#0 0x000055faf6730b4f in gl_journal_update_latest_timestamp
(journal=0x55faf80c1360) at ../src/gl-journal.c:98
#1 gl_journal_get_boot_time (journal=0x55faf80c1360, boot_match=0x0) at
../src/gl-journal.c:127
#2 0x000055faf67324c9 in gl_journal_model_get_boot_time (model=<optimized
out>, boot_match=<optimized out>)
at ../src/gl-journal-model.c:1158
#3 0x000055faf672c6b0 in gl_event_view_list_get_boot_time
(view=view@entry=0x55faf829d250, boot_match=<optimized out>)
at ../src/gl-eventviewlist.c:402
And it's Debian bug #899204, still not fixed.
> I haven't touched anything on the system, and I get this segfault.
And it seems to me you're supposed to get it. Because...
> I am thinking a few scenarios:
> 1. non-root user does not have access to /var/log -- which makes
> sense, and therefore, maybe, GNOME Logs can't read. However, I was
> working no issue with Ubuntu. Probably, default Ubuntu user has enough
> *power* to read /var/log files.
Files do not apply to the problem. Systemd's journal does. gnome-logs'
source is pretty clear on that - multiple sd_journal* calls, no attempt
to even read a single file.
> 2. I deleted a few packages before using GNOME Logs, and maybe, this led to
> that segfault
Nope. It's a configuration problem, so to speak. Or a developer's
oversight. Or maybe both.
Gnome-logs can show you the contents of systemd's journal, but only if
your user can access it. It segfaults if your user cannot do it.
Of course, a *sane* developer would test this particular scenario, but,
well, it's GNOME.
Out-of-the box Debian should show to a non-root user this (and that's a
good programming BTW - you have a problem and they show you what's
wrong):
$ journalctl
Hint: You are currently not seeing messages from other users and the
system. Users in the 'systemd-journal' group can see all messages. Pass
-q to turn off this notice.
No journal files were opened due to insufficient permissions.
Adding a user to the mentioned group fixes the issue for me.
Reco
