[Digikam-users] Crashes in many circumstances

[Noeck]

Hi Gilles,

thanks. I opened the image editor, clicked on the toolbox, clicked in
the image again (no changes to the image) and closed the editor again.
Digikam crashed and this is the rest of the program output and the stack
trace:

void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*,
QMenu*, int, int, const QStringList&): No id for action
void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*,
QMenu*, int, int, const QStringList&): No id for action
void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*,
QMenu*, int, int, const QStringList&): No id for action
[Thread 0x7fff2effd700 (LWP 13436) exited]
[Thread 0x7fff35ffb700 (LWP 13423) exited]
[Thread 0x7fff9d7f9700 (LWP 13403) exited]
[Thread 0x7fff55ffb700 (LWP 13416) exited]
[Thread 0x7fff9cff8700 (LWP 13404) exited]
[Thread 0x7fff76ffd700 (LWP 13407) exited]
[Thread 0x7fff9f7fd700 (LWP 13399) exited]
[Thread 0x7fff75ffb700 (LWP 13409) exited]
[Thread 0x7fff9effc700 (LWP 13400) exited]
[Thread 0x7fff2f7fe700 (LWP 13427) exited]
[Thread 0x7fff57fff700 (LWP 13412) exited]
[Thread 0x7fff767fc700 (LWP 13408) exited]

Program received signal SIGSEGV, Segmentation fault.
0x0000000001fbff50 in ?? ()
(gdb) bt
#0  0x0000000001fbff50 in ?? ()
#1  0x00007fffdc4eddac in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#2  0x00007fffdc4edf63 in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#3  0x00007fffdc502579 in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#4  0x00007fffdc52a9c5 in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#5  0x00007fffdc532ed7 in sqlite3_step ()
   from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#6  0x00007fffb08cb11c in QSQLiteResultPrivate::fetchNext (
    this=this at entry=0x12bc0570, values=..., idx=idx at entry=0,
    initialFetch=initialFetch at entry=true)
    at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:235
#7  0x00007fffb08cbe48 in QSQLiteResult::exec (this=0x1008dd80)
    at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:447
#8  0x00007ffff7babb7d in QSqlQuery::exec (this=this at entry=0x7fffffffc188)
    at kernel/qsqlquery.cpp:949
#9  0x00007ffff55b6a26 in Digikam::DatabaseCoreBackend::exec
(this=0xf71350,
    query=...)
    at
/build/buildd/digikam-3.5.0/core/libs/database/core/databasecorebackend.cpp:1414
#10 0x00007ffff55b6aac in Digikam::DatabaseCoreBackend::execQuery (
    this=this at entry=0xf71350, query=..., boundValue1=...)
    at
/build/buildd/digikam-3.5.0/core/libs/database/core/databasecorebackend.cpp:1056
#11 0x00007ffff55b7b50 in Digikam::DatabaseCoreBackend::execQuery (
    this=this at entry=0xf71350, sql=..., boundValue1=...)
    at
/build/buildd/digikam-3.5.0/core/libs/database/core/databasecorebackend.c


Does that tell you something?

Cheers,
Daniel

Am 11.10.2014 um 21:48 schrieb Gilles Caulier:
> Run digikam into gdb to get a backtrace. Follow instructions here :
> 
> https://www.digikam.org/contrib
> 
> Gilles Caulier
> 
> 2014-10-11 19:43 GMT+02:00 Noeck <noeck.marburg at gmx.de>:
>> Hi,
>>
>> I use Digikam 3.5 under Ubuntu 14.04 (Qt: 4.8.6, KDE: 4.13.3). It
>> crashes very often (every 10-30 min) when editing images, changing
>> metadata, switching between albums.
>> In order to send meaningful bug reports, I installed digikam-dbg and
>> kdelibs5-dbg. But the stack trace is still not shown and it keeps saying
>> that this is no helpful bug report.
>>
>> What can I do to find the reason of these crashes?
>>
>> Thanks in advance,
>> Daniel