After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617081 - Crash detected in tracker-store (tracker-0.8.3)
Crash detected in tracker-store (tracker-0.8.3)
Status: RESOLVED OBSOLETE
Product: tracker
Classification: Core
Component: Store
0.8.x
Other Linux
: Low enhancement
: ---
Assigned To: tracker-general
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2010-04-28 13:52 UTC by Deji Akingunola
Modified: 2014-08-21 09:03 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Crash backtace (14.08 KB, text/plain)
2010-04-28 13:52 UTC, Deji Akingunola 		Details

Description Deji Akingunola 2010-04-28 13:52:35 UTC 
Created attachment 159797 [details]
Crash backtace

The bug is originally reported in Fedora, https://bugzilla.redhat.com/show_bug.cgi?id=586706 .

How to reproduce
-----
1. Initial indexing run with 0.8.3
2. abrt notices crash
3. file in bugzilla
Comment 1 Fabio Durán Verdugo 2010-04-28 13:54:29 UTC 
Paste here the stacktrace.

[New Thread 4153]
Core was generated by `/usr/libexec/tracker-store'.
Program terminated with signal 6, Aborted.
#0  0x00000034[New Thread 4153]
Core was generated by `/usr/libexec/tracker-store'.
Program terminated with signal 6, Aborted.

+ Trace 221590







Comment 2


Philip Van Hoof





          2010-04-28 14:09:34 UTC
        



This is caused by a corrupted database






Comment 3


Philip Van Hoof





          2010-04-28 14:13:03 UTC
        



The only way to avoid this from happening is removing the "PRAGMA synchronous = OFF;" on systems that don't require super good insertion speed. We could make this a configuration option, for example. Making this bug a featurerequest for that reason.


Note that after restart of tracker-store, the user's journal will be replayed and everything should be fixed.






Comment 4


Deji Akingunola





          2010-04-28 14:27:21 UTC
        



(In reply to comment #2)
> This is caused by a corrupted database

As the reporter stated, the crash happened on initial indexing after installing tracker-0.8.3 .It is very likely he/she was updating from tracker-0.6.96 (tracker-0.8.3 is the first version of tracker-0.8.x in Fedora 13).
I think this is a case of tracker needing to more gracefully handle upgrade from tracker-0.6.x to the latest.






Comment 5


Philip Van Hoof





          2010-04-28 14:50:33 UTC
        



No the backtrace is quite clear about it, it's the abort() that we do when the database is corrupted.





+
Trace
    221591






    

  • 
#4
create_result_set_from_stmt

    
                at tracker-db-interface-sqlite.c
                  line
                  701

    

    • 








Look for g_error in that function.






Comment 6


Martyn Russell





          2014-08-21 09:03:40 UTC
        



Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.