Bug 2066703

Summary: tracker-extract-3 killed by SIGSYS
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: tracker-minersAssignee: Kalev Lember <klember>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: awilliam, cgarnach, debarshir, gnome-sig, klember, leftmostcat, lnie, robatino, teohhanhui
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/261765/
Whiteboard: AcceptedBlocker
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-29 18:57:30 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: 1953785    
Attachments:
Description Flags
backtrace
none
core_backtrace
none
coredump.xz
none
system journal
none
rpm -qa output
none
abrt-crash-dir.txz
none
journal from the machine where tracker-miners crashed 124 times none

Description Kamil Páral 2022-03-22 10:53:28 UTC
Description of problem:
tracker-miners sometimes crashes after a clean Workstation install. Shortly (1-2 minutes) after the first login into the installed system, a crash notification pops up. Once I saw it while working with gnome-software, once I saw it once working with dnf. It might be related, but I'm not sure.

This crash is already reported 5 times when you open the issue in abrt. It seems that each time it happens, 5 more crashes occur. On affected systems, I've seen the crash repeat on re-login (at least once).

This doesn't happen with each install. But I've already seen it multiple times.

Abrt analytics link:
https://retrace.fedoraproject.org/faf/reports/261765/

Abrt doesn't allow me to report this bug (it says "Crash thread not found" and "'post_report' exited with 1"), so I must report this manually. Attached are files from the abrt crash directory.


Version-Release number of selected component (if applicable):
tracker-miners-3.3.0~rc-1.fc36.x86_64

How reproducible:
often, not always

Steps to Reproduce:
1. Install F36 Workstation Live Beta RC1.2 (into a VM, in my case)
2. Boot the installed system, complete the initial setup
3. Wait 1-2 minutes, see abrt notification about tracker-miners crashing (sometimes)

Comment 1 Kamil Páral 2022-03-22 10:55:36 UTC
Created attachment 1867424 [details]
backtrace

Comment 2 Kamil Páral 2022-03-22 10:55:40 UTC
Created attachment 1867425 [details]
core_backtrace

Comment 3 Kamil Páral 2022-03-22 10:56:49 UTC
Created attachment 1867426 [details]
coredump.xz

Comment 4 Kamil Páral 2022-03-22 10:57:24 UTC
Created attachment 1867427 [details]
system journal

Comment 5 Kamil Páral 2022-03-22 10:57:30 UTC
Created attachment 1867428 [details]
rpm -qa output

Comment 6 Kamil Páral 2022-03-22 11:00:28 UTC
Created attachment 1867429 [details]
abrt-crash-dir.txz

Comment 7 Kamil Páral 2022-03-22 11:02:11 UTC
There's another report from Lili in bug 2063056 (merging as a duplicate).

Comment 8 Kamil Páral 2022-03-22 11:03:01 UTC
*** Bug 2063056 has been marked as a duplicate of this bug. ***

Comment 9 Kamil Páral 2022-03-22 11:05:16 UTC
Proposing as a Final blocker:
"There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop. "
https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#SELinux_and_crash_notifications

It seems to happen frequently enough to not be considered a random failure.

Comment 10 lnie 2022-03-22 13:47:15 UTC
Do  default installation with Fedora-Workstation-Live-x86_64-36_Beta-1.4.iso , after install available updates using gnome-software,reboot and login to the system,it crashed 124 times,
and there are 20 crashes on another machine where I tried to reproduce the 124 crash.

Comment 11 lnie 2022-03-22 13:50:01 UTC
Created attachment 1867499 [details]
journal from the machine where tracker-miners crashed 124 times

Comment 12 Adam Williamson 2022-03-28 15:00:31 UTC
+4 in https://pagure.io/fedora-qa/blocker-review/issue/684 , marking accepted.

Comment 13 Adam Williamson 2022-03-28 17:48:00 UTC
This probably needs reporting upstream at https://gitlab.gnome.org/GNOME/tracker-miners/-/issues . It'd be great if we could get a proper backtrace also. I'll see if I can reproduce it in a VM.

Comment 14 Adam Williamson 2022-03-28 17:48:59 UTC
garnacho says https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/386 probably fixes this.

Comment 15 Fedora Update System 2022-03-28 17:57:56 UTC
FEDORA-2022-a69718b1e1 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a69718b1e1

Comment 16 Adam Williamson 2022-03-28 17:59:53 UTC
So that fix was in 3.3.0, which means it's in the current GNOME mega-update that's pending stable, we should test and see if it's fixed there. A way to test would be to chroot into the installed system after install and update tracker-miners before first booting into the installed system.

Comment 17 Fedora Update System 2022-03-29 00:17:08 UTC
FEDORA-2022-a69718b1e1 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 lnie 2022-03-29 07:02:42 UTC
Checked 3.3.0,didn't see this crash anymore.

Comment 19 Adam Williamson 2022-03-29 18:57:30 UTC
OK, let's close this for now. If anyone still sees the crash, we can reopen. Thanks lnie!

Comment 20 lnie 2022-03-30 03:19:06 UTC
Nope,I bet others won't see this crash anymore either,I checked every cases where I saw the crash:I chroot into the installed system to install 3.3.0 before first boot, I waited 2 minutes after g-i-s ,then played with Maps and Software for a while,and then downloaded the Updates,install&restart the system,and then played with Maps and Software for a while again.

Comment 21 Sean Burke 2022-11-07 05:57:58 UTC
I'm experiencing a reproducible crash with this description when opening gnome-books 40.0-4.fc36. I have tracker-miners 3.3.1-1.fc36 installed. Should I open a new bug?