Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1875398
Summary: | tracker-miners randomly crashes on F33 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Rusek <drusek> |
Component: | tracker-miners | Assignee: | Kalev Lember <klember> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | debarshir, ego.cordatus, fzatlouk, gnome-sig, klember, mail |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | tracker-miners-2.3.4-2.fc33 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-09-08 17:04:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1766776 |
Description
Daniel Rusek
2020-09-03 13:36:35 UTC
The provided coredump is for tracker-extract. It seems that both tracker-miners and tracker-extract are crashing. I see that the crashing thread ends with calling 'statx' -- I assume this must be due to glib switching to statx instead of stat in F33 and that broke tracker sandboxing (it needs to whitelist statx, if my theory is right). Any chance you could file this as an issue upstream against tracker or tracker-miners? Great, thanks! I left a comment there too. OK, it's fixed in git upstream now and I've backported the fix to tracker-miners-2.3.4-2.fc33. I'll also nominate this as a Beta FE as it would be nice to have a non-crashing tracker on the install media. The fix should be very low risk as it just adds the statx syscall to the whitelist (new glib2 version that's already in F33 uses statx so tracker needs to whitelist this in its sandbox to not crash). FEDORA-2020-6138a5e1b2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6138a5e1b2 FEDORA-2020-6138a5e1b2 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-6138a5e1b2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6138a5e1b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Setting as AcceptedFreezeException per voting: https://pagure.io/fedora-qa/blocker-review/issue/66 Setting as Verified as tracker-miners crashing stopped after the update. FEDORA-2020-6138a5e1b2 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. I've reported this 2020-08-27 but was no reaction at all https://bugzilla.redhat.com/show_bug.cgi?id=1873196 Anyway no more crashes since last update. *** Bug 1873196 has been marked as a duplicate of this bug. *** Sorry Artem, sometimes I miss things in bugzilla noise. Feel free to poke me on irc (or send an email) if there's something urgent that needs attention in GNOME packages. No prob. :) Same here with bugzilla and often missing important notifications. Good to know the next time. This was not urgent bug but annoying in same time since i've updated to f33 everywhere. Thanks Kalev! |