Red Hat Bugzilla – Bug 1028807
[abrt] clementine-1.1.1-9.fc21: sqlite3_free: Process /usr/bin/clementine was killed by signal 11 (SIGSEGV)
Last modified: 2016-07-19 06:34:40 EDT
Description of problem:
I managed to start about three clementines at once, so I closed the surplus ones and the abrt report appeared
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#1 sqlite3_free at sqlite3.c:19290
#2 sqlite3DeleteTable at sqlite3.c:84333
#3 sqlite3SchemaClear at sqlite3.c:88098
#4 sqlite3BtreeClose at sqlite3.c:52112
#5 sqlite3LeaveMutexAndCloseZombie at sqlite3.c:118385
#6 sqlite3Close at sqlite3.c:118328
#7 QSQLiteDriver::close at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:589
#8 QSqlDatabase::~QSqlDatabase at kernel/qsqldatabase.cpp:803
#9 ~QHashNode at ../../src/corelib/tools/qhash.h:216
#10 QHash<QString, QSqlDatabase>::deleteNode2 at ../../src/corelib/tools/qhash.h:521
Created attachment 822176 [details]
Created attachment 822177 [details]
Created attachment 822178 [details]
Created attachment 822179 [details]
Created attachment 822180 [details]
Created attachment 822181 [details]
Created attachment 822182 [details]
Created attachment 822183 [details]
Created attachment 822184 [details]
Created attachment 822185 [details]
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.