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 1951194

Summary: [abrt] tracker: tracker_vtab_triples_init(): tracker3 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: kxra
Component: trackerAssignee: Debarshi Ray <debarshir>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: amigadave, awilliam, bcotton, cgarnach, dakingun, debarshir, igor.raits, jan.public, kparal, robatino, truls
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6a51f86e8971027caa82561d925f50ecf6532257
Whiteboard: abrt_hash:901beca233857bb4030e482c6e6f6e9a1942eaa5;VARIANT_ID=silverblue; Accepted0Day
Fixed In Version: tracker-3.1.1-2.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-23 21:03:51 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:
Bug Depends On:    
Bug Blocks: 1829024    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description kxra 2021-04-19 19:08:41 UTC
Version-Release number of selected component:
tracker-3.1.1-1.fc34

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cmdline:        /usr/libexec/tracker3/export --2to3 files-starred --keyfile
crash_function: tracker_vtab_triples_init
executable:     /usr/bin/tracker3
journald_cursor: s=45de7e50411a4e4cb10c4e67586c8222;i=6e857;b=232c41142fb24bf683d34f069e7c2813;m=5867032;t=5c042f3a0c4a8;x=3ffcc45e33e74812
kernel:         5.11.12-300.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1002

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 tracker_vtab_triples_init at ../src/libtracker-data/tracker-vtab-triples.c:631
 #1 tracker_db_interface_init_vtabs at ../src/libtracker-data/tracker-db-interface-sqlite.c:3769
 #2 tracker_db_manager_create_db_interface at ../src/libtracker-data/tracker-db-manager.c:779
 #3 init_writable_db_interface at ../src/libtracker-data/tracker-db-manager.c:924
 #4 tracker_db_manager_get_writable_db_interface at ../src/libtracker-data/tracker-db-manager.c:937
 #5 tracker_db_manager_get_metadata at ../src/libtracker-data/tracker-db-manager.c:242
 #6 tracker_db_manager_new.constprop.0 at ../src/libtracker-data/tracker-db-manager.c:603
 #7 export_2to3_with_query at ../src/tracker/tracker-export.c:391
 #8 export_2to3_run_files_starred at ../src/tracker/tracker-export.c:483
 #9 export_2to3_run at ../src/tracker/tracker-export.c:497

Comment 1 kxra 2021-04-19 19:08:44 UTC
Created attachment 1773366 [details]
File: backtrace

Comment 2 kxra 2021-04-19 19:08:45 UTC
Created attachment 1773367 [details]
File: cgroup

Comment 3 kxra 2021-04-19 19:08:45 UTC
Created attachment 1773368 [details]
File: core_backtrace

Comment 4 kxra 2021-04-19 19:08:46 UTC
Created attachment 1773369 [details]
File: cpuinfo

Comment 5 kxra 2021-04-19 19:08:47 UTC
Created attachment 1773370 [details]
File: dso_list

Comment 6 kxra 2021-04-19 19:08:47 UTC
Created attachment 1773371 [details]
File: environ

Comment 7 kxra 2021-04-19 19:08:48 UTC
Created attachment 1773372 [details]
File: exploitable

Comment 8 kxra 2021-04-19 19:08:49 UTC
Created attachment 1773373 [details]
File: limits

Comment 9 kxra 2021-04-19 19:08:50 UTC
Created attachment 1773374 [details]
File: maps

Comment 10 kxra 2021-04-19 19:08:51 UTC
Created attachment 1773375 [details]
File: mountinfo

Comment 11 kxra 2021-04-19 19:08:52 UTC
Created attachment 1773376 [details]
File: open_fds

Comment 12 kxra 2021-04-19 19:08:52 UTC
Created attachment 1773377 [details]
File: proc_pid_status

Comment 13 Kamil Páral 2021-04-22 12:15:01 UTC
Similar problem has been detected:

I upgraded from Fedora 32 to 34. This error popped up right after logging in into the upgraded system.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Nautilus.slice/dbus-:1.2-org.gnome.Nautilus
cmdline:        /usr/libexec/tracker3/export --2to3 files-starred --keyfile
crash_function: tracker_vtab_triples_init
executable:     /usr/bin/tracker3
journald_cursor: s=0b3ede3b86db494fba9fff5b341e90e6;i=29d7c;b=c8dc7cbdd7d84de68eb3fee98a1eb98a;m=1c3f791;t=5c08e6a54baef;x=725f9daa9e71f899
kernel:         5.11.12-300.fc34.x86_64
package:        tracker-3.1.1-1.fc34
reason:         tracker3 killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Kamil Páral 2021-04-22 12:17:12 UTC
Another duplicate (also from F32->F34 upgrade) is in bug 1947153.

Comment 15 Kamil Páral 2021-04-22 12:17:23 UTC
*** Bug 1947153 has been marked as a duplicate of this bug. ***

Comment 16 Kamil Páral 2021-04-22 12:19:24 UTC
I'm proposing this as a blocker due to:
"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_34_Final_Release_Criteria#SELinux_and_crash_notifications

The tracker crash notification occurs on first login after F32->F34 upgrade.

Comment 17 Kamil Páral 2021-04-22 12:57:58 UTC
Sorry, I forgot one important criterion:
"For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed."
"The upgraded system must meet all release criteria."
https://fedoraproject.org/wiki/Fedora_34_Beta_Release_Criteria#Upgrade_requirements

The combination of this one and the one from comment 16 should be enough to propose this as a blocker, if we consider "first login after install" to be the equivalent of "first login after upgrade" for upgraded systems.

Comment 18 Kamil Páral 2021-04-22 13:00:21 UTC
I've performed a completely clean F32 Workstation Live install, fully updated it, and the upgraded to F34. No other changes were performed, no new files created in home, etc. I've seen the same crash show up after upgrade. This is not specific to some user-generated content.

Comment 19 Fedora Update System 2021-04-22 16:32:18 UTC
FEDORA-2021-98f4fa2e2b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-98f4fa2e2b

Comment 20 Adam Williamson 2021-04-22 17:09:03 UTC
+7 in https://pagure.io/fedora-qa/blocker-review/issue/370 , marking as Accepted0Day. As a reminder that means the bug is a blocker, but the fix only needs to be stable by release day, it does not need to be on the media. It applies in this case as the issue is specific to upgrades, and upgrades don't use the release media; as long as the update is in the updates repo on release day, we'd be OK.

Comment 21 Fedora Update System 2021-04-22 18:25:49 UTC
FEDORA-2021-98f4fa2e2b has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-98f4fa2e2b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-98f4fa2e2b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 22 Kamil Páral 2021-04-22 20:21:06 UTC
(In reply to Fedora Update System from comment #21)
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-98f4fa2e2b

When I upgrade from F32 with this, I no longer see the crash notification.

Comment 23 Fedora Update System 2021-04-23 21:03:51 UTC
FEDORA-2021-98f4fa2e2b has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.