Bug#948543: gnome-logs: Unable to start gnome-logs due to Segmentation fault

2020-01-14 Thread Teodoro Coluccio 
I found a definitive "solution", for stable/testing, simply adding my user to 
the adm and sudo groups with "adduser user adm, adduser user sudo", and 
everything works correctly.

Regards
Teo

Bug#948543: gnome-logs: Unable to start gnome-logs due to Segmentation fault

2020-01-12 Thread Bernhard Übelacker 
Dear Maintainer,
I could reproduce this issue.

Upstream fixed this crash with this upstream commit:

https://gitlab.gnome.org/GNOME/gnome-logs/commit/7d0062a4ab36d457b74fe17b8d494570d4a0334b

A package build with this patch applied still crashes,
which got fixed in this upstream commit:

https://gitlab.gnome.org/GNOME/gnome-logs/commit/86ae341d6837e7b6b36bd8e0c65be0211ef37eba

With both patches applied it does not crash
(and shows no logs as expected as non-root user).

Both patches seem to be already contained in
gnome-logs 3.34.0-1 currently in testing, therefore
this issue should just affect Buster or older.

Kind regards,
Bernhard


(gdb) bt
#0  0x55a9d5e79b4f in gl_journal_update_latest_timestamp 
(journal=0x55a9d6de69e0) at ../src/gl-journal.c:98
#1  gl_journal_get_boot_time (journal=0x55a9d6de69e0, boot_match=0x0) at 
../src/gl-journal.c:127
#2  0x55a9d5e7b4c9 in gl_journal_model_get_boot_time (model=, boot_match=) at ../src/gl-journal-model.c:1158
#3  0x55a9d5e756b0 in gl_event_view_list_get_boot_time 
(view=view@entry=0x55a9d6ce53c0, boot_match=) at 
../src/gl-eventviewlist.c:402
#4  0x55a9d5e7d721 in on_category_list_changed (list=, 
pspec=, user_data=) at ../src/gl-window.c:252
#5  0x7f2ddab5fc8d in g_closure_invoke (closure=0x55a9d70b8ba0, 
return_value=0x0, n_param_values=2, param_values=0x7ffec12b7ee0, 
invocation_hint=0x7ffec12b7e60) at ../../../gobject/gclosure.c:810
...
#57 0x55a9d5e7155c in main (argc=1, argv=0x7ffec12b9858) at 
../src/gl-main.c:39
(gdb)

# Buster/stable amd64 qemu VM 2020-01-12

apt update
apt dist-upgrade

apt install systemd-coredump gnome
apt build-dep gnome-logs



mkdir /home/benutzer/source/gnome-logs/orig -p
cd/home/benutzer/source/gnome-logs/orig
apt source gnome-logs
cd 



benutzer@debian:~$ export DISPLAY=:0
benutzer@debian:~$ gnome-logs 

** (gnome-logs:3016): WARNING **: 19:13:04.073: Error retrieving the sender 
timestamps: Die angeforderte Adresse kann nicht zugewiesen werden
Speicherzugriffsfehler (Speicherabzug geschrieben)



dmesg:
[  121.990363] gnome-logs[3016]: segfault at 17fff8 ip 55a9d5e79b4f sp 
7ffec12b7cc0 error 4 in gnome-logs[55a9d5e7+e000]
[  121.990370] Code: 43 18 48 8b 3b 48 89 e6 8b 50 08 48 8b 00 83 ea 01 48 8d 
14 52 4c 8d 24 d0 e8 4d 6b ff ff 85 c0 0f 88 fd 00 00 00 48 8b 04 24 <49> 39 44 
24 10 0f 82 8e 00 00 00 48 8b 3b e8 5e 70 ff ff 85 c0 0f



root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Sun 2020-01-12 19:13:04 CET3016  1000  1000  11 present   
/usr/bin/gnome-logs



root@debian:~# coredumpctl gdb 3016
   PID: 3016 (gnome-logs)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Sun 2020-01-12 19:13:04 CET (1min 13s ago)
  Command Line: gnome-logs
Executable: /usr/bin/gnome-logs
 Control Group: /user.slice/user-1000.slice/session-5.scope
  Unit: session-5.scope
 Slice: user-1000.slice
   Session: 5
 Owner UID: 1000 (benutzer)
   Boot ID: 31e1a4dac60f43c3b142249a971244a8
Machine ID: 33f18f39d2a9438eb75b0ed52848afcd
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.gnome-logs.1000.31e1a4dac60f43c3b142249a971244a8.3016.157885278400.lz4
   Message: Process 3016 (gnome-logs) of user 1000 dumped core.

Stack trace of thread 3016:
#0  0x55a9d5e79b4f n/a (gnome-logs)
#1  0x55a9d5e7d721 n/a (gnome-logs)
#2  0x7f2ddab5fc8d g_closure_invoke (libgobject-2.0.so.0)
#3  0x7f2ddab73365 n/a (libgobject-2.0.so.0)
#4  0x7f2ddab7c2be g_signal_emit_valist 
(libgobject-2.0.so.0)
#5  0x7f2ddab7c97f g_signal_emit (libgobject-2.0.so.0)
#6  0x7f2ddab64364 n/a (libgobject-2.0.so.0)
#7  0x7f2ddab66921 g_object_notify_by_pspec 
(libgobject-2.0.so.0)
#8  0x55a9d5e72691 n/a (gnome-logs)
#9  0x7f2ddab5fc8d g_closure_invoke (libgobject-2.0.so.0)
#10 0x7f2ddab73365 n/a (libgobject-2.0.so.0)
#11 0x7f2ddab7c2be g_signal_emit_valist 
(libgobject-2.0.so.0)
#12 0x7f2ddab7c97f g_signal_emit (libgobject-2.0.so.0)
#13 0x7f2dda56f735 n/a (libgtk-3.so.0)
#14 0x7f2dda573192 n/a (libgtk-3.so.0)
#15 0x7f2dda573280 n/a (libgtk-3.so.0)
#16 0x7f2dd9aa38ee ffi_call_unix64 (libffi.so.6)
#17 0x7f2dd9aa32bf ffi_call (libffi.so.6)
#18 0x7f2ddab60906 g_cclosure_marshal_generic_va 
(libgobject-2.0.so.0)
#19 0x7f2ddab5fec6 n/a (libgobject-2.0.so.0)
#20 0x7f2ddab7c38d g_signal_emit_valist 
(libgobject-2.0.so.0)
#21 0x7f2ddab7c97f g_signal_emit (libgobject-2.0.so.0)
#22

Bug#948543: gnome-logs: Unable to start gnome-logs due to Segmentation fault

2020-01-09 Thread Teo 
Package: gnome-logs
Version: 3.30.0-2
Severity: important
Tags: upstream

Hi,
If I run gnome-logs by gui, it crashes instantly.
So I I wanted to investigate, and running it by terminal:
$ gnome-logs

** (gnome-logs:24155): WARNING **: 01:02:25.445: Error retrieving the sender
timestamps: Cannot assign requested address
Segmentation fault

But If I run it by root and not normal user, it works fine.
Finally, I'm agree that only administrator user can reads most of logs, but I
don't think that this behavior is right, rather I believe that a text field
should come out where to enter the administrator password and use it correctly.



-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-logs depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gsettings-desktop-schemas3.28.1-1
ii  libc62.28-10
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-7~deb10u1
ii  libsystemd0  241-7~deb10u2

gnome-logs recommends no packages.

gnome-logs suggests no packages.

-- no debconf information