User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101
Firefox/50.0
Build Identifier:
After updating openSUSE Tumbleweed yesterday (12/29), I discovered that the
tracker-extract process was cyclically failing and causing core dumps to be
generated through systemd-coredump.
The issue does not start until I log into the GNOME desktop (Wayland and/or
X.org), and is not present if I log into the IceWM desktop.
When I log into the GNOME desktop, I quickly hear my laptop fans kick into high
gear, and I can see several (6-8) systemd-coredump processes running to
generate the core dump files. I can see the new core-dump files being actively
created in /var/lib/systemd/coredump/
When I first noticed this issue, I was using the packman-essentials repo for
codes. I disabled the packman-essentials repo and reverted to the official
Tumbleweed versions, and the issue is still present.
I did a little debugging with the systemd coredumpctl utility, and the error
seems to be caused by a bad system call in glibc socket(). Here's the gdb
output and backtrace:
Core was generated by `/usr/lib/tracker-extract'.
Program terminated with signal SIGSYS, Bad system call.
#0 0x00007f34356a1587 in socket () at ../sysdeps/unix/syscall-template.S:84
84 ../sysdeps/unix/syscall-template.S: No such file or directory.
[Current thread is 1 (Thread 0x7f3413b15700 (LWP 2777))]
(gdb) bt
#0 0x00007f34356a1587 in socket () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f342fb0d304 in udev_monitor_new_from_netlink_fd
(udev=0x7f340c379be0, name=<optimized out>, fd=-1) at
src/libudev/libudev-monitor.c:207
#2 0x00007f343178a3a2 in () at /usr/lib64/libgudev-1.0.so.0
#3 0x00007f3435e9f0d7 in () at /usr/lib64/libgobject-2.0.so.0
#4 0x00007f3435ea0a6e in g_object_new_valist () at
/usr/lib64/libgobject-2.0.so.0
#5 0x00007f3435ea0d11 in g_object_new () at /usr/lib64/libgobject-2.0.so.0
#6 0x00007f343178a537 in g_udev_client_new () at /usr/lib64/libgudev-1.0.so.0
#7 0x00007f33fe030d3a in () at /usr/lib64/gstreamer-1.0/libgstvideo4linux2.so
#8 0x00007f33fe00ea53 in () at /usr/lib64/gstreamer-1.0/libgstvideo4linux2.so
#9 0x00007f34207d10f7 in () at /usr/lib64/libgstreamer-1.0.so.0
#10 0x00007f34207d3068 in () at /usr/lib64/libgstreamer-1.0.so.0
#11 0x00007f34207dfc0e in () at /usr/lib64/libgstreamer-1.0.so.0
#12 0x00007f34207e0d01 in () at /usr/lib64/libgstreamer-1.0.so.0
#13 0x00007f34207e0ed6 in () at /usr/lib64/libgstreamer-1.0.so.0
#14 0x00007f34207e2b24 in gst_update_registry () at
/usr/lib64/libgstreamer-1.0.so.0
#15 0x00007f342077d41e in () at /usr/lib64/libgstreamer-1.0.so.0
#16 0x00007f3435bcc988 in g_option_context_parse () at
/usr/lib64/libglib-2.0.so.0
#17 0x00007f342077ddef in gst_init_check () at /usr/lib64/libgstreamer-1.0.so.0
#18 0x00007f342077de44 in gst_init () at /usr/lib64/libgstreamer-1.0.so.0
#19 0x00007f342110434b in tracker_extract_gstreamer
(uri=uri@entry=0x7f340c007930
"file:///home/bwilson3013/Music/moe_/Sticks%20and%20Stones/02%20Sticks%20and%20Stones.m4a",
info=info@entry=0x7f3418003060, type=type@entry=EXTRACT_MIME_AUDIO) at
tracker-extract-gstreamer.c:1341
#20 0x00007f3421105b59 in tracker_extract_get_metadata (info=0x7f3418003060) at
tracker-extract-gstreamer.c:1470
#21 0x000000000040ba86 in get_file_metadata (task=task@entry=0x17ad590,
info_out=info_out@entry=0x7f3413b14d10) at tracker-extract.c:326
#22 0x000000000040bb53 in get_metadata (task=0x17ad590) at
tracker-extract.c:510
#23 0x000000000040bbb0 in single_thread_get_metadata (queue=0x1932510) at
tracker-extract.c:538
#24 0x00007f3435be81c5 in () at /usr/lib64/libglib-2.0.so.0
#25 0x00007f343595d454 in start_thread (arg=0x7f3413b15700) at
pthread_create.c:333
#26 0x00007f34356a037f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105
Reproducible: Always
Steps to Reproduce:
1. Turn on computer
2. Log into GNOME
3. See systemd-coredump processes running
Actual Results:
New core dump files for /usr/lib/tracker-extract appear in
/var/lib/systemd/coredump/
Expected Results:
GNOME tracker (or udev) should not be generating core dumps