Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1288081[details]
backtrace (abrt fails to do anything for me)
Description of problem:
When I start new gnome-session I quite often get few core dumps in my $HOME. They are all (according to file core.*) from /usr/libexec/tracker-extract, but when looking at the backtrace, it seems the crash itself is in gst-plugin-scanner run from inside tracker-extract.
I have no idea what's is the cause of this by wtay suggested that switch to using g_spawn_async_with_pipes may be the culprit.
Version-Release number of selected component (if applicable):
gstreamer1-1.10.4-2.el7.x86_64
tracker-1.10.5-4.el7.x86_64
How reproducible:
there is usually a streak (three to five or something like that) of coredumps after start of new gnome-session (evidently as tracker rechecks content of the followed directories), then it ceases to happen until tracker is rerun.
Comment 3RHEL Program Management
2021-01-15 07:38:16 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Created attachment 1288081 [details] backtrace (abrt fails to do anything for me) Description of problem: When I start new gnome-session I quite often get few core dumps in my $HOME. They are all (according to file core.*) from /usr/libexec/tracker-extract, but when looking at the backtrace, it seems the crash itself is in gst-plugin-scanner run from inside tracker-extract. I have no idea what's is the cause of this by wtay suggested that switch to using g_spawn_async_with_pipes may be the culprit. Version-Release number of selected component (if applicable): gstreamer1-1.10.4-2.el7.x86_64 tracker-1.10.5-4.el7.x86_64 How reproducible: there is usually a streak (three to five or something like that) of coredumps after start of new gnome-session (evidently as tracker rechecks content of the followed directories), then it ceases to happen until tracker is rerun.