Re: Re: Re: Re: Re: does anyone know how to calm down 'tracker-store'?

2018-11-29 Thread Patrice Duroux 
Hi,

That is done under #915042.
I hope improving a bit the output by using 'coredumpctl debug' and adding some
other debugging symbol packages.

Many thanks!

Re: Re: Re: Re: does anyone know how to calm down 'tracker-store'?

2018-11-28 Thread Reco 
Hi.

On Wed, Nov 28, 2018 at 11:03:28PM +0100, Patrice Duroux wrote:
> 
> Hi,
> Not sure to got it exactly but here is finally the 'coredumpctl info' output.
> Where to address it if needed?

Install reportbug if you haven't already.
Run 'reportbug tracker-extract'.
Copy this part of the backtrace into it:

Stack trace of thread 32070:
#0  0x7f4db09e1635 gst_video_codec_frame_ref (libgstvideo-1.0.so.0)
#1  0x7f4dae1c134e _gst_libde265_return_image (libgstde265.so)
#2  0x7f4dae1c17a5 gst_libde265_dec_handle_frame (libgstde265.so)
#3  0x7f4db09cfe4b gst_video_decoder_decode_frame (libgstvideo-1.0.so.0)
#4  0x7f4db09d2964 gst_video_decoder_chain_forward (libgstvideo-1.0.so.0)
#5  0x7f4db09d3042 gst_video_decoder_chain (libgstvideo-1.0.so.0)
#6  0x7f4db0adcc3a gst_pad_chain_data_unchecked (libgstreamer-1.0.so.0)
#7  0x7f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#8  0x7f4db08a7dfd gst_base_transform_chain (libgstbase-1.0.so.0)
#9  0x7f4db0adcc3a gst_pad_chain_data_unchecked (libgstreamer-1.0.so.0)
#10 0x7f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#11 0x7f4db088c9c8 gst_base_parse_push_frame (libgstbase-1.0.so.0)
#12 0x7f4db088da35 gst_base_parse_chain (libgstbase-1.0.so.0)
#13 0x7f4db0adcc3a gst_pad_chain_data_unchecked (libgstreamer-1.0.so.0)
#14 0x7f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#15 0x7f4daea5fa8d gst_single_queue_push_one (libgstcoreelements.so)
#16 0x7f4db0b11f41 gst_task_func (libgstreamer-1.0.so.0)
#17 0x7f4df35daad3 n/a (libglib-2.0.so.0)
#18 0x7f4df35da135 n/a (libglib-2.0.so.0)
#19 0x7f4df3501f2a start_thread (libpthread.so.0)
#20 0x7f4df3434edf __clone (libc.so.6)

This gdb output is mangled as it does not show source lines, but it
should do.

Reco

Re: Re: Re: does anyone know how to calm down 'tracker-store'?

2018-11-28 Thread Reco 
Hi.

On Wed, Nov 28, 2018 at 10:20:22PM +0100, Patrice Duroux wrote:
> root@hp-dark:/var/lib/systemd/coredump# gdb 
> core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.154343689200

It's always 'gdb  '.

Reco

Re: Re: Re: Re: does anyone know how to calm down 'tracker-store'?

2018-11-28 Thread Patrice Duroux 

Hi,
Not sure to got it exactly but here is finally the 'coredumpctl info' output.
Where to address it if needed?
Thanks,
Patrice


   PID: 32028 (tracker-extract)
   UID: 1000 (patrice)
   GID: 1000 (patrice)
Signal: 11 (SEGV)
 Timestamp: Wed 2018-11-28 22:54:42 CET (5min ago)
  Command Line: /usr/lib/tracker/tracker-extract
Executable: /usr/lib/tracker/tracker-extract
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/tracker-extract.service
  Unit: user@1000.service
 User Unit: tracker-extract.service
 Slice: user-1000.slice
 Owner UID: 1000 (patrice)
   Boot ID: 2b431ca216e346b9a2451932baa8be23
Machine ID: 7b96703962d14b21b365984860adb794
  Hostname: hp-dark
   Storage: 
/var/lib/systemd/coredump/core.tracker-extract.1000.2b431ca216e346b9a2451932baa8be23.32028.154344208200.lz4
   Message: Process 32028 (tracker-extract) of user 1000 dumped core.

