digiKam › digikam-users

Crashes in many circumstances

Classic

List

Threaded

10 messages Options

Noeck

Crashes in many circumstances

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
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Gilles Caulier-4

Re: Crashes in many circumstances

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 <[hidden email]>:

> 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
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Noeck

Re: Crashes in many circumstances

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@entry=0x12bc0570, values=..., idx=idx@entry=0,
initialFetch=initialFetch@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@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@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@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 <[hidden email]>:
>> 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

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Gilles Caulier-4

Re: Crashes in many circumstances

yes. It sound like a UPSTREAM bug from libsqlite :

https://bugs.kde.org/show_bug.cgi?id=329697

Gilles Caulier

2014-10-11 22:08 GMT+02:00 Noeck <[hidden email]>:

> 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@entry=0x12bc0570, values=..., idx=idx@entry=0,
> initialFetch=initialFetch@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@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@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@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 <[hidden email]>:
>>> 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
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Noeck

Re: Crashes in many circumstances

Hi Gilles,

thanks. That bug seems appeared several times while I read the mailing
list archive. Do I understand it right that this is a bug with libsqlite
3.8.2 and it should be fixed in the next Ubuntu release (libsqlite3 3.8.6)?

Is my database still ok after several crashes or should I rebuild it
from scratch by importing the metadata from the files with the new
Ubuntu version?

Cheers,
Daniel

Am 11.10.2014 um 22:14 schrieb Gilles Caulier:
> yes. It sound like a UPSTREAM bug from libsqlite :
>
> https://bugs.kde.org/show_bug.cgi?id=329697
>
> Gilles Caulier
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Gilles Caulier-4

Re: Crashes in many circumstances

2014-10-11 22:28 GMT+02:00 Noeck <[hidden email]>:
> Hi Gilles,
>
> thanks. That bug seems appeared several times while I read the mailing
> list archive. Do I understand it right that this is a bug with libsqlite
> 3.8.2 and it should be fixed in the next Ubuntu release (libsqlite3 3.8.6)?

yes, i think.

>
> Is my database still ok after several crashes or should I rebuild it
> from scratch by importing the metadata from the files with the new
> Ubuntu version?

Difficult to said. It's probably better to rebuild DB from scratch.

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Philippe Clérié

Re: Crashes in many circumstances

In reply to this post by Noeck

On 10/11/2014 01:43 PM, Noeck wrote:

I never got 3.5 working to my satisfaction: impossible to edit in any
way shape or form. 4.0 to 4.3 crashed all the time, and not necessarily
for the same reasons. The 2 really bad problems are with SQlite and
libkexiv2. There are solutions it seems, but they have not appeared in
Kubuntu 14.04 as far as I can tell, and I have been running on
backports, Kubuntu PPA and another PPA for digikam.

