Summary: | Baloo crashes when adding tags to many files | ||
---|---|---|---|
Product: | [Unmaintained] Baloo | Reporter: | Eric Mesa <ericsbinaryworld> |
Component: | General | Assignee: | Vishesh Handa <me> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Eric Mesa
2015-07-27 09:53:47 UTC
Crash is in Sqlite through KDE Baloo interface : Thread 10 (Thread 0x7f8f397fa700 (LWP 8569)): [KCrash Handler] #6 0x00000036a1a349c8 in raise () at /lib64/libc.so.6 #7 0x00000036a1a3665a in abort () at /lib64/libc.so.6 #8 0x00000036a1a77a92 in () at /lib64/libc.so.6 #9 0x00000036a1a83d2d in free () at /lib64/libc.so.6 #10 0x00000036bd61775b in sqlite3_free () at /lib64/libsqlite3.so.0 #11 0x00000036bd625c94 in vdbeFreeOpArray () at /lib64/libsqlite3.so.0 #12 0x00000036bd62611c in sqlite3VdbeClearObject () at /lib64/libsqlite3.so.0 #13 0x00000036bd62619c in sqlite3VdbeDelete () at /lib64/libsqlite3.so.0 #14 0x00000036bd66b4a6 in sqlite3VdbeFinalize () at /lib64/libsqlite3.so.0 #15 0x00000036bd66b4e7 in sqlite3_finalize () at /lib64/libsqlite3.so.0 #16 0x00007f8f550f19ad in QSQLiteDriver::close() () at /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so #17 0x00007f8f550efe2e in QSQLiteDriver::open(QString const&, QString const&, QString const&, QString const&, int, QString const&) () at /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so #18 0x00000036b2c133f0 in QSqlDatabase::open() () at /lib64/libQtSql.so.4 #19 0x000000314ce128bb in fileMappingDb(QString const&) () at /lib64/libbaloofiles.so.4 #20 0x000000314ce132b5 in fileMappingDb() () at /lib64/libbaloofiles.so.4 #21 0x000000314ce0e07f in Baloo::FileModifyJob::doStart() () at /lib64/libbaloofiles.so.4 Gilles Caulier Fixed with Plasma 5. I am pretty sure I'm using Plasma 5. I'm in KDE 5.3 or whatever Fedora's latest KDE is. Could you be more specific about the version of Baloo or whatever so I can check? (In reply to Eric Mesa from comment #3) > I am pretty sure I'm using Plasma 5. I'm in KDE 5.3 or whatever Fedora's > latest KDE is. Could you be more specific about the version of Baloo or > whatever so I can check? Sorry. I should have been more clear. It was fixed with Baloo 5.x. where 'x' can be anything. The thing is that the Digikam you're using is the Qt4 version not 5. (In reply to Vishesh Handa from comment #4) > (In reply to Eric Mesa from comment #3) > > I am pretty sure I'm using Plasma 5. I'm in KDE 5.3 or whatever Fedora's > > latest KDE is. Could you be more specific about the version of Baloo or > > whatever so I can check? > > Sorry. I should have been more clear. It was fixed with Baloo 5.x. where 'x' > can be anything. The thing is that the Digikam you're using is the Qt4 > version not 5. Ah, ok. So until Digikam with QT5 is released this will be an issue. Am I right? Thanks for the info. (In reply to Eric Mesa from comment #5) > (In reply to Vishesh Handa from comment #4) > > (In reply to Eric Mesa from comment #3) > > > I am pretty sure I'm using Plasma 5. I'm in KDE 5.3 or whatever Fedora's > > > latest KDE is. Could you be more specific about the version of Baloo or > > > whatever so I can check? > > > > Sorry. I should have been more clear. It was fixed with Baloo 5.x. where 'x' > > can be anything. The thing is that the Digikam you're using is the Qt4 > > version not 5. > > Ah, ok. So until Digikam with QT5 is released this will be an issue. Am I > right? Thanks for the info. Yes. |