Bug 972478

Summary: Crash in gvdb_table_lookup called from tracker-ontologies.c
Product: [Fedora] Fedora Reporter: Gerhard Dekker <gerhard.dekker>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: dakingun, debarshir, iliketurtlesbro, kaka.in, rhbugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c1bd9af8afd7599c071804db0cd753cfcb160732
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 02:48:03 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Gerhard Dekker 2013-06-09 17:11:17 UTC
Version-Release number of selected component:
tracker-0.16.1-1.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: gvdb_table_lookup
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.9.4-301.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gvdb_table_lookup at gvdb-reader.c:265
 #1 gvdb_table_get_value at gvdb-reader.c:441
 #2 tracker_ontologies_get_property_value_gvdb at tracker-ontologies.c:670
 #3 tracker_property_get_domain_indexes at tracker-property.c:343
 #4 tracker_sparql_pattern_parse_object at /home/martyn/Source/tracker/src/libtracker-data/tracker-sparql-pattern.vala:1361
 #5 tracker_sparql_pattern_parse_object_list at /home/martyn/Source/tracker/src/libtracker-data/tracker-sparql-pattern.vala:581
 #6 tracker_sparql_pattern_parse_property_list_not_empty at /home/martyn/Source/tracker/src/libtracker-data/tracker-sparql-pattern.vala:617
 #7 tracker_sparql_pattern_parse_triples at /home/martyn/Source/tracker/src/libtracker-data/tracker-sparql-pattern.vala:826
 #8 tracker_sparql_pattern_translate_group_graph_pattern at /home/martyn/Source/tracker/src/libtracker-data/tracker-sparql-pattern.vala:958
 #9 tracker_sparql_pattern_translate_select at /home/martyn/Source/tracker/src/libtracker-data/tracker-sparql-pattern.vala:278

Potential duplicate: bug 768770

Comment 1 Gerhard Dekker 2013-06-09 17:11:21 UTC
Created attachment 758868 [details]
File: backtrace

Comment 2 Gerhard Dekker 2013-06-09 17:11:24 UTC
Created attachment 758869 [details]
File: cgroup

Comment 3 Gerhard Dekker 2013-06-09 17:11:27 UTC
Created attachment 758870 [details]
File: core_backtrace

Comment 4 Gerhard Dekker 2013-06-09 17:11:30 UTC
Created attachment 758871 [details]
File: dso_list

Comment 5 Gerhard Dekker 2013-06-09 17:11:33 UTC
Created attachment 758872 [details]
File: environ

Comment 6 Gerhard Dekker 2013-06-09 17:11:39 UTC
Created attachment 758873 [details]
File: limits

Comment 7 Gerhard Dekker 2013-06-09 17:11:43 UTC
Created attachment 758875 [details]
File: maps

Comment 8 Gerhard Dekker 2013-06-09 17:11:46 UTC
Created attachment 758876 [details]
File: open_fds

Comment 9 Gerhard Dekker 2013-06-09 17:11:48 UTC
Created attachment 758877 [details]
File: proc_pid_status

Comment 10 Gerhard Dekker 2013-06-09 17:11:51 UTC
Created attachment 758878 [details]
File: var_log_messages

Comment 11 Fedora Admin XMLRPC Client 2014-07-26 17:11:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Fedora Admin XMLRPC Client 2014-07-27 06:33:05 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Debarshi Ray 2014-10-01 13:16:47 UTC
*** Bug 1115180 has been marked as a duplicate of this bug. ***

Comment 14 Debarshi Ray 2014-10-01 13:18:12 UTC
This has also happened in recent versions like tracker-1.0.1-2.fc21. See bug 1115180

Comment 15 Debarshi Ray 2014-10-01 13:19:51 UTC
*** Bug 1048568 has been marked as a duplicate of this bug. ***

Comment 16 Fedora End Of Life 2015-11-04 13:56:38 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 17 Fedora End Of Life 2015-12-02 02:48:07 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.