I am now experimenting a bit with Digikam 4.2 on Kubuntu 14.10. It
appears to be more stable. I was able to work for a few hours a couple
of days ago. But then a system update brought me a bad kernel. Been
fighting Kubuntu since then. (It's a beta; so par for the course!)

I have just downgraded to a previous kernel so now that my system is up
again I can eventually continue checking out 4.2. Crossing fingers and
praying to the spirits.

I have not had any particular problem with the database itself, but it
probably won't hurt to rebuild it.

Hope that helps!

--
Philippe

------
The trouble with common sense it that it is so uncommon.
<Anonymous>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Jan Wolter

Re: Crashes in many circumstances

I think it would be a good idea to switch to the newest stable version
4.4.0, since the problems concerning libexiv2 are fixed there. To solve
the sqlite problem, you could download the newest *.deb files (you need
sqlite3 and libsqlite3-0) from the upcoming Ubuntu release and install
them with dpkg.

Best regards,
Jan

On 10/14/2014 03:38 AM, Philippe Clérié wrote:

> I never got 3.5 working to my satisfaction: impossible to edit in any
> way shape or form. 4.0 to 4.3 crashed all the time, and not
> necessarily for the same reasons. The 2 really bad problems are with
> SQlite and libkexiv2. There are solutions it seems, but they have not
> appeared in Kubuntu 14.04 as far as I can tell, and I have been
> running on backports, Kubuntu PPA and another PPA for digikam.
>
> I am now experimenting a bit with Digikam 4.2 on Kubuntu 14.10. It
> appears to be more stable. I was able to work for a few hours a couple
> of days ago. But then a system update brought me a bad kernel. Been
> fighting Kubuntu since then. (It's a beta; so par for the course!)
>
> I have just downgraded to a previous kernel so now that my system is
> up again I can eventually continue checking out 4.2. Crossing fingers
> and praying to the spirits.
>
> I have not had any particular problem with the database itself, but it
> probably won't hurt to rebuild it.
>
> Hope that helps!
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Jan Wolter

Re: Crashes in many circumstances

Ah, I just read you have the upcoming Kubuntu already installed. Then
you should install dk 4.4.0. For me the newest release is very stable
and runs without crashes.

On 10/14/2014 09:57 AM, Jan Wolter wrote:

> I think it would be a good idea to switch to the newest stable version
> 4.4.0, since the problems concerning libexiv2 are fixed there. To
> solve the sqlite problem, you could download the newest *.deb files
> (you need sqlite3 and libsqlite3-0) from the upcoming Ubuntu release
> and install them with dpkg.
>
> Best regards,
> Jan
>
> On 10/14/2014 03:38 AM, Philippe Clérié wrote:
>> I never got 3.5 working to my satisfaction: impossible to edit in any
>> way shape or form. 4.0 to 4.3 crashed all the time, and not
>> necessarily for the same reasons. The 2 really bad problems are with
>> SQlite and libkexiv2. There are solutions it seems, but they have not
>> appeared in Kubuntu 14.04 as far as I can tell, and I have been
>> running on backports, Kubuntu PPA and another PPA for digikam.
>>
>> I am now experimenting a bit with Digikam 4.2 on Kubuntu 14.10. It
>> appears to be more stable. I was able to work for a few hours a
>> couple of days ago. But then a system update brought me a bad kernel.
>> Been fighting Kubuntu since then. (It's a beta; so par for the course!)
>>
>> I have just downgraded to a previous kernel so now that my system is
>> up again I can eventually continue checking out 4.2. Crossing fingers
>> and praying to the spirits.
>>
>> I have not had any particular problem with the database itself, but
>> it probably won't hurt to rebuild it.
>>
>> Hope that helps!
>>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Philippe Clérié

Re: Crashes in many circumstances

In reply to this post by Jan Wolter

On 10/14/2014 03:57 AM, Jan Wolter wrote:

> I think it would be a good idea to switch to the newest stable version
> 4.4.0, since the problems concerning libexiv2 are fixed there. To solve
> the sqlite problem, you could download the newest *.deb files (you need
> sqlite3 and libsqlite3-0) from the upcoming Ubuntu release and install
> them with dpkg.
>
> Best regards,
> Jan
>
> On 10/14/2014 03:38 AM, Philippe Clérié wrote:
>> I never got 3.5 working to my satisfaction: impossible to edit in any
>> way shape or form. 4.0 to 4.3 crashed all the time, and not
>> necessarily for the same reasons. The 2 really bad problems are with
>> SQlite and libkexiv2. There are solutions it seems, but they have not
>> appeared in Kubuntu 14.04 as far as I can tell, and I have been
>> running on backports, Kubuntu PPA and another PPA for digikam.
>>
>> I am now experimenting a bit with Digikam 4.2 on Kubuntu 14.10. It
>> appears to be more stable. I was able to work for a few hours a couple
>> of days ago. But then a system update brought me a bad kernel. Been
>> fighting Kubuntu since then. (It's a beta; so par for the course!)
>>
>> I have just downgraded to a previous kernel so now that my system is
>> up again I can eventually continue checking out 4.2. Crossing fingers
>> and praying to the spirits.
>>
>> I have not had any particular problem with the database itself, but it
>> probably won't hurt to rebuild it.
>>
>> Hope that helps!
>>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

I am pleased to hear that 4.4 works with utopic. But I am going to very
conservative this time around. I'll stick to whatever version works
_and_ is included in the distribution.

To be honest, getting a working version of Digikam is the only reason
why I'm not sticking to Trusty. It's only fair that I give some other
software a chance at frustrating me. ;-)

--
Philippe

------
The trouble with common sense it that it is so uncommon.
<Anonymous>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users