Stack trace of thread 32070:
#0  0x7f4db09e1635 gst_video_codec_frame_ref 
(libgstvideo-1.0.so.0)
#1  0x7f4dae1c134e _gst_libde265_return_image 
(libgstde265.so)
#2  0x7f4dae1c17a5 gst_libde265_dec_handle_frame 
(libgstde265.so)
#3  0x7f4db09cfe4b gst_video_decoder_decode_frame 
(libgstvideo-1.0.so.0)
#4  0x7f4db09d2964 gst_video_decoder_chain_forward 
(libgstvideo-1.0.so.0)
#5  0x7f4db09d3042 gst_video_decoder_chain 
(libgstvideo-1.0.so.0)
#6  0x7f4db0adcc3a gst_pad_chain_data_unchecked 
(libgstreamer-1.0.so.0)
#7  0x7f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#8  0x7f4db08a7dfd gst_base_transform_chain 
(libgstbase-1.0.so.0)
#9  0x7f4db0adcc3a gst_pad_chain_data_unchecked 
(libgstreamer-1.0.so.0)
#10 0x7f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#11 0x7f4db088c9c8 gst_base_parse_push_frame 
(libgstbase-1.0.so.0)
#12 0x7f4db088da35 gst_base_parse_chain 
(libgstbase-1.0.so.0)
#13 0x7f4db0adcc3a gst_pad_chain_data_unchecked 
(libgstreamer-1.0.so.0)
#14 0x7f4db0ae4ed2 gst_pad_push (libgstreamer-1.0.so.0)
#15 0x7f4daea5fa8d gst_single_queue_push_one 
(libgstcoreelements.so)
#16 0x7f4db0b11f41 gst_task_func (libgstreamer-1.0.so.0)
#17 0x7f4df35daad3 n/a (libglib-2.0.so.0)
#18 0x7f4df35da135 n/a (libglib-2.0.so.0)
#19 0x7f4df3501f2a start_thread (libpthread.so.0)
#20 0x7f4df3434edf __clone (libc.so.6)

Stack trace of thread 32030:
#0  0x7f4df342a739 __GI___poll (libc.so.6)
#1  0x7f4df35b1e46 n/a (libglib-2.0.so.0)
#2  0x7f4df35b21d2 g_main_loop_run (libglib-2.0.so.0)
#3  0x7f4df37ac7b6 n/a (libgio-2.0.so.0)
#4  0x7f4df35da135 n/a (libglib-2.0.so.0)
#5  0x7f4df3501f2a start_thread (libpthread.so.0)
#6  0x7f4df3434edf __clone (libc.so.6)

Stack trace of thread 32033:
#0  0x7f4df342fa79 syscall (libc.so.6)
#1  0x7f4df35f863f g_cond_wait (libglib-2.0.so.0)
#2  0x7f4df358407b n/a (libglib-2.0.so.0)
#3  0x7f4df35daaa7 n/a (libglib-2.0.so.0)
#4  0x7f4df35da135 n/a (libglib-2.0.so.0)
#5  0x7f4df3501f2a start_thread (libpthread.so.0)
#6  0x7f4df3434edf __clone (libc.so.6)

Stack trace of thread 32028:
#0  0x7f4df342a739 __GI___poll (libc.so.6)
#1  0x7f4df35b1e46 n/a (libglib-2.0.so.0)
#2  0x7f4df35b21d2 g_main_loop_run (libglib-2.0.so.0)
#3  0x5556d54eadcb main (tracker-extract)
#4  0x7f4df335fb17 __libc_start_main (libc.so.6)
#5  0x5556d54eaeba _start (tracker-extract)

Stack trace of thread 32034:
#0  0x7f4df342fa79 syscall (libc.so.6)
#1  0x7f4df35f863f g_cond_wait (libglib-2.0.so.0)
#2  0x7f4df358407b n/a (libglib-2.0.so.0)
#3  0x7f4df35daaa7 n/a (libglib-2.0.so.0)
#4  0x7f4df35da135 n/a (libglib-2.0.so.0)
#5  0x7f4df3501f2a start_thread (libpthread.so.0)
#6  0x7f4df3434edf __clone (libc.so.6)

Stack trace of thread 32031:
#0  0x7f4df342a739 __GI___poll (libc.so.6)
#1  0x7f4df35b1e46 n/a (libglib-2.0.so.0)
#2  0x7f4df35b1f6c g_main_context_iteration 
(libglib-2.0.so.0)

Re: Re: Re: does anyone know how to calm down 'tracker-store'?

2018-11-28 Thread Patrice Duroux 


Hi again,

Then here is my current situation (after a LZ4 decompression, 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914934):

root@hp-dark:/var/lib/systemd/coredump# file 
core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.154343689200
core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.154343689200:
 ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/lib/tracker/tracker-extract', real uid: 1000, effective uid: 1000, real 
gid: 1000, effective gid: 1000, execfn: '/usr/lib/tracker/tracker-extract', 
platform: 'x86_64'
root@hp-dark:/var/lib/systemd/coredump# gdb 
core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.154343689200
GNU gdb (Debian 8.2-1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
;.
Find the GDB manual and other documentation resources online at:
;.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/var/lib/systemd/coredump/core.tracker-extract.1000.273d78802abc412f8e7a360fd7509e52.14743.154343689200":
 not in executable format: file format not recognized
(gdb) quit


I have installed:
ii  libde265-0-dbgsym:amd64 1.0.3-1+b1  
  amd64debug symbols for libde265-0
ii  libdvdcss2-dbgsym:amd64 1.4.2-1~local   
  amd64debug symbols for libdvdcss2
ii  tracker-extract-dbgsym  2.1.5-3 
  amd64debug symbols for tracker-extract

because by another way (looking at /tmp/tracker-extract-files.X) I have 
found that the error is due to a Matroska video file.
Finally I tried to look at https://wiki.debian.org/HowToGetABacktrace but it 
does not mention systemd-coredump at all, and then it is not clear when the 
need is for a user or session daemon/service debugging because in my case it is 
not explicitly launching a specific command to get the error.

Regards,
Patrice