Bug 1538786

Summary: [abrt] tracker-miners: g_pattern_match(): tracker-miner-fs killed by SIGABRT
Product: [Fedora] Fedora Reporter: George R. Goffe <grgoffe>
Component: tracker-minersAssignee: Kalev Lember <klember>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: cnangel, csiterallat, frankivax, jreiser, klember, rychlikjobs, sudmann, thierry.brichler
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9040f21e7c1e5d9d9d7bbcb451fc44a1fe83f728
Whiteboard: abrt_hash:1e2fb318ad49f098648e074436710b11214f0fd7;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 19:23:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description George R. Goffe 2018-01-25 20:19:36 UTC
Description of problem:
This problem occured within 5 minutes of a system reboot and subsequent start of the KDE window manager.

Version-Release number of selected component:
tracker-miners-2.0.3-2.fc28

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: g_pattern_match
executable:     /usr/libexec/tracker-miner-fs
journald_cursor: s=10116d5a8f5245e89e802c32d725012b;i=37e1bc;b=0a955e197c6a42e88c390837b3fbb8b7;m=1c40a96f;t=5639e442d7f6d;x=8c64b8fdd1a1e54b
kernel:         4.15.0-0.rc8.git0.1.fc28.x86_64
rootdir:        /
runlevel:       N 3
type:           CCpp
uid:            0

Potential duplicate: bug 1520872

Comment 1 George R. Goffe 2018-01-25 20:19:40 UTC
Created attachment 1386277 [details]
File: backtrace

Comment 2 George R. Goffe 2018-01-25 20:19:41 UTC
Created attachment 1386278 [details]
File: cgroup

Comment 3 George R. Goffe 2018-01-25 20:19:42 UTC
Created attachment 1386279 [details]
File: core_backtrace

Comment 4 George R. Goffe 2018-01-25 20:19:43 UTC
Created attachment 1386280 [details]
File: cpuinfo

Comment 5 George R. Goffe 2018-01-25 20:19:44 UTC
Created attachment 1386281 [details]
File: dso_list

Comment 6 George R. Goffe 2018-01-25 20:19:45 UTC
Created attachment 1386282 [details]
File: environ

Comment 7 George R. Goffe 2018-01-25 20:19:46 UTC
Created attachment 1386283 [details]
File: limits

Comment 8 George R. Goffe 2018-01-25 20:19:47 UTC
Created attachment 1386284 [details]
File: maps

Comment 9 George R. Goffe 2018-01-25 20:19:48 UTC
Created attachment 1386285 [details]
File: mountinfo

Comment 10 George R. Goffe 2018-01-25 20:19:48 UTC
Created attachment 1386286 [details]
File: open_fds

Comment 11 George R. Goffe 2018-01-25 20:19:49 UTC
Created attachment 1386287 [details]
File: proc_pid_status

Comment 12 Fedora End Of Life 2018-02-20 15:32:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 13 John Reiser 2018-06-10 03:51:57 UTC
Similar problem has been detected:

Installed Fedora 28 Live Workstation.  Changed my home directory to be a symlink to a directory on another drive.
Rebooted and logged in.  In a couple iminutes, got a notification that tracker-miners had crashed.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: g_pattern_match
executable:     /usr/libexec/tracker-miner-fs
journald_cursor: s=8bd0b0ff0e544ad288ad1aed7bb33b2b;i=324b;b=2c0d661155bb46f5b3c2844eccb333bd;m=1f221491;t=56e41545be17e;x=2d75e1dea05e25cd
kernel:         4.16.14-300.fc28.x86_64
package:        tracker-miners-2.0.4-3.fc28
reason:         tracker-miner-fs killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 rychlikjobs 2018-09-27 11:31:00 UTC
Similar problem has been detected:

It happened after an attempted soft reboot. The system failed to soft reboot.
After a hard reboot, kernel crash was reported. 

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: g_pattern_match
executable:     /usr/libexec/tracker-miner-fs
journald_cursor: s=97db83a54691474fba5d1899c4c76ffc;i=43a039;b=95ba20b28dcf4916a7b1688d0fb3d14e;m=56b800bcd;t=576ca5b33fef6;x=2c6ed9ce2486f861
kernel:         4.18.9-200.fc28.x86_64
package:        tracker-miners-2.1.4-1.fc28
reason:         tracker-miner-fs killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 15 rychlikjobs 2018-10-26 23:27:10 UTC
Similar problem has been detected:

Using Remote Desktop/VNC

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: g_pattern_match
executable:     /usr/libexec/tracker-miner-fs
journald_cursor: s=4c5f44a6ba694666842c9fa6cdfbc2fe;i=dfef1;b=1580088b04d54f7fa96e5fcbc259b660;m=2f2b1b5;t=57886da126b61;x=153d4dac8e1276a6
kernel:         4.18.14-200.fc28.x86_64
package:        tracker-miners-2.1.4-1.fc28
reason:         tracker-miner-fs killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 16 frankivax 2019-03-05 02:29:14 UTC
Similar problem has been detected:

simplemente sale este mensaje que el minero no funciona al encender la maquina

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: g_pattern_match
executable:     /usr/libexec/tracker-miner-fs
journald_cursor: s=ed7e11ee9be04aee9fc95be94fa274c2;i=a2e;b=e7a33b9e86974b989be93b7e6a780b9a;m=7d7da1e;t=582d745c14264;x=d72c07c453892245
kernel:         4.20.11-100.fc28.x86_64
package:        tracker-miners-2.1.4-1.fc28
reason:         tracker-miner-fs killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 17 Ben Cotton 2019-05-02 19:48:55 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 18 Mars 2019-05-03 14:09:44 UTC
I can't close Auto-reports?
I used F29 and now F30, i cant test it.

Comment 19 George R. Goffe 2019-05-03 17:15:19 UTC
Mars,

Do you need me to do something?

George...

Comment 20 Ben Cotton 2019-05-28 19:23:34 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.