[Bug 1017652] New: tracker-extract process generating core dumps through udev bad system call to socket()
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652 Bug ID: 1017652 Summary: tracker-extract process generating core dumps through udev bad system call to socket() Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: bwilson3013@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- 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 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c1
--- Comment #1 from Brett Wilson
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Brett Wilson
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Peter Linnell
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c2
Karl Ove Hufthammer
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c3
Fabien Lo Ricco
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c4
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c5
--- Comment #5 from Brett Wilson
From the command line, the file command reports that the music files are "ISO Media, Apple iTunes ALAC/AAC-LC (.M4A) Audio"
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c6
--- Comment #6 from Karl Ove Hufthammer
The sad thing is that tracker is only suffering from underlying libs that generally crash.
So in any case, we need sample files that tracker tries to extract and fails. Then we can identify the library causing the failure and fix them directly
I’ll try to submit a sample file, but I don’t how to find out *which* files make the library crash. (Though I think there are many such files, since tracker-extract generates coredumps *countinously* if I don’t disable it.) I have kept a few coredump files, but they are *huge* (e.g. several hundred MiB each). Are they of any use? How can I inspect them to figure out which file(s) caused the crashes? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c7
--- Comment #7 from Dominique Leuenberger
I’ll try to submit a sample file, but I don’t how to find out *which* files make the library crash. (Though I think there are many such files, since tracker-extract generates coredumps *countinously* if I don’t disable it.)
I have kept a few coredump files, but they are *huge* (e.g. several hundred MiB each). Are they of any use? How can I inspect them to figure out which file(s) caused the crashes?
Best is to extract a back trace directly on your machine; try with: coredumpctl gdb /usr/lib/tracker-extract then at the (gdb) prompt type "bt full"; if there are mentions of missing -debuginfo packages, please install them and reproduce the coredumpctl gdb command (there should be no '???' in the resulting dump. With this it might be possible to find some clues where it's happening. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c8
--- Comment #8 from Karl Ove Hufthammer
Best is to extract a back trace directly on your machine; try with:
coredumpctl gdb /usr/lib/tracker-extract
then at the (gdb) prompt type "bt full"; if there are mentions of missing -debuginfo packages, please install them and reproduce the coredumpctl gdb command (there should be no '???' in the resulting dump.
With this it might be possible to find some clues where it's happening.
coredumpctl couldn’t find any coredump files, but running gdb manually I managed to extract the information. First, tracker 1.10.4 became available just a moment ago, and that seemed to have cured most of the crashes. But running gdb on the *old* (tracker 1.10.3), I found this: #0 0x00007fabff6e3eb7 in munlock () at /lib64/libc.so.6 #1 0x00007fabbc93611f in delete_fluid_defsfont () at /usr/lib64/libfluidsynth.so.1 #2 0x00007fabbc936256 in fluid_defsfont_sfont_delete () at /usr/lib64/libfluidsynth.so.1 #3 0x00007fabbc94b7d2 in fluid_synth_sfont_unref () at /usr/lib64/libfluidsynth.so.1 #4 0x00007fabbc950ce0 in fluid_synth_sfunload () at /usr/lib64/libfluidsynth.so.1 #5 0x00007fabbcbee271 in () at /usr/lib64/gstreamer-1.0/libgstfluidsynthmidi.so #6 0x00007fabce3ed90e in gst_element_change_state () at /usr/lib64/libgstreamer-1.0.so.0 #7 0x00007fabce3ee07f in () at /usr/lib64/libgstreamer-1.0.so.0 libfluidsynth is a MIDI library, and the crashes seemed to be releated to extracting metadata from MIDI files (.mid files). With the new 1.10.4 version it doesn’t crash on MIDI files (or perhaps it’s just indexed all of them?), but I still get crashes, now on MP3 files, referencing the libmediaart library: #0 0x00007f4b3f6b6e97 in unlink () at /lib64/libc.so.6 #1 0x00007f4b4034af7b in () at /usr/lib64/libmediaart-2.0.so.0 #2 0x00007f4b4034cbf8 in media_art_process_file () at /usr/lib64/libmediaart-2.0.so.0 #3 0x00007f4a80095dc9 in tracker_extract_get_metadata (info=0x7f4b20033e60) at tracker-extract-mp3.c:2584 media_art_process = <optimized out> error = 0x7f4a90437390 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c9
--- Comment #9 from Karl Ove Hufthammer
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c10
--- Comment #10 from Dominique Leuenberger
Probably related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848842
Likely - and that one seems to have sorted with 0.4 The new one for mp3
#0 0x00007f4b3f6b6e97 in unlink () at /lib64/libc.so.6 #1 0x00007f4b4034af7b in () at /usr/lib64/libmediaart-2.0.so.0 #2 0x00007f4b4034cbf8 in media_art_process_file () at /usr/lib64/libmediaart-2.0.so.0 #3 0x00007f4a80095dc9 in tracker_extract_get_metadata (info=0x7f4b20033e60) at tracker-extract-mp3.c:2584 media_art_process = <optimized out> error = 0x7f4a90437390
That one MIGHT be related to the fix for libmediaart2 we just prepared - possible the mp3 has not ARTIST set? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c11
Karl Ove Hufthammer
(In reply to Karl Ove Hufthammer from comment #9)
Probably related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848842
Likely - and that one seems to have sorted with 0.4
On Debian they disabled libmediaart completely, and that doesn’t seem to be done upstream (yet), AFAICS: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=848842;filename=0001...
#3 0x00007f4a80095dc9 in tracker_extract_get_metadata (info=0x7f4b20033e60) at tracker-extract-mp3.c:2584 media_art_process = <optimized out> error = 0x7f4a90437390
That one MIGHT be related to the fix for libmediaart2 we just prepared - possible the mp3 has not ARTIST set?
The MP3 file *does* have the ARTIST field set. Here’s one of the files that resulted in coredumps on my system: http://static1.squarespace.com/static/50844bb5c4aa1a31c6526430/t/551cc024e4b... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c12
Bjørn Lie
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c13
--- Comment #13 from Bjørn Lie
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c14
--- Comment #14 from Bjørn Lie
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c15
--- Comment #15 from Brett Wilson
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c16
--- Comment #16 from Brett Wilson
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c17
--- Comment #17 from Brett Wilson
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Peter Linnell
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c18
Eric Schirra
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Frederic Crozat
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Shane Wims
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c19
Sébastien POHER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c20
--- Comment #20 from Sébastien POHER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Peter Keller
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c21
--- Comment #21 from Peter Keller
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c22
--- Comment #22 from Peter Keller
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c23
Vinicius B. Rodrigues
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c24
--- Comment #24 from Vinicius B. Rodrigues
I'm having the same problem in Leap, here you can see my coredumpctl gdb tracker-extract http://susepaste.org/12359644
The new one: http://susepaste.org/12359644 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Tyler McClanahan
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c25
--- Comment #25 from Tyler McClanahan
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c26
--- Comment #26 from Adrien Plazas
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c27
--- Comment #27 from Adrien Plazas
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c28
--- Comment #28 from Dominique Leuenberger
What seems to be taking all my CPU is `systemd-coredump` though, and by running coredumpctl I see many instances of tracker-extract and only that.
yes, hence theneed to fix tracker / the libs it used that are crashing (one seems to be libmediaart, which we should likely update to the Version in TW); the 2nd trace crashes in v4l/gst - that might be even nastier -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c29
--- Comment #29 from Adrien Plazas
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c30
--- Comment #30 from Dominique Leuenberger
I updated Tracker on 42.3 from 1.8.3 to 1.12.3 (the current once on Tumbleweed) and I couldn't reproduce the bug anymore. Would updating Tracker be enough, is it acceptable to do so?
lookup423 ^tracker: tracker: SUSE:SLE-12-SP3:GA
Good luck :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c31
--- Comment #31 from Adrien Plazas
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c32
Malcolm Lewis
I produced a patch which seems to work just fine for me: https://build.opensuse.org/package/show/home:aplazas:branches:openSUSE:Leap: 42.3:Update/tracker
Feel free to double-check it before I submit it. Hi Just an observation, I re-installed 42.3 and unable to duplicate without the ~/Music directory (and others) as softlinks to a separate partition/folder when copying in mp3's. These are just the default directories in my ~/.
I also note that it doesn't occur on SLES/SLED 12 SP3 (with the same softlinks and files) as this does not included the grilo-plugin-tracker package. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Johannes Thumshirn
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Andreas Färber
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c33
--- Comment #33 from Andreas Färber
I produced a patch which seems to work just fine for me: https://build.opensuse.org/package/show/home:aplazas:branches:openSUSE:Leap: 42.3:Update/tracker
Feel free to double-check it before I submit it.
I've tested your above "tracker" package, and it appears to fix crashes on 42.3. If there's no other problems with it, please submit it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c35
Andreas Stieger
lookup423 ^tracker: tracker: SUSE:SLE-12-SP3:GA
Good luck :)
What is that supposed to mean? The fix is currently submitted to SLE maintenance. Please contact maintenance for any prioritization.
https://build.opensuse.org/request/show/532678 42.3 / tracker
I have declined it for Leap maintenance at this point in expectation of a SLE maintenance update. If something else is required, please reopen the request and clearly indicate so. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c36
David Deaven
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c37
--- Comment #37 from Scott Reeves
(In reply to Dominique Leuenberger from comment #30)
lookup423 ^tracker: tracker: SUSE:SLE-12-SP3:GA
Good luck :)
What is that supposed to mean?
The way I read that is that Adrien was asking if we could do a version update and Dominique pointed out that tracker comes from SLE where it's much harder to do that instead of backporting the patch.
The fix is currently submitted to SLE maintenance. Please contact maintenance for any prioritization.
https://build.opensuse.org/request/show/532678 42.3 / tracker
I have declined it for Leap maintenance at this point in expectation of a SLE maintenance update. If something else is required, please reopen the request and clearly indicate so.
Adrien - it looks like you forgot to run pre_checkin.sh so the tracker and tracker-extras spec files don't match (patch2 is missing). In this case I don't think it makes any difference but we want to keep the spec files in sync. Could you resubmit this to Devel:Desktop. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c38
--- Comment #38 from Adrien Plazas
The fix is currently submitted to SLE maintenance. Please contact maintenance for any prioritization.
https://build.opensuse.org/request/show/532678 42.3 / tracker
I have declined it for Leap maintenance at this point in expectation of a SLE maintenance update. If something else is required, please reopen the request and clearly indicate so.
Adrien - it looks like you forgot to run pre_checkin.sh so the tracker and tracker-extras spec files don't match (patch2 is missing). In this case I don't think it makes any difference but we want to keep the spec files in sync. Could you resubmit this to Devel:Desktop.
Good catch! It's fixed and merged on Devel:Desktop:SLE12:SP3. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Sal Luna
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Frederic Crozat
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Gustavo Pichorim Boiko
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c43
Ailin Nemui
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c44
--- Comment #44 from Ailin Nemui
any update here? this is gravely affecting the usability of my openSUSE Leap 42.3
(gdb) bt #0 0x00007fab10e93ab7 in symlink () at /lib64/libc.so.6 #1 0x00007fab11b23c52 in media_art_process_file () at /usr/lib64/libmediaart-2.0.so.0 #2 0x00007faae8a19381 in tracker_extract_get_metadata (info=0x7faae00095e0) at tracker-extract-mp3.c:2714 #3 0x000000000040bc9e in get_file_metadata (task=task@entry=0x24a1700, info_out=info_out@entry=0x7faae8a11d98) at tracker-extract.c:332 #4 0x000000000040bdb5 in get_metadata (task=0x24a1700) at tracker-extract.c:532 #5 0x000000000040be20 in single_thread_get_metadata (queue=0x24a1ee0) at tracker-extract.c:560 #6 0x00007fab113e3a85 in () at /usr/lib64/libglib-2.0.so.0 #7 0x00007fab1115e724 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fab10e9ec1d in clone () at /lib64/libc.so.6 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c45
--- Comment #45 from Peter Keller
any update here? this is gravely affecting the usability of my openSUSE Leap 42.3
I agree: it is really annoying that this patch is taking so long to appear. I hope that we aren't going to have to wait until openSUSE 15 to get it. I guess that the problem is that relatively few people happen to have files that trigger the bug, so backporting it into 42.3 isn't seen as a priority. I only see this for one user on one machine myself. A mitigation is to execute the command 'tracker daemon -k' after logging in, but that is hardly a fix. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c46
--- Comment #46 from Peter Keller
any update here? this is gravely affecting the usability of my openSUSE Leap 42.3
I agree: it is really annoying that this patch is taking so long to appear. I hope that we aren't going to have to wait until openSUSE 15 to get it. I guess that the problem is that relatively few people happen to have files that trigger the bug, so backporting it into 42.3 isn't seen as a priority. I only see this for one user on one machine myself. A mitigation is to execute the command 'tracker daemon -k' after logging in, but that is hardly a fix. P.S. Am I right in thinking that I am the only person who has voted for this bug? If more people voted for it, that might help. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c47
--- Comment #47 from Ailin Nemui
(In reply to Dominique Leuenberger from comment #30)
https://build.opensuse.org/request/show/532678 42.3 / tracker
I tried to test this and it didn't seem to fix the problem, still crashing -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c48
--- Comment #48 from Andreas Stieger
I agree: it is really annoying that this patch is taking so long to appear. I hope that we aren't going to have to wait until openSUSE 15 to get it. I guess that the problem is that relatively few people happen to have files that trigger the bug, so backporting it into 42.3 isn't seen as a priority. I only see this for one user on one machine myself.
It will be released once the fix has been verified. So far this is not the case, see comment #47.
P.S. Am I right in thinking that I am the only person who has voted for this bug? If more people voted for it, that might help.
Not really. The determining factor would be for a fix to be available. In this case, via SLE maintenance which will then quickly be imported into Leap updates. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Hans van den Heuvel
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c49
Scott Reeves
It will be released once the fix has been verified. So far this is not the case, see comment #47.
Antonio - can you help diagnose comment #47 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c50
Christopher HORLER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c51
--- Comment #51 from Christopher HORLER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c52
--- Comment #52 from Christopher HORLER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c53
--- Comment #53 from Christopher HORLER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c54
--- Comment #54 from Christopher HORLER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c55
--- Comment #55 from Christopher HORLER
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Alexey Svistunov
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
Alexey Svistunov
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652
http://bugzilla.opensuse.org/show_bug.cgi?id=1017652#c64
Dominique Leuenberger
openSUSE-RU-2019:1238-1: An update that has two recommended fixes can now be installed.
Category: recommended (low) Bug References: 1017652,1038829 CVE References: Sources used: openSUSE Leap 42.3 (src): tracker-1.8.3-2.3.1, tracker-extras-1.8.3-2.3.1
That actually all seems released - and from what I get from the feedbacks, they were helping at the time -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com