Bug 1033219

Summary: Clementine : search in database really slow with sqlite 3.8
Product: [Fedora] Fedora Reporter: Dag <den.mail>
Component: clementineAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jgrulich
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:20:49 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:

Description Dag 2013-11-21 17:53:05 UTC
Description of problem:
when doing a search (any search) in music database, the search can take several minutes to display some result.
When it's searching, one CPU core is taken 100% by Clementine and the GUI is frozen.

With sqlite-3.7.17-1.fc19.x86_64 searches were taking no time to a fex seconds, always less than 5s.

So this makes a HUGE difference and renders the search in database unpractical.


Version-Release number of selected component (if applicable):
Using :
- clementine-1.1.1-4.fc19.x86_64
- sqlite-3.8.0.2-4.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. install Fedora 19 and Clementine with sqlite-3.7.17-1.fc19.x86_64
2. open Clementine and update music database
3. make searches : it takes no time to output results,
4. update to sqlite-3.8.0.2-4.fc19.x86_64,
5. restart Clementine
6. make a search in the music database : it's taking minutes to complete and GUI is frozen waiting for the search to finish

Actual results:
Clementine takes several minutes to complete any search in the music database, which makes this database unusable.

Expected results:
the search should complete in less than 5s as it used to be.

Additional info:
This issue is described here :
http://code.google.com/p/clementine-player/issues/detail?id=3847

Mybe this information will be useful to the packager.

Bye for now,
Dag

Comment 1 Fedora Admin XMLRPC Client 2014-02-10 18:36:16 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Admin XMLRPC Client 2014-02-27 01:23:58 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-01-09 20:39:37 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 4 Fedora End Of Life 2015-02-17 19:20:49 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.