Digikam 3.5 is crashing

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Digikam 3.5 is crashing

Jim Dory-2
I have been very unstable since 3.5. I'm running Gentoo and unstable settings  ( ~amd_64) but haven't had any problem until this latest digikam version.  KDE-4.12

I can work several minutes and then it crashes. Not reproducible other than just using it for a bit - nothing in particular seems to be the cause. Program just disappears - closes completely.

I recompiled it with the debug use flag (compiled in debug) and I'll give a little backtrace when it crashed - although this time it didn't just close like usual.. but maybe that was from running it with gdb. This time it just froze, and I see I had a seg fault. At the time I had just clicked on an image thumbnail in an album.

I've also had problems with it not properly reading the thumbnails. I can fix a few of them by running "rebuild the thumbnails in current album" but it won't fix them all and sometimes they revert to other image thumbnails.

I'm running the albums on a network attached storage, though the database is on my home partition.

Here's my component list followed by the 'bt':  (hope this helps - let me know what else you might want)

digiKam version 3.5.0
Demosaic GPL2 pack support: Yes
Demosaic GPL3 pack support: Yes
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibEigen: 3.1.3
LibExiv2: 0.23
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.12.0
LibKExiv2: 2.3.1
LibKGeoMap: 2.0.0
LibKdcraw: 2.4.2
LibLCMS: 2050
LibLensFun: 0.2.8-0
LibPGF: 6.12.27 - external shared library
LibPNG: 1.6.7
LibQt: 4.8.5
LibRaw: 0.15.4
LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.17.0 (stable version)
Parallelized PGF codec: No
Parallelized demosaicing: Yes
RawSpeed codec support: Yes
Database backend: QSQLITE
Kipi-Plugins: 3.5.0
LibKface: 3.0.0
LibKipi: 2.1.0
LibOpenCV: 2.4.6.1



digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory: Loading image history  ""
[Thread 0x7fffb6b02700 (LWP 13427) exited]
[Thread 0x7fff96c89700 (LWP 13428) exited]
[Thread 0x7fffb7677700 (LWP 13429) exited]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
#2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
#3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
#4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
#5  0x00007fffe09a5ed6 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
#6  0x00007fffd4a52b4f in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
#7  0x00007fffd4a538ef in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
#8  0x00007ffff7bac687 in QSqlQuery::exec() () from /usr/lib64/qt4/libQtSql.so.4
#9  0x00007ffff5511c86 in Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from /usr/lib64/libdigikamcore.so.3
#10 0x00007ffff5511d0c in Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
#11 0x00007ffff5512b80 in Digikam::DatabaseCoreBackend::execQuery(QString const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
#12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString const&, QVariant const&, QList<QVariant>*, QVariant*) () from /usr/lib64/libdigikamcore.so.3
#13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&) () from /usr/lib64/libdigikamdatabase.so.3
#14 0x00007ffff4e804a9 in Digikam::AlbumDB::getFilterSettings(QStringList*, QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
#15 0x000000000065f9a5 in ?? ()
#16 0x00000000005442e6 in ?? ()
#17 0x0000000000543c54 in ?? ()
#18 0x00007fff9415ae34 in ?? () from /usr/lib64/kde4/kipiplugin_advancedslideshow.so
#19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) () from /usr/lib64/libkipi.so.11
#21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00000000005bb724 in ?? ()
#23 0x00000000005e39d5 in ?? ()
#24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#25 0x00007ffff397925e in QFrame::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#28 0x00000000005dad40 in ?? ()
#29 0x00007ffff2b46f65 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib64/qt4/libQtGui.so.4
#35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
#36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
#40 0x00007fffeaf6022c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#41 0x00007ffff2b75884 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#43 0x00007ffff2b45a2f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#44 0x00007ffff2b45d10 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#46 0x0000000000497a3c in ?? ()
#47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
#48 0x000000000049a151 in _start ()
(gdb) quit
A debugging session is active.

        Inferior 1 [process 13284] will be killed.


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Gilles Caulier-4
It crash in Sqlite Qt driver. There is no reason for that, excepted if
binary compatibility is broken due to a recent update of system
package... It's the eternal problem under Linux if packager don't take
a care enough...

Note : your digiKam is not compiled with debug symbols. There is no
source code from digiKam printed in GDB...

Gilles Caulier

2013/12/20 Jim Dory <[hidden email]>:

> I have been very unstable since 3.5. I'm running Gentoo and unstable
> settings  ( ~amd_64) but haven't had any problem until this latest digikam
> version.  KDE-4.12
>
> I can work several minutes and then it crashes. Not reproducible other than
> just using it for a bit - nothing in particular seems to be the cause.
> Program just disappears - closes completely.
>
> I recompiled it with the debug use flag (compiled in debug) and I'll give a
> little backtrace when it crashed - although this time it didn't just close
> like usual.. but maybe that was from running it with gdb. This time it just
> froze, and I see I had a seg fault. At the time I had just clicked on an
> image thumbnail in an album.
>
> I've also had problems with it not properly reading the thumbnails. I can
> fix a few of them by running "rebuild the thumbnails in current album" but
> it won't fix them all and sometimes they revert to other image thumbnails.
>
> I'm running the albums on a network attached storage, though the database is
> on my home partition.
>
> Here's my component list followed by the 'bt':  (hope this helps - let me
> know what else you might want)
>
> digiKam version 3.5.0
> Demosaic GPL2 pack support: Yes
> Demosaic GPL3 pack support: Yes
> Exiv2 can write to Jp2: Yes
> Exiv2 can write to Jpeg: Yes
> Exiv2 can write to Pgf: Yes
> Exiv2 can write to Png: Yes
> Exiv2 can write to Tiff: Yes
> Exiv2 supports XMP metadata: Yes
> LibCImg: 130
> LibEigen: 3.1.3
> LibExiv2: 0.23
> LibJPEG: 62
> LibJasper: 1.900.1
> LibKDE: 4.12.0
> LibKExiv2: 2.3.1
> LibKGeoMap: 2.0.0
> LibKdcraw: 2.4.2
> LibLCMS: 2050
> LibLensFun: 0.2.8-0
> LibPGF: 6.12.27 - external shared library
> LibPNG: 1.6.7
> LibQt: 4.8.5
> LibRaw: 0.15.4
> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler
> Copyright (c) 1991-1996 Silicon Graphics, Inc.
> Marble Widget: 0.17.0 (stable version)
> Parallelized PGF codec: No
> Parallelized demosaicing: Yes
> RawSpeed codec support: Yes
> Database backend: QSQLITE
> Kipi-Plugins: 3.5.0
> LibKface: 3.0.0
> LibKipi: 2.1.0
> LibOpenCV: 2.4.6.1
>
>
>
> digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory: Loading
> image history  ""
> [Thread 0x7fffb6b02700 (LWP 13427) exited]
> [Thread 0x7fff96c89700 (LWP 13428) exited]
> [Thread 0x7fffb7677700 (LWP 13429) exited]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0  0x0000000000000000 in ?? ()
> #1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
> #2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
> #3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
> #4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
> #5  0x00007fffe09a5ed6 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
> #6  0x00007fffd4a52b4f in ?? () from
> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
> #7  0x00007fffd4a538ef in ?? () from
> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
> #8  0x00007ffff7bac687 in QSqlQuery::exec() () from
> /usr/lib64/qt4/libQtSql.so.4
> #9  0x00007ffff5511c86 in
> Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
> /usr/lib64/libdigikamcore.so.3
> #10 0x00007ffff5511d0c in
> Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant const&)
> () from /usr/lib64/libdigikamcore.so.3
> #11 0x00007ffff5512b80 in Digikam::DatabaseCoreBackend::execQuery(QString
> const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
> #12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString
> const&, QVariant const&, QList<QVariant>*, QVariant*) () from
> /usr/lib64/libdigikamcore.so.3
> #13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&) ()
> from /usr/lib64/libdigikamdatabase.so.3
> #14 0x00007ffff4e804a9 in Digikam::AlbumDB::getFilterSettings(QStringList*,
> QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
> #15 0x000000000065f9a5 in ?? ()
> #16 0x00000000005442e6 in ?? ()
> #17 0x0000000000543c54 in ?? ()
> #18 0x00007fff9415ae34 in ?? () from
> /usr/lib64/kde4/kipiplugin_advancedslideshow.so
> #19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
> #20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) () from
> /usr/lib64/libkipi.so.11
> #21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
> #22 0x00000000005bb724 in ?? ()
> #23 0x00000000005e39d5 in ?? ()
> #24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #25 0x00007ffff397925e in QFrame::event(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #28 0x00000000005dad40 in ?? ()
> #29 0x00007ffff2b46f65 in
> QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
> from /usr/lib64/qt4/libQtCore.so.4
> #30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
> #31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) () from
> /usr/lib64/libkdeui.so.5
> #33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*,
> QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
> #34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*,
> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
> from /usr/lib64/qt4/libQtGui.so.4
> #35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from
> /usr/lib64/libglib-2.0.so.0
> #39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
> #40 0x00007fffeaf6022c in g_main_context_iteration () from
> /usr/lib64/libglib-2.0.so.0
> #41 0x00007ffff2b75884 in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () from /usr/lib64/qt4/libQtCore.so.4
> #42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #43 0x00007ffff2b45a2f in
> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib64/qt4/libQtCore.so.4
> #44 0x00007ffff2b45d10 in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib64/qt4/libQtCore.so.4
> #45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from
> /usr/lib64/qt4/libQtCore.so.4
> #46 0x0000000000497a3c in ?? ()
> #47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
> #48 0x000000000049a151 in _start ()
> (gdb) quit
> A debugging session is active.
>
>         Inferior 1 [process 13284] will be killed.
>
>
> _______________________________________________
> 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
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Jim Dory-2
Thanks for info. I've compiled it with the debug use flag so will have to research it a bit to see how to get more debugging. Appreciate your work!
cheers, Jim


On Fri, Dec 20, 2013 at 12:20 AM, Gilles Caulier <[hidden email]> wrote:
It crash in Sqlite Qt driver. There is no reason for that, excepted if
binary compatibility is broken due to a recent update of system
package... It's the eternal problem under Linux if packager don't take
a care enough...

Note : your digiKam is not compiled with debug symbols. There is no
source code from digiKam printed in GDB...

Gilles Caulier

2013/12/20 Jim Dory <[hidden email]>:
> I have been very unstable since 3.5. I'm running Gentoo and unstable
> settings  ( ~amd_64) but haven't had any problem until this latest digikam
> version.  KDE-4.12
>
> I can work several minutes and then it crashes. Not reproducible other than
> just using it for a bit - nothing in particular seems to be the cause.
> Program just disappears - closes completely.
>
> I recompiled it with the debug use flag (compiled in debug) and I'll give a
> little backtrace when it crashed - although this time it didn't just close
> like usual.. but maybe that was from running it with gdb. This time it just
> froze, and I see I had a seg fault. At the time I had just clicked on an
> image thumbnail in an album.
>
> I've also had problems with it not properly reading the thumbnails. I can
> fix a few of them by running "rebuild the thumbnails in current album" but
> it won't fix them all and sometimes they revert to other image thumbnails.
>
> I'm running the albums on a network attached storage, though the database is
> on my home partition.
>
> Here's my component list followed by the 'bt':  (hope this helps - let me
> know what else you might want)
>
> digiKam version 3.5.0
> Demosaic GPL2 pack support: Yes
> Demosaic GPL3 pack support: Yes
> Exiv2 can write to Jp2: Yes
> Exiv2 can write to Jpeg: Yes
> Exiv2 can write to Pgf: Yes
> Exiv2 can write to Png: Yes
> Exiv2 can write to Tiff: Yes
> Exiv2 supports XMP metadata: Yes
> LibCImg: 130
> LibEigen: 3.1.3
> LibExiv2: 0.23
> LibJPEG: 62
> LibJasper: 1.900.1
> LibKDE: 4.12.0
> LibKExiv2: 2.3.1
> LibKGeoMap: 2.0.0
> LibKdcraw: 2.4.2
> LibLCMS: 2050
> LibLensFun: 0.2.8-0
> LibPGF: 6.12.27 - external shared library
> LibPNG: 1.6.7
> LibQt: 4.8.5
> LibRaw: 0.15.4
> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler
> Copyright (c) 1991-1996 Silicon Graphics, Inc.
> Marble Widget: 0.17.0 (stable version)
> Parallelized PGF codec: No
> Parallelized demosaicing: Yes
> RawSpeed codec support: Yes
> Database backend: QSQLITE
> Kipi-Plugins: 3.5.0
> LibKface: 3.0.0
> LibKipi: 2.1.0
> LibOpenCV: 2.4.6.1
>
>
>
> digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory: Loading
> image history  ""
> [Thread 0x7fffb6b02700 (LWP 13427) exited]
> [Thread 0x7fff96c89700 (LWP 13428) exited]
> [Thread 0x7fffb7677700 (LWP 13429) exited]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0  0x0000000000000000 in ?? ()
> #1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
> #2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
> #3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
> #4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
> #5  0x00007fffe09a5ed6 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
> #6  0x00007fffd4a52b4f in ?? () from
> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
> #7  0x00007fffd4a538ef in ?? () from
> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
> #8  0x00007ffff7bac687 in QSqlQuery::exec() () from
> /usr/lib64/qt4/libQtSql.so.4
> #9  0x00007ffff5511c86 in
> Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
> /usr/lib64/libdigikamcore.so.3
> #10 0x00007ffff5511d0c in
> Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant const&)
> () from /usr/lib64/libdigikamcore.so.3
> #11 0x00007ffff5512b80 in Digikam::DatabaseCoreBackend::execQuery(QString
> const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
> #12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString
> const&, QVariant const&, QList<QVariant>*, QVariant*) () from
> /usr/lib64/libdigikamcore.so.3
> #13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&) ()
> from /usr/lib64/libdigikamdatabase.so.3
> #14 0x00007ffff4e804a9 in Digikam::AlbumDB::getFilterSettings(QStringList*,
> QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
> #15 0x000000000065f9a5 in ?? ()
> #16 0x00000000005442e6 in ?? ()
> #17 0x0000000000543c54 in ?? ()
> #18 0x00007fff9415ae34 in ?? () from
> /usr/lib64/kde4/kipiplugin_advancedslideshow.so
> #19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
> #20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) () from
> /usr/lib64/libkipi.so.11
> #21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
> #22 0x00000000005bb724 in ?? ()
> #23 0x00000000005e39d5 in ?? ()
> #24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #25 0x00007ffff397925e in QFrame::event(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #28 0x00000000005dad40 in ?? ()
> #29 0x00007ffff2b46f65 in
> QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
> from /usr/lib64/qt4/libQtCore.so.4
> #30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
> #31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) () from
> /usr/lib64/libkdeui.so.5
> #33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*,
> QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
> #34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*,
> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
> from /usr/lib64/qt4/libQtGui.so.4
> #35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from
> /usr/lib64/libglib-2.0.so.0
> #39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
> #40 0x00007fffeaf6022c in g_main_context_iteration () from
> /usr/lib64/libglib-2.0.so.0
> #41 0x00007ffff2b75884 in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () from /usr/lib64/qt4/libQtCore.so.4
> #42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #43 0x00007ffff2b45a2f in
> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib64/qt4/libQtCore.so.4
> #44 0x00007ffff2b45d10 in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib64/qt4/libQtCore.so.4
> #45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from
> /usr/lib64/qt4/libQtCore.so.4
> #46 0x0000000000497a3c in ?? ()
> #47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
> #48 0x000000000049a151 in _start ()
> (gdb) quit
> A debugging session is active.
>
>         Inferior 1 [process 13284] will be killed.
>
>
> _______________________________________________
> 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


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Peter Albrecht
Hello Jim,

one reason for missing debug symbols under gentoo might be
the stripping, portage does at default.

Just adding "-ggdb" to your CFLAGS is not enough. You also
have to add "nostrip" or "splitdebug" to your FEATURES.

For details see:
> http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces#Stripping

Regards,
        Peter

On 20.12.2013 18:50, Jim Dory wrote:

> Thanks for info. I've compiled it with the debug use flag so will have to
> research it a bit to see how to get more debugging. Appreciate your work!
> cheers, Jim
>
>
> On Fri, Dec 20, 2013 at 12:20 AM, Gilles Caulier
> <[hidden email]>wrote:
>
>> It crash in Sqlite Qt driver. There is no reason for that, excepted if
>> binary compatibility is broken due to a recent update of system
>> package... It's the eternal problem under Linux if packager don't take
>> a care enough...
>>
>> Note : your digiKam is not compiled with debug symbols. There is no
>> source code from digiKam printed in GDB...
>>
>> Gilles Caulier
>>
>> 2013/12/20 Jim Dory <[hidden email]>:
>>> I have been very unstable since 3.5. I'm running Gentoo and unstable
>>> settings  ( ~amd_64) but haven't had any problem until this latest
>> digikam
>>> version.  KDE-4.12
>>>
>>> I can work several minutes and then it crashes. Not reproducible other
>> than
>>> just using it for a bit - nothing in particular seems to be the cause.
>>> Program just disappears - closes completely.
>>>
>>> I recompiled it with the debug use flag (compiled in debug) and I'll
>> give a
>>> little backtrace when it crashed - although this time it didn't just
>> close
>>> like usual.. but maybe that was from running it with gdb. This time it
>> just
>>> froze, and I see I had a seg fault. At the time I had just clicked on an
>>> image thumbnail in an album.
>>>
>>> I've also had problems with it not properly reading the thumbnails. I can
>>> fix a few of them by running "rebuild the thumbnails in current album"
>> but
>>> it won't fix them all and sometimes they revert to other image
>> thumbnails.
>>>
>>> I'm running the albums on a network attached storage, though the
>> database is
>>> on my home partition.
>>>
>>> Here's my component list followed by the 'bt':  (hope this helps - let me
>>> know what else you might want)
>>>
>>> digiKam version 3.5.0
>>> Demosaic GPL2 pack support: Yes
>>> Demosaic GPL3 pack support: Yes
>>> Exiv2 can write to Jp2: Yes
>>> Exiv2 can write to Jpeg: Yes
>>> Exiv2 can write to Pgf: Yes
>>> Exiv2 can write to Png: Yes
>>> Exiv2 can write to Tiff: Yes
>>> Exiv2 supports XMP metadata: Yes
>>> LibCImg: 130
>>> LibEigen: 3.1.3
>>> LibExiv2: 0.23
>>> LibJPEG: 62
>>> LibJasper: 1.900.1
>>> LibKDE: 4.12.0
>>> LibKExiv2: 2.3.1
>>> LibKGeoMap: 2.0.0
>>> LibKdcraw: 2.4.2
>>> LibLCMS: 2050
>>> LibLensFun: 0.2.8-0
>>> LibPGF: 6.12.27 - external shared library
>>> LibPNG: 1.6.7
>>> LibQt: 4.8.5
>>> LibRaw: 0.15.4
>>> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler
>>> Copyright (c) 1991-1996 Silicon Graphics, Inc.
>>> Marble Widget: 0.17.0 (stable version)
>>> Parallelized PGF codec: No
>>> Parallelized demosaicing: Yes
>>> RawSpeed codec support: Yes
>>> Database backend: QSQLITE
>>> Kipi-Plugins: 3.5.0
>>> LibKface: 3.0.0
>>> LibKipi: 2.1.0
>>> LibOpenCV: 2.4.6.1
>>>
>>>
>>>
>>> digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory:
>> Loading
>>> image history  ""
>>> [Thread 0x7fffb6b02700 (LWP 13427) exited]
>>> [Thread 0x7fff96c89700 (LWP 13428) exited]
>>> [Thread 0x7fffb7677700 (LWP 13429) exited]
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x0000000000000000 in ?? ()
>>> (gdb) bt
>>> #0  0x0000000000000000 in ?? ()
>>> #1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
>>> #2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
>>> #3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
>>> #4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
>>> #5  0x00007fffe09a5ed6 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
>>> #6  0x00007fffd4a52b4f in ?? () from
>>> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>>> #7  0x00007fffd4a538ef in ?? () from
>>> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>>> #8  0x00007ffff7bac687 in QSqlQuery::exec() () from
>>> /usr/lib64/qt4/libQtSql.so.4
>>> #9  0x00007ffff5511c86 in
>>> Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
>>> /usr/lib64/libdigikamcore.so.3
>>> #10 0x00007ffff5511d0c in
>>> Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant
>> const&)
>>> () from /usr/lib64/libdigikamcore.so.3
>>> #11 0x00007ffff5512b80 in Digikam::DatabaseCoreBackend::execQuery(QString
>>> const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
>>> #12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString
>>> const&, QVariant const&, QList<QVariant>*, QVariant*) () from
>>> /usr/lib64/libdigikamcore.so.3
>>> #13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&) ()
>>> from /usr/lib64/libdigikamdatabase.so.3
>>> #14 0x00007ffff4e804a9 in
>> Digikam::AlbumDB::getFilterSettings(QStringList*,
>>> QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
>>> #15 0x000000000065f9a5 in ?? ()
>>> #16 0x00000000005442e6 in ?? ()
>>> #17 0x0000000000543c54 in ?? ()
>>> #18 0x00007fff9415ae34 in ?? () from
>>> /usr/lib64/kde4/kipiplugin_advancedslideshow.so
>>> #19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>>> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>>> #20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) ()
>> from
>>> /usr/lib64/libkipi.so.11
>>> #21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>>> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>>> #22 0x00000000005bb724 in ?? ()
>>> #23 0x00000000005e39d5 in ?? ()
>>> #24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #25 0x00007ffff397925e in QFrame::event(QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) ()
>> from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #28 0x00000000005dad40 in ?? ()
>>> #29 0x00007ffff2b46f65 in
>>> QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*,
>> QEvent*) ()
>>> from /usr/lib64/qt4/libQtCore.so.4
>>> #30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*,
>>> QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
>>> #31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) () from
>>> /usr/lib64/libkdeui.so.5
>>> #33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*,
>>> QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
>>> #34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*,
>>> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
>>> from /usr/lib64/qt4/libQtGui.so.4
>>> #35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
>>> #36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>>> #38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from
>>> /usr/lib64/libglib-2.0.so.0
>>> #39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
>>> #40 0x00007fffeaf6022c in g_main_context_iteration () from
>>> /usr/lib64/libglib-2.0.so.0
>>> #41 0x00007ffff2b75884 in
>>>
>> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>> () from /usr/lib64/qt4/libQtCore.so.4
>>> #42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>>> #43 0x00007ffff2b45a2f in
>>> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
>>> /usr/lib64/qt4/libQtCore.so.4
>>> #44 0x00007ffff2b45d10 in
>>> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
>>> /usr/lib64/qt4/libQtCore.so.4
>>> #45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from
>>> /usr/lib64/qt4/libQtCore.so.4
>>> #46 0x0000000000497a3c in ?? ()
>>> #47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
>>> #48 0x000000000049a151 in _start ()
>>> (gdb) quit
>>> A debugging session is active.
>>>
>>>         Inferior 1 [process 13284] will be killed.
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> _______________________________________________
> 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
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Jim Dory-2
Thanks Peter for the help. I've tried it again and it output a bit more:

Program received signal SIGSEGV, Segmentation fault.
0x0000007f0000007f in ?? ()
(gdb) bt
#0  0x0000007f0000007f in ?? ()
#1  0x00007fffe09b9a9e in ?? () from /usr/lib64/libsqlite3.so.0
#2  0x00007fffe09b9e30 in ?? () from /usr/lib64/libsqlite3.so.0
#3  0x00007fffe09debbd in ?? () from /usr/lib64/libsqlite3.so.0
#4  0x00007fffe09e76c5 in ?? () from /usr/lib64/libsqlite3.so.0
#5  0x00007fffe09efed6 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
#6  0x00007fffd4a9cb4f in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
#7  0x00007fffd4a9d8ef in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
#8  0x00007ffff7bac687 in QSqlQuery::exec() () from /usr/lib64/qt4/libQtSql.so.4
#9  0x00007ffff55545e6 in Digikam::DatabaseCoreBackend::exec (this=0xe3fe70, query=...)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/core/databasecorebackend.cpp:1414
#10 0x00007ffff555466c in Digikam::DatabaseCoreBackend::execQuery (this=this@entry=0xe3fe70, query=..., boundValue1=...)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/core/databasecorebackend.cpp:1056
#11 0x00007ffff5555760 in Digikam::DatabaseCoreBackend::execQuery (this=this@entry=0xe3fe70, sql=..., boundValue1=...)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/core/databasecorebackend.cpp:1005
#12 0x00007ffff55557a9 in Digikam::DatabaseCoreBackend::execSql (this=0xe3fe70, sql=..., boundValue1=..., values=values@entry=0x7fffffffbbd0, lastInsertId=lastInsertId@entry=0x0)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/core/databasecorebackend.cpp:902
#13 0x00007ffff4edbbce in Digikam::AlbumDB::getSetting (this=this@entry=0xde85a0, keyword=...)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/albumdb.cpp:972
#14 0x00007ffff4edc4fc in Digikam::AlbumDB::getFilterSettings (this=0xde85a0, imageFilter=imageFilter@entry=0x7fffffffbe20, videoFilter=videoFilter@entry=0x7fffffffbe40, 
    audioFilter=audioFilter@entry=0x7fffffffbe30) at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/albumdb.cpp:1017
#15 0x00007ffff4ef24ec in Digikam::CollectionScanner::loadNameFilters (this=this@entry=0x7fffffffc1a0)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/collectionscanner.cpp:408
#16 0x00007ffff4ef2c13 in Digikam::CollectionScanner::mainEntryPoint (this=this@entry=0x7fffffffc1a0, complete=complete@entry=false)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/collectionscanner.cpp:806
#17 0x00007ffff4ef5284 in Digikam::CollectionScanner::scanFile (this=this@entry=0x7fffffffc1a0, fi=..., albumId=albumId@entry=847, imageId=imageId@entry=-1, 
    mode=mode@entry=Digikam::CollectionScanner::NormalScan) at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/collectionscanner.cpp:767
#18 0x00007ffff4ef929d in Digikam::CollectionScanner::scanFile (this=this@entry=0x7fffffffc1a0, albumRoot=..., album=..., fileName=..., 
    mode=mode@entry=Digikam::CollectionScanner::NormalScan) at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/collectionscanner.cpp:749
#19 0x00007ffff4ef975b in Digikam::CollectionScanner::scanFile (this=this@entry=0x7fffffffc1a0, filePath=..., mode=mode@entry=Digikam::CollectionScanner::NormalScan)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/libs/database/collectionscanner.cpp:718
#20 0x00000000005e2ab0 in Digikam::ScanController::scannedInfo (this=0xe01b90, filePath=...)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/digikam/database/scancontroller.cpp:555
#21 0x00000000004a2893 in Digikam::ImageWindow::saveAsIsComplete (this=0x3bbdc40)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/utilities/imageeditor/main/imagewindow.cpp:1013
#22 0x00007ffff5692acc in Digikam::EditorWindow::movingSaveFileFinished (this=this@entry=0x3bbdc40, successful=successful@entry=true)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/utilities/imageeditor/editor/editorwindow.cpp:1803
#23 0x00007ffff56a092b in Digikam::EditorWindow::moveFile (this=this@entry=0x3bbdc40)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/utilities/imageeditor/editor/editorwindow.cpp:2627
#24 0x00007ffff56a0f98 in Digikam::EditorWindow::slotSavingFinished (this=0x3bbdc40, filename=..., success=<optimized out>)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/utilities/imageeditor/editor/editorwindow.cpp:1765
#25 0x00007ffff2bb663f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#26 0x00007ffff56005d6 in Digikam::Canvas::signalSavingFinished (this=<optimized out>, _t1=..., _t2=true)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0_build/digikam/canvas.moc:298
#27 0x00007ffff2bb663f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#28 0x00007ffff56680b6 in Digikam::EditorCore::signalImageSaved (this=this@entry=0x3aba880, _t1=..., _t2=_t2@entry=true)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0_build/digikam/editorcore.moc:197
#29 0x00007ffff56702a3 in Digikam::EditorCore::slotImageSaved (this=0x3aba880, filePath=..., success=<optimized out>)
    at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/utilities/imageeditor/core/editorcore.cpp:451
#30 0x00007ffff2bbb9fe in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#31 0x00007ffff35ccb8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#32 0x00007ffff35cf5bf in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#33 0x00007ffff432a3aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#34 0x00007ffff2ba1ded in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#35 0x00007ffff2ba5420 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4                                                
#36 0x00007ffff2bd0713 in ?? () from /usr/lib64/qt4/libQtCore.so.4                                                                                                                     
#37 0x00007fffeafacdf4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0                                                                                                  
#38 0x00007fffeafad164 in ?? () from /usr/lib64/libglib-2.0.so.0                                                                                                                       
#39 0x00007fffeafad22c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0                                                                                                  
#40 0x00007ffff2bd0884 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4                                              
#41 0x00007ffff366e4c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4                                                                                                                        
#42 0x00007ffff2ba0a2f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4                                                         
#43 0x00007ffff2ba0d10 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4                                                                  
#44 0x00007ffff2ba5fc8 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4                                                                                                 
#45 0x0000000000497988 in main (argc=<optimized out>, argv=<optimized out>) at /var/tmp/portage/media-gfx/digikam-3.5.0/work/digikam-3.5.0/core/digikam/main/main.cpp:235   


On Fri, Dec 20, 2013 at 11:53 PM, Peter Albrecht <[hidden email]> wrote:
Hello Jim,

one reason for missing debug symbols under gentoo might be
the stripping, portage does at default.

Just adding "-ggdb" to your CFLAGS is not enough. You also
have to add "nostrip" or "splitdebug" to your FEATURES.

For details see:
> http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces#Stripping

Regards,
        Peter

On <a href="tel:20.12.2013%2018" value="+12012201318">20.12.2013 18:50, Jim Dory wrote:
> Thanks for info. I've compiled it with the debug use flag so will have to
> research it a bit to see how to get more debugging. Appreciate your work!
> cheers, Jim
>
>
> On Fri, Dec 20, 2013 at 12:20 AM, Gilles Caulier
> <[hidden email]>wrote:
>
>> It crash in Sqlite Qt driver. There is no reason for that, excepted if
>> binary compatibility is broken due to a recent update of system
>> package... It's the eternal problem under Linux if packager don't take
>> a care enough...
>>
>> Note : your digiKam is not compiled with debug symbols. There is no
>> source code from digiKam printed in GDB...
>>
>> Gilles Caulier
>>
>> 2013/12/20 Jim Dory <[hidden email]>:
>>> I have been very unstable since 3.5. I'm running Gentoo and unstable
>>> settings  ( ~amd_64) but haven't had any problem until this latest
>> digikam
>>> version.  KDE-4.12
>>>
>>> I can work several minutes and then it crashes. Not reproducible other
>> than
>>> just using it for a bit - nothing in particular seems to be the cause.
>>> Program just disappears - closes completely.
>>>
>>> I recompiled it with the debug use flag (compiled in debug) and I'll
>> give a
>>> little backtrace when it crashed - although this time it didn't just
>> close
>>> like usual.. but maybe that was from running it with gdb. This time it
>> just
>>> froze, and I see I had a seg fault. At the time I had just clicked on an
>>> image thumbnail in an album.
>>>
>>> I've also had problems with it not properly reading the thumbnails. I can
>>> fix a few of them by running "rebuild the thumbnails in current album"
>> but
>>> it won't fix them all and sometimes they revert to other image
>> thumbnails.
>>>
>>> I'm running the albums on a network attached storage, though the
>> database is
>>> on my home partition.
>>>
>>> Here's my component list followed by the 'bt':  (hope this helps - let me
>>> know what else you might want)
>>>
>>> digiKam version 3.5.0
>>> Demosaic GPL2 pack support: Yes
>>> Demosaic GPL3 pack support: Yes
>>> Exiv2 can write to Jp2: Yes
>>> Exiv2 can write to Jpeg: Yes
>>> Exiv2 can write to Pgf: Yes
>>> Exiv2 can write to Png: Yes
>>> Exiv2 can write to Tiff: Yes
>>> Exiv2 supports XMP metadata: Yes
>>> LibCImg: 130
>>> LibEigen: 3.1.3
>>> LibExiv2: 0.23
>>> LibJPEG: 62
>>> LibJasper: 1.900.1
>>> LibKDE: 4.12.0
>>> LibKExiv2: 2.3.1
>>> LibKGeoMap: 2.0.0
>>> LibKdcraw: 2.4.2
>>> LibLCMS: 2050
>>> LibLensFun: 0.2.8-0
>>> LibPGF: 6.12.27 - external shared library
>>> LibPNG: 1.6.7
>>> LibQt: 4.8.5
>>> LibRaw: 0.15.4
>>> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler
>>> Copyright (c) 1991-1996 Silicon Graphics, Inc.
>>> Marble Widget: 0.17.0 (stable version)
>>> Parallelized PGF codec: No
>>> Parallelized demosaicing: Yes
>>> RawSpeed codec support: Yes
>>> Database backend: QSQLITE
>>> Kipi-Plugins: 3.5.0
>>> LibKface: 3.0.0
>>> LibKipi: 2.1.0
>>> LibOpenCV: 2.4.6.1
>>>
>>>
>>>
>>> digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory:
>> Loading
>>> image history  ""
>>> [Thread 0x7fffb6b02700 (LWP 13427) exited]
>>> [Thread 0x7fff96c89700 (LWP 13428) exited]
>>> [Thread 0x7fffb7677700 (LWP 13429) exited]
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x0000000000000000 in ?? ()
>>> (gdb) bt
>>> #0  0x0000000000000000 in ?? ()
>>> #1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
>>> #2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
>>> #3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
>>> #4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
>>> #5  0x00007fffe09a5ed6 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
>>> #6  0x00007fffd4a52b4f in ?? () from
>>> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>>> #7  0x00007fffd4a538ef in ?? () from
>>> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>>> #8  0x00007ffff7bac687 in QSqlQuery::exec() () from
>>> /usr/lib64/qt4/libQtSql.so.4
>>> #9  0x00007ffff5511c86 in
>>> Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
>>> /usr/lib64/libdigikamcore.so.3
>>> #10 0x00007ffff5511d0c in
>>> Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant
>> const&)
>>> () from /usr/lib64/libdigikamcore.so.3
>>> #11 0x00007ffff5512b80 in Digikam::DatabaseCoreBackend::execQuery(QString
>>> const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
>>> #12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString
>>> const&, QVariant const&, QList<QVariant>*, QVariant*) () from
>>> /usr/lib64/libdigikamcore.so.3
>>> #13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&) ()
>>> from /usr/lib64/libdigikamdatabase.so.3
>>> #14 0x00007ffff4e804a9 in
>> Digikam::AlbumDB::getFilterSettings(QStringList*,
>>> QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
>>> #15 0x000000000065f9a5 in ?? ()
>>> #16 0x00000000005442e6 in ?? ()
>>> #17 0x0000000000543c54 in ?? ()
>>> #18 0x00007fff9415ae34 in ?? () from
>>> /usr/lib64/kde4/kipiplugin_advancedslideshow.so
>>> #19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>>> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>>> #20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) ()
>> from
>>> /usr/lib64/libkipi.so.11
>>> #21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>>> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>>> #22 0x00000000005bb724 in ?? ()
>>> #23 0x00000000005e39d5 in ?? ()
>>> #24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #25 0x00007ffff397925e in QFrame::event(QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) ()
>> from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #28 0x00000000005dad40 in ?? ()
>>> #29 0x00007ffff2b46f65 in
>>> QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*,
>> QEvent*) ()
>>> from /usr/lib64/qt4/libQtCore.so.4
>>> #30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*,
>>> QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
>>> #31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) () from
>>> /usr/lib64/libkdeui.so.5
>>> #33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*,
>>> QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
>>> #34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*,
>>> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
>>> from /usr/lib64/qt4/libQtGui.so.4
>>> #35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
>>> #36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) () from
>>> /usr/lib64/qt4/libQtGui.so.4
>>> #37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>>> #38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from
>>> /usr/lib64/libglib-2.0.so.0
>>> #39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
>>> #40 0x00007fffeaf6022c in g_main_context_iteration () from
>>> /usr/lib64/libglib-2.0.so.0
>>> #41 0x00007ffff2b75884 in
>>>
>> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>> () from /usr/lib64/qt4/libQtCore.so.4
>>> #42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>>> #43 0x00007ffff2b45a2f in
>>> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
>>> /usr/lib64/qt4/libQtCore.so.4
>>> #44 0x00007ffff2b45d10 in
>>> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
>>> /usr/lib64/qt4/libQtCore.so.4
>>> #45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from
>>> /usr/lib64/qt4/libQtCore.so.4
>>> #46 0x0000000000497a3c in ?? ()
>>> #47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
>>> #48 0x000000000049a151 in _start ()
>>> (gdb) quit
>>> A debugging session is active.
>>>
>>>         Inferior 1 [process 13284] will be killed.
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> _______________________________________________
> 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


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Jim Dory-2
In reply to this post by Gilles Caulier-4
Happy New Year Gilles,

Does digikam need sqlite3 for gentoo, do you know? This page seems to suggest that:

On my system I have sqlite installed, but not sqlite3. I may go ahead and install that, but wondering if it will fix my thumbnails and crashing problem.

cheers, Jim


On Fri, Dec 20, 2013 at 12:20 AM, Gilles Caulier <[hidden email]> wrote:
It crash in Sqlite Qt driver. There is no reason for that, excepted if
binary compatibility is broken due to a recent update of system
package... It's the eternal problem under Linux if packager don't take
a care enough...

Note : your digiKam is not compiled with debug symbols. There is no
source code from digiKam printed in GDB...

Gilles Caulier

2013/12/20 Jim Dory <[hidden email]>:
> I have been very unstable since 3.5. I'm running Gentoo and unstable
> settings  ( ~amd_64) but haven't had any problem until this latest digikam
> version.  KDE-4.12
>
> I can work several minutes and then it crashes. Not reproducible other than
> just using it for a bit - nothing in particular seems to be the cause.
> Program just disappears - closes completely.
>
> I recompiled it with the debug use flag (compiled in debug) and I'll give a
> little backtrace when it crashed - although this time it didn't just close
> like usual.. but maybe that was from running it with gdb. This time it just
> froze, and I see I had a seg fault. At the time I had just clicked on an
> image thumbnail in an album.
>
> I've also had problems with it not properly reading the thumbnails. I can
> fix a few of them by running "rebuild the thumbnails in current album" but
> it won't fix them all and sometimes they revert to other image thumbnails.
>
> I'm running the albums on a network attached storage, though the database is
> on my home partition.
>
> Here's my component list followed by the 'bt':  (hope this helps - let me
> know what else you might want)
>
> digiKam version 3.5.0
> Demosaic GPL2 pack support: Yes
> Demosaic GPL3 pack support: Yes
> Exiv2 can write to Jp2: Yes
> Exiv2 can write to Jpeg: Yes
> Exiv2 can write to Pgf: Yes
> Exiv2 can write to Png: Yes
> Exiv2 can write to Tiff: Yes
> Exiv2 supports XMP metadata: Yes
> LibCImg: 130
> LibEigen: 3.1.3
> LibExiv2: 0.23
> LibJPEG: 62
> LibJasper: 1.900.1
> LibKDE: 4.12.0
> LibKExiv2: 2.3.1
> LibKGeoMap: 2.0.0
> LibKdcraw: 2.4.2
> LibLCMS: 2050
> LibLensFun: 0.2.8-0
> LibPGF: 6.12.27 - external shared library
> LibPNG: 1.6.7
> LibQt: 4.8.5
> LibRaw: 0.15.4
> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler
> Copyright (c) 1991-1996 Silicon Graphics, Inc.
> Marble Widget: 0.17.0 (stable version)
> Parallelized PGF codec: No
> Parallelized demosaicing: Yes
> RawSpeed codec support: Yes
> Database backend: QSQLITE
> Kipi-Plugins: 3.5.0
> LibKface: 3.0.0
> LibKipi: 2.1.0
> LibOpenCV: 2.4.6.1
>
>
>
> digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory: Loading
> image history  ""
> [Thread 0x7fffb6b02700 (LWP 13427) exited]
> [Thread 0x7fff96c89700 (LWP 13428) exited]
> [Thread 0x7fffb7677700 (LWP 13429) exited]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0  0x0000000000000000 in ?? ()
> #1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
> #2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
> #3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
> #4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
> #5  0x00007fffe09a5ed6 in sqlite3_step () from /usr/lib64/libsqlite3.so.0
> #6  0x00007fffd4a52b4f in ?? () from
> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
> #7  0x00007fffd4a538ef in ?? () from
> /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
> #8  0x00007ffff7bac687 in QSqlQuery::exec() () from
> /usr/lib64/qt4/libQtSql.so.4
> #9  0x00007ffff5511c86 in
> Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
> /usr/lib64/libdigikamcore.so.3
> #10 0x00007ffff5511d0c in
> Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant const&)
> () from /usr/lib64/libdigikamcore.so.3
> #11 0x00007ffff5512b80 in Digikam::DatabaseCoreBackend::execQuery(QString
> const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
> #12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString
> const&, QVariant const&, QList<QVariant>*, QVariant*) () from
> /usr/lib64/libdigikamcore.so.3
> #13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&) ()
> from /usr/lib64/libdigikamdatabase.so.3
> #14 0x00007ffff4e804a9 in Digikam::AlbumDB::getFilterSettings(QStringList*,
> QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
> #15 0x000000000065f9a5 in ?? ()
> #16 0x00000000005442e6 in ?? ()
> #17 0x0000000000543c54 in ?? ()
> #18 0x00007fff9415ae34 in ?? () from
> /usr/lib64/kde4/kipiplugin_advancedslideshow.so
> #19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
> #20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) () from
> /usr/lib64/libkipi.so.11
> #21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
> const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
> #22 0x00000000005bb724 in ?? ()
> #23 0x00000000005e39d5 in ?? ()
> #24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #25 0x00007ffff397925e in QFrame::event(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #28 0x00000000005dad40 in ?? ()
> #29 0x00007ffff2b46f65 in
> QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
> from /usr/lib64/qt4/libQtCore.so.4
> #30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
> #31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) () from
> /usr/lib64/libkdeui.so.5
> #33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*,
> QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
> #34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*,
> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
> from /usr/lib64/qt4/libQtGui.so.4
> #35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) () from
> /usr/lib64/qt4/libQtGui.so.4
> #37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from
> /usr/lib64/libglib-2.0.so.0
> #39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
> #40 0x00007fffeaf6022c in g_main_context_iteration () from
> /usr/lib64/libglib-2.0.so.0
> #41 0x00007ffff2b75884 in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () from /usr/lib64/qt4/libQtCore.so.4
> #42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
> #43 0x00007ffff2b45a2f in
> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib64/qt4/libQtCore.so.4
> #44 0x00007ffff2b45d10 in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib64/qt4/libQtCore.so.4
> #45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from
> /usr/lib64/qt4/libQtCore.so.4
> #46 0x0000000000497a3c in ?? ()
> #47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
> #48 0x000000000049a151 in _start ()
> (gdb) quit
> A debugging session is active.
>
>         Inferior 1 [process 13284] will be killed.
>
>
> _______________________________________________
> 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


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Gilles Caulier-4
yes, you need SQlite3 Qt plugin... not SQlite directly. We use Qt DB SDK

Gilles Caulier

2014/1/2 Jim Dory <[hidden email]>:

> Happy New Year Gilles,
>
> Does digikam need sqlite3 for gentoo, do you know? This page seems to
> suggest that:
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README
>
> On my system I have sqlite installed, but not sqlite3. I may go ahead and
> install that, but wondering if it will fix my thumbnails and crashing
> problem.
>
> cheers, Jim
>
>
> On Fri, Dec 20, 2013 at 12:20 AM, Gilles Caulier <[hidden email]>
> wrote:
>>
>> It crash in Sqlite Qt driver. There is no reason for that, excepted if
>> binary compatibility is broken due to a recent update of system
>> package... It's the eternal problem under Linux if packager don't take
>> a care enough...
>>
>> Note : your digiKam is not compiled with debug symbols. There is no
>> source code from digiKam printed in GDB...
>>
>> Gilles Caulier
>>
>> 2013/12/20 Jim Dory <[hidden email]>:
>> > I have been very unstable since 3.5. I'm running Gentoo and unstable
>> > settings  ( ~amd_64) but haven't had any problem until this latest
>> > digikam
>> > version.  KDE-4.12
>> >
>> > I can work several minutes and then it crashes. Not reproducible other
>> > than
>> > just using it for a bit - nothing in particular seems to be the cause.
>> > Program just disappears - closes completely.
>> >
>> > I recompiled it with the debug use flag (compiled in debug) and I'll
>> > give a
>> > little backtrace when it crashed - although this time it didn't just
>> > close
>> > like usual.. but maybe that was from running it with gdb. This time it
>> > just
>> > froze, and I see I had a seg fault. At the time I had just clicked on an
>> > image thumbnail in an album.
>> >
>> > I've also had problems with it not properly reading the thumbnails. I
>> > can
>> > fix a few of them by running "rebuild the thumbnails in current album"
>> > but
>> > it won't fix them all and sometimes they revert to other image
>> > thumbnails.
>> >
>> > I'm running the albums on a network attached storage, though the
>> > database is
>> > on my home partition.
>> >
>> > Here's my component list followed by the 'bt':  (hope this helps - let
>> > me
>> > know what else you might want)
>> >
>> > digiKam version 3.5.0
>> > Demosaic GPL2 pack support: Yes
>> > Demosaic GPL3 pack support: Yes
>> > Exiv2 can write to Jp2: Yes
>> > Exiv2 can write to Jpeg: Yes
>> > Exiv2 can write to Pgf: Yes
>> > Exiv2 can write to Png: Yes
>> > Exiv2 can write to Tiff: Yes
>> > Exiv2 supports XMP metadata: Yes
>> > LibCImg: 130
>> > LibEigen: 3.1.3
>> > LibExiv2: 0.23
>> > LibJPEG: 62
>> > LibJasper: 1.900.1
>> > LibKDE: 4.12.0
>> > LibKExiv2: 2.3.1
>> > LibKGeoMap: 2.0.0
>> > LibKdcraw: 2.4.2
>> > LibLCMS: 2050
>> > LibLensFun: 0.2.8-0
>> > LibPGF: 6.12.27 - external shared library
>> > LibPNG: 1.6.7
>> > LibQt: 4.8.5
>> > LibRaw: 0.15.4
>> > LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler
>> > Copyright (c) 1991-1996 Silicon Graphics, Inc.
>> > Marble Widget: 0.17.0 (stable version)
>> > Parallelized PGF codec: No
>> > Parallelized demosaicing: Yes
>> > RawSpeed codec support: Yes
>> > Database backend: QSQLITE
>> > Kipi-Plugins: 3.5.0
>> > LibKface: 3.0.0
>> > LibKipi: 2.1.0
>> > LibOpenCV: 2.4.6.1
>> >
>> >
>> >
>> > digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory:
>> > Loading
>> > image history  ""
>> > [Thread 0x7fffb6b02700 (LWP 13427) exited]
>> > [Thread 0x7fff96c89700 (LWP 13428) exited]
>> > [Thread 0x7fffb7677700 (LWP 13429) exited]
>> >
>> > Program received signal SIGSEGV, Segmentation fault.
>> > 0x0000000000000000 in ?? ()
>> > (gdb) bt
>> > #0  0x0000000000000000 in ?? ()
>> > #1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
>> > #2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
>> > #3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
>> > #4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
>> > #5  0x00007fffe09a5ed6 in sqlite3_step () from
>> > /usr/lib64/libsqlite3.so.0
>> > #6  0x00007fffd4a52b4f in ?? () from
>> > /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>> > #7  0x00007fffd4a538ef in ?? () from
>> > /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>> > #8  0x00007ffff7bac687 in QSqlQuery::exec() () from
>> > /usr/lib64/qt4/libQtSql.so.4
>> > #9  0x00007ffff5511c86 in
>> > Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
>> > /usr/lib64/libdigikamcore.so.3
>> > #10 0x00007ffff5511d0c in
>> > Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant
>> > const&)
>> > () from /usr/lib64/libdigikamcore.so.3
>> > #11 0x00007ffff5512b80 in
>> > Digikam::DatabaseCoreBackend::execQuery(QString
>> > const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
>> > #12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString
>> > const&, QVariant const&, QList<QVariant>*, QVariant*) () from
>> > /usr/lib64/libdigikamcore.so.3
>> > #13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&)
>> > ()
>> > from /usr/lib64/libdigikamdatabase.so.3
>> > #14 0x00007ffff4e804a9 in
>> > Digikam::AlbumDB::getFilterSettings(QStringList*,
>> > QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
>> > #15 0x000000000065f9a5 in ?? ()
>> > #16 0x00000000005442e6 in ?? ()
>> > #17 0x0000000000543c54 in ?? ()
>> > #18 0x00007fff9415ae34 in ?? () from
>> > /usr/lib64/kde4/kipiplugin_advancedslideshow.so
>> > #19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>> > const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>> > #20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) ()
>> > from
>> > /usr/lib64/libkipi.so.11
>> > #21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>> > const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>> > #22 0x00000000005bb724 in ?? ()
>> > #23 0x00000000005e39d5 in ?? ()
>> > #24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #25 0x00007ffff397925e in QFrame::event(QEvent*) () from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) ()
>> > from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #28 0x00000000005dad40 in ?? ()
>> > #29 0x00007ffff2b46f65 in
>> > QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*,
>> > QEvent*) ()
>> > from /usr/lib64/qt4/libQtCore.so.4
>> > #30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*,
>> > QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
>> > #31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) ()
>> > from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) ()
>> > from
>> > /usr/lib64/libkdeui.so.5
>> > #33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*,
>> > QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
>> > #34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*,
>> > QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)
>> > ()
>> > from /usr/lib64/qt4/libQtGui.so.4
>> > #35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
>> > #36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) ()
>> > from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>> > #38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from
>> > /usr/lib64/libglib-2.0.so.0
>> > #39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
>> > #40 0x00007fffeaf6022c in g_main_context_iteration () from
>> > /usr/lib64/libglib-2.0.so.0
>> > #41 0x00007ffff2b75884 in
>> >
>> > QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>> > () from /usr/lib64/qt4/libQtCore.so.4
>> > #42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>> > #43 0x00007ffff2b45a2f in
>> > QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
>> > /usr/lib64/qt4/libQtCore.so.4
>> > #44 0x00007ffff2b45d10 in
>> > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
>> > /usr/lib64/qt4/libQtCore.so.4
>> > #45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from
>> > /usr/lib64/qt4/libQtCore.so.4
>> > #46 0x0000000000497a3c in ?? ()
>> > #47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
>> > #48 0x000000000049a151 in _start ()
>> > (gdb) quit
>> > A debugging session is active.
>> >
>> >         Inferior 1 [process 13284] will be killed.
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
>
> _______________________________________________
> 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
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Jim Dory-2
Ok, I may have it already as my version is sqlite-3.8.2

I did enable a sqlite3 USE flag in the make.conf but when doing an "emerge -avuND @world" no package picks it up. There is a dev-ruby/sqlite3 that says this: "An extension library to access a SQLite database from Ruby" so not sure that would do anything for me. Thanks much for the response.  cheers, Jim


On Thu, Jan 2, 2014 at 12:25 PM, Gilles Caulier <[hidden email]> wrote:
yes, you need SQlite3 Qt plugin... not SQlite directly. We use Qt DB SDK

Gilles Caulier

2014/1/2 Jim Dory <[hidden email]>:
> Happy New Year Gilles,
>
> Does digikam need sqlite3 for gentoo, do you know? This page seems to
> suggest that:
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README
>
> On my system I have sqlite installed, but not sqlite3. I may go ahead and
> install that, but wondering if it will fix my thumbnails and crashing
> problem.
>
> cheers, Jim
>
>
> On Fri, Dec 20, 2013 at 12:20 AM, Gilles Caulier <[hidden email]>
> wrote:
>>
>> It crash in Sqlite Qt driver. There is no reason for that, excepted if
>> binary compatibility is broken due to a recent update of system
>> package... It's the eternal problem under Linux if packager don't take
>> a care enough...
>>
>> Note : your digiKam is not compiled with debug symbols. There is no
>> source code from digiKam printed in GDB...
>>
>> Gilles Caulier
>>
>> 2013/12/20 Jim Dory <[hidden email]>:
>> > I have been very unstable since 3.5. I'm running Gentoo and unstable
>> > settings  ( ~amd_64) but haven't had any problem until this latest
>> > digikam
>> > version.  KDE-4.12
>> >
>> > I can work several minutes and then it crashes. Not reproducible other
>> > than
>> > just using it for a bit - nothing in particular seems to be the cause.
>> > Program just disappears - closes completely.
>> >
>> > I recompiled it with the debug use flag (compiled in debug) and I'll
>> > give a
>> > little backtrace when it crashed - although this time it didn't just
>> > close
>> > like usual.. but maybe that was from running it with gdb. This time it
>> > just
>> > froze, and I see I had a seg fault. At the time I had just clicked on an
>> > image thumbnail in an album.
>> >
>> > I've also had problems with it not properly reading the thumbnails. I
>> > can
>> > fix a few of them by running "rebuild the thumbnails in current album"
>> > but
>> > it won't fix them all and sometimes they revert to other image
>> > thumbnails.
>> >
>> > I'm running the albums on a network attached storage, though the
>> > database is
>> > on my home partition.
>> >
>> > Here's my component list followed by the 'bt':  (hope this helps - let
>> > me
>> > know what else you might want)
>> >
>> > digiKam version 3.5.0
>> > Demosaic GPL2 pack support: Yes
>> > Demosaic GPL3 pack support: Yes
>> > Exiv2 can write to Jp2: Yes
>> > Exiv2 can write to Jpeg: Yes
>> > Exiv2 can write to Pgf: Yes
>> > Exiv2 can write to Png: Yes
>> > Exiv2 can write to Tiff: Yes
>> > Exiv2 supports XMP metadata: Yes
>> > LibCImg: 130
>> > LibEigen: 3.1.3
>> > LibExiv2: 0.23
>> > LibJPEG: 62
>> > LibJasper: 1.900.1
>> > LibKDE: 4.12.0
>> > LibKExiv2: 2.3.1
>> > LibKGeoMap: 2.0.0
>> > LibKdcraw: 2.4.2
>> > LibLCMS: 2050
>> > LibLensFun: 0.2.8-0
>> > LibPGF: 6.12.27 - external shared library
>> > LibPNG: 1.6.7
>> > LibQt: 4.8.5
>> > LibRaw: 0.15.4
>> > LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler
>> > Copyright (c) 1991-1996 Silicon Graphics, Inc.
>> > Marble Widget: 0.17.0 (stable version)
>> > Parallelized PGF codec: No
>> > Parallelized demosaicing: Yes
>> > RawSpeed codec support: Yes
>> > Database backend: QSQLITE
>> > Kipi-Plugins: 3.5.0
>> > LibKface: 3.0.0
>> > LibKipi: 2.1.0
>> > LibOpenCV: 2.4.6.1
>> >
>> >
>> >
>> > digikam(13284)/digikam (core) Digikam::DMetadata::getImageHistory:
>> > Loading
>> > image history  ""
>> > [Thread 0x7fffb6b02700 (LWP 13427) exited]
>> > [Thread 0x7fff96c89700 (LWP 13428) exited]
>> > [Thread 0x7fffb7677700 (LWP 13429) exited]
>> >
>> > Program received signal SIGSEGV, Segmentation fault.
>> > 0x0000000000000000 in ?? ()
>> > (gdb) bt
>> > #0  0x0000000000000000 in ?? ()
>> > #1  0x00007fffe096fa9e in ?? () from /usr/lib64/libsqlite3.so.0
>> > #2  0x00007fffe096fe30 in ?? () from /usr/lib64/libsqlite3.so.0
>> > #3  0x00007fffe0994bbd in ?? () from /usr/lib64/libsqlite3.so.0
>> > #4  0x00007fffe099d6c5 in ?? () from /usr/lib64/libsqlite3.so.0
>> > #5  0x00007fffe09a5ed6 in sqlite3_step () from
>> > /usr/lib64/libsqlite3.so.0
>> > #6  0x00007fffd4a52b4f in ?? () from
>> > /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>> > #7  0x00007fffd4a538ef in ?? () from
>> > /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
>> > #8  0x00007ffff7bac687 in QSqlQuery::exec() () from
>> > /usr/lib64/qt4/libQtSql.so.4
>> > #9  0x00007ffff5511c86 in
>> > Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
>> > /usr/lib64/libdigikamcore.so.3
>> > #10 0x00007ffff5511d0c in
>> > Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant
>> > const&)
>> > () from /usr/lib64/libdigikamcore.so.3
>> > #11 0x00007ffff5512b80 in
>> > Digikam::DatabaseCoreBackend::execQuery(QString
>> > const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
>> > #12 0x00007ffff5512bc9 in Digikam::DatabaseCoreBackend::execSql(QString
>> > const&, QVariant const&, QList<QVariant>*, QVariant*) () from
>> > /usr/lib64/libdigikamcore.so.3
>> > #13 0x00007ffff4e7fb6e in Digikam::AlbumDB::getSetting(QString const&)
>> > ()
>> > from /usr/lib64/libdigikamdatabase.so.3
>> > #14 0x00007ffff4e804a9 in
>> > Digikam::AlbumDB::getFilterSettings(QStringList*,
>> > QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
>> > #15 0x000000000065f9a5 in ?? ()
>> > #16 0x00000000005442e6 in ?? ()
>> > #17 0x0000000000543c54 in ?? ()
>> > #18 0x00007fff9415ae34 in ?? () from
>> > /usr/lib64/kde4/kipiplugin_advancedslideshow.so
>> > #19 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>> > const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>> > #20 0x00007ffff5eb5012 in KIPI::Interface::currentAlbumChanged(bool) ()
>> > from
>> > /usr/lib64/libkipi.so.11
>> > #21 0x00007ffff2b5b63f in QMetaObject::activate(QObject*, QMetaObject
>> > const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
>> > #22 0x00000000005bb724 in ?? ()
>> > #23 0x00000000005e39d5 in ?? ()
>> > #24 0x00007ffff35bf75a in QWidget::event(QEvent*) () from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #25 0x00007ffff397925e in QFrame::event(QEvent*) () from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #26 0x00007ffff3a9086b in QAbstractItemView::viewportEvent(QEvent*) ()
>> > from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #27 0x00007ffff3ad0816 in QTreeView::viewportEvent(QEvent*) () from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #28 0x00000000005dad40 in ?? ()
>> > #29 0x00007ffff2b46f65 in
>> > QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*,
>> > QEvent*) ()
>> > from /usr/lib64/qt4/libQtCore.so.4
>> > #30 0x00007ffff3571b6c in QApplicationPrivate::notify_helper(QObject*,
>> > QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
>> > #31 0x00007ffff3574e31 in QApplication::notify(QObject*, QEvent*) ()
>> > from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #32 0x00007ffff42cf3aa in KApplication::notify(QObject*, QEvent*) ()
>> > from
>> > /usr/lib64/libkdeui.so.5
>> > #33 0x00007ffff2b46ded in QCoreApplication::notifyInternal(QObject*,
>> > QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
>> > #34 0x00007ffff3577ce2 in QApplicationPrivate::sendMouseEvent(QWidget*,
>> > QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)
>> > ()
>> > from /usr/lib64/qt4/libQtGui.so.4
>> > #35 0x00007ffff35ebe9c in ?? () from /usr/lib64/qt4/libQtGui.so.4
>> > #36 0x00007ffff35ea7e1 in QApplication::x11ProcessEvent(_XEvent*) ()
>> > from
>> > /usr/lib64/qt4/libQtGui.so.4
>> > #37 0x00007ffff36133e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>> > #38 0x00007fffeaf5fdf4 in g_main_context_dispatch () from
>> > /usr/lib64/libglib-2.0.so.0
>> > #39 0x00007fffeaf60164 in ?? () from /usr/lib64/libglib-2.0.so.0
>> > #40 0x00007fffeaf6022c in g_main_context_iteration () from
>> > /usr/lib64/libglib-2.0.so.0
>> > #41 0x00007ffff2b75884 in
>> >
>> > QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>> > () from /usr/lib64/qt4/libQtCore.so.4
>> > #42 0x00007ffff36134c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
>> > #43 0x00007ffff2b45a2f in
>> > QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
>> > /usr/lib64/qt4/libQtCore.so.4
>> > #44 0x00007ffff2b45d10 in
>> > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
>> > /usr/lib64/qt4/libQtCore.so.4
>> > #45 0x00007ffff2b4afc8 in QCoreApplication::exec() () from
>> > /usr/lib64/qt4/libQtCore.so.4
>> > #46 0x0000000000497a3c in ?? ()
>> > #47 0x00007ffff1b9bb8d in __libc_start_main () from /lib64/libc.so.6
>> > #48 0x000000000049a151 in _start ()
>> > (gdb) quit
>> > A debugging session is active.
>> >
>> >         Inferior 1 [process 13284] will be killed.
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
>
> _______________________________________________
> 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


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Peter Albrecht
Hi Jim,

on my gentoo system "dev-ruby/sqlite3" is not installed and
digikam works fine with sqlite datebase. So I guess, you
don't need it.

I am no gentoo expert, but
"/usr/portage/media-gfx/digikam/digikam-3.5.0.ebuild"
says:
> CDEPEND="... || ( dev-qt/qtsql:4[mysql] dev-qt/qtsql:4[sqlite] ) ..."

I would read this: You need QtSQL (slot 4) with USE-Flag
"mysql" or "sqlite" enabled.

While "/usr/portage/dev-qt/qtsql/qtsql-4.8.5.ebuild" says:
> DEPEND="... sqlite? ( dev-db/sqlite:3 )"

Which, I would read like: I you enable "sqlite" USE-Flag,
install "dev-db/sqlite slot 3".
And "eix ^sqlite$" tells you, slot 3 contains version 3.7.x
and 3.8.x.

To sum up:
If build dev-qt/qtsql with USE-Flag sqlite, sqlite 3.x will
be installed automatically.

I use at the moment:
 - media-gfx/digikam-3.5.0
 - dev-db/sqlite-3.7.17
 - dev-qt/qtsql-4.8.5

This works fine for me. Maybe you try these versions.


As for gentoo in general:
Maybe you missed some step at your last system update. Wenn
I do updates, I go through the following steps:

 1) eix-sync   or   emerge --sync; eix-update

 2) emerge -vpt --update --newuse --deep world

 3) check elogs (if enabled) with "elogv"

 4) emerge -va @preserved-rebuild

 5) emerge -va --depclean

 6) revdep-rebuild -i

 7) eclean-dist --destructive

 8) dispatch-conf


Regards,
        Peter


On 02.01.2014 23:33, Jim Dory wrote:

> Ok, I may have it already as my version is sqlite-3.8.2
>
> I did enable a sqlite3 USE flag in the make.conf but when doing an "emerge
> -avuND @world" no package picks it up. There is a dev-ruby/sqlite3 that
> says this: "An extension library to access a SQLite database from Ruby" so
> not sure that would do anything for me. Thanks much for the response.
>  cheers, Jim
>
>
> On Thu, Jan 2, 2014 at 12:25 PM, Gilles Caulier <[hidden email]>wrote:
>
>> yes, you need SQlite3 Qt plugin... not SQlite directly. We use Qt DB SDK
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Jim Dory-2
Peter, thanks for informative reply.

1) I don't use eix - I'll give it a try.
2) I always use emerge -avuND @world when updating.
3) I have the elogs emailed me automatically so I can read each one.
4) yes, but only when it asks
5) depclean not as often as I should, but occasionally
6) first go-to when I have a problem, usually doesn't have anything to fix these days.
7) when my root partition starts filling up I do this.
8) when it asks, not as matter of course.

I will say I may have fixed problem but haven't had time to play around much to be sure. Possibly things are still broken, but I am finally able to get some accurate thumbnails. I will see what happens when I tag some - that was throwing the thumbnails off previously.

What I did was try to build an ebuild with digikam-4.0.0.beta1 but it would fail during the compile. So I went ahead and as my user (not root) installed it via "make && make install [as root]" in my home/Opt directory. However, I forgot about specifying an install directory so it installed globally. Oops.

I had the exact same problem with the beta version so uninstalled it using the make uninstall command. That removed a lot of KDE libraries, which I reinstalled using my sets (i.e.: emerge -av @kdegraphics) and a few others. So I'm back on dk 3.5, and it seems to be behaving better now.

Not sure why I was having trouble with the dk beta1 ebuild, but that would be another thread I guess and maybe something for the gentoo forums. 


On Fri, Jan 3, 2014 at 12:04 AM, Peter Albrecht <[hidden email]> wrote:
Hi Jim,

on my gentoo system "dev-ruby/sqlite3" is not installed and
digikam works fine with sqlite datebase. So I guess, you
don't need it.

I am no gentoo expert, but
"/usr/portage/media-gfx/digikam/digikam-3.5.0.ebuild"
says:
> CDEPEND="... || ( dev-qt/qtsql:4[mysql] dev-qt/qtsql:4[sqlite] ) ..."

I would read this: You need QtSQL (slot 4) with USE-Flag
"mysql" or "sqlite" enabled.

While "/usr/portage/dev-qt/qtsql/qtsql-4.8.5.ebuild" says:
> DEPEND="... sqlite? ( dev-db/sqlite:3 )"

Which, I would read like: I you enable "sqlite" USE-Flag,
install "dev-db/sqlite slot 3".
And "eix ^sqlite$" tells you, slot 3 contains version 3.7.x
and 3.8.x.

To sum up:
If build dev-qt/qtsql with USE-Flag sqlite, sqlite 3.x will
be installed automatically.

I use at the moment:
 - media-gfx/digikam-3.5.0
 - dev-db/sqlite-3.7.17
 - dev-qt/qtsql-4.8.5

This works fine for me. Maybe you try these versions.


As for gentoo in general:
Maybe you missed some step at your last system update. Wenn
I do updates, I go through the following steps:

 1) eix-sync   or   emerge --sync; eix-update

 2) emerge -vpt --update --newuse --deep world

 3) check elogs (if enabled) with "elogv"

 4) emerge -va @preserved-rebuild

 5) emerge -va --depclean

 6) revdep-rebuild -i

 7) eclean-dist --destructive

 8) dispatch-conf


Regards,
        Peter


On 02.01.2014 23:33, Jim Dory wrote:
> Ok, I may have it already as my version is sqlite-3.8.2
>
> I did enable a sqlite3 USE flag in the make.conf but when doing an "emerge
> -avuND @world" no package picks it up. There is a dev-ruby/sqlite3 that
> says this: "An extension library to access a SQLite database from Ruby" so
> not sure that would do anything for me. Thanks much for the response.
>  cheers, Jim
>
>
> On Thu, Jan 2, 2014 at 12:25 PM, Gilles Caulier <[hidden email]>wrote:
>
>> yes, you need SQlite3 Qt plugin... not SQlite directly. We use Qt DB SDK
_______________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Jim Dory-2
Peter,

Just an FYI, the DK-3.5 is still crashing on me but the thumbnails are tamed down a bit. I did try again to build DK-4.0.0-beta1 by renaming the 3.5 ebuild into my local overlay and pointing it at the tarball. I get about 41% compiled before the first error. I googled it but found nothing. For what its worth here's the errors:

/var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/xmpwidget.cpp:126:44: error: no matching function for call to 'Digikam::DMetadata::getXmpTagsDataList()'
     setMetadataMap(data.getXmpTagsDataList());

<snip>

/usr/include/libkexiv2/kexiv2.h:810:25: note:   candidate expects 2 arguments, 0 provided
digikam/CMakeFiles/digikamcore.dir/build.make:5199: recipe for target 'digikam/CMakeFiles/digikamcore.dir/__/libs/widgets/metadata/xmpwidget.o' failed
make[2]: *** [digikam/CMakeFiles/digikamcore.dir/__/libs/widgets/metadata/xmpwidget.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/exifwidget.cpp: In member function 'virtual bool Digikam::ExifWidget::decodeMetadata()':
/var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/exifwidget.cpp:115:45: error: no matching function for call to 'Digikam::DMetadata::getExifTagsDataList()'
     setMetadataMap(data.getExifTagsDataList());

Could be something in my ebuild I used from 3.5. Or I'm missing something.   cheers, JD







On Fri, Jan 3, 2014 at 1:16 PM, Jim Dory <[hidden email]> wrote:
Peter, thanks for informative reply.

1) I don't use eix - I'll give it a try.
2) I always use emerge -avuND @world when updating.
3) I have the elogs emailed me automatically so I can read each one.
4) yes, but only when it asks
5) depclean not as often as I should, but occasionally
6) first go-to when I have a problem, usually doesn't have anything to fix these days.
7) when my root partition starts filling up I do this.
8) when it asks, not as matter of course.

I will say I may have fixed problem but haven't had time to play around much to be sure. Possibly things are still broken, but I am finally able to get some accurate thumbnails. I will see what happens when I tag some - that was throwing the thumbnails off previously.

What I did was try to build an ebuild with digikam-4.0.0.beta1 but it would fail during the compile. So I went ahead and as my user (not root) installed it via "make && make install [as root]" in my home/Opt directory. However, I forgot about specifying an install directory so it installed globally. Oops.

I had the exact same problem with the beta version so uninstalled it using the make uninstall command. That removed a lot of KDE libraries, which I reinstalled using my sets (i.e.: emerge -av @kdegraphics) and a few others. So I'm back on dk 3.5, and it seems to be behaving better now.

Not sure why I was having trouble with the dk beta1 ebuild, but that would be another thread I guess and maybe something for the gentoo forums. 


On Fri, Jan 3, 2014 at 12:04 AM, Peter Albrecht <[hidden email]> wrote:
Hi Jim,

on my gentoo system "dev-ruby/sqlite3" is not installed and
digikam works fine with sqlite datebase. So I guess, you
don't need it.

I am no gentoo expert, but
"/usr/portage/media-gfx/digikam/digikam-3.5.0.ebuild"
says:
> CDEPEND="... || ( dev-qt/qtsql:4[mysql] dev-qt/qtsql:4[sqlite] ) ..."

I would read this: You need QtSQL (slot 4) with USE-Flag
"mysql" or "sqlite" enabled.

While "/usr/portage/dev-qt/qtsql/qtsql-4.8.5.ebuild" says:
> DEPEND="... sqlite? ( dev-db/sqlite:3 )"

Which, I would read like: I you enable "sqlite" USE-Flag,
install "dev-db/sqlite slot 3".
And "eix ^sqlite$" tells you, slot 3 contains version 3.7.x
and 3.8.x.

To sum up:
If build dev-qt/qtsql with USE-Flag sqlite, sqlite 3.x will
be installed automatically.

I use at the moment:
 - media-gfx/digikam-3.5.0
 - dev-db/sqlite-3.7.17
 - dev-qt/qtsql-4.8.5

This works fine for me. Maybe you try these versions.


As for gentoo in general:
Maybe you missed some step at your last system update. Wenn
I do updates, I go through the following steps:

 1) eix-sync   or   emerge --sync; eix-update

 2) emerge -vpt --update --newuse --deep world

 3) check elogs (if enabled) with "elogv"

 4) emerge -va @preserved-rebuild

 5) emerge -va --depclean

 6) revdep-rebuild -i

 7) eclean-dist --destructive

 8) dispatch-conf


Regards,
        Peter


On 02.01.2014 23:33, Jim Dory wrote:
> Ok, I may have it already as my version is sqlite-3.8.2
>
> I did enable a sqlite3 USE flag in the make.conf but when doing an "emerge
> -avuND @world" no package picks it up. There is a dev-ruby/sqlite3 that
> says this: "An extension library to access a SQLite database from Ruby" so
> not sure that would do anything for me. Thanks much for the response.
>  cheers, Jim
>
>
> On Thu, Jan 2, 2014 at 12:25 PM, Gilles Caulier <[hidden email]>wrote:
>
>> yes, you need SQlite3 Qt plugin... not SQlite directly. We use Qt DB SDK
_______________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Gilles Caulier-4
This compilation problem is fixed in current implementation, planed for beta2

Gilles Caulier

2014/1/4 Jim Dory <[hidden email]>:

> Peter,
>
> Just an FYI, the DK-3.5 is still crashing on me but the thumbnails are tamed
> down a bit. I did try again to build DK-4.0.0-beta1 by renaming the 3.5
> ebuild into my local overlay and pointing it at the tarball. I get about 41%
> compiled before the first error. I googled it but found nothing. For what
> its worth here's the errors:
>
> /var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/xmpwidget.cpp:126:44:
> error: no matching function for call to
> 'Digikam::DMetadata::getXmpTagsDataList()'
>      setMetadataMap(data.getXmpTagsDataList());
>
> <snip>
>
> /usr/include/libkexiv2/kexiv2.h:810:25: note:   candidate expects 2
> arguments, 0 provided
> digikam/CMakeFiles/digikamcore.dir/build.make:5199: recipe for target
> 'digikam/CMakeFiles/digikamcore.dir/__/libs/widgets/metadata/xmpwidget.o'
> failed
> make[2]: ***
> [digikam/CMakeFiles/digikamcore.dir/__/libs/widgets/metadata/xmpwidget.o]
> Error 1
> make[2]: *** Waiting for unfinished jobs....
> /var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/exifwidget.cpp:
> In member function 'virtual bool Digikam::ExifWidget::decodeMetadata()':
> /var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/exifwidget.cpp:115:45:
> error: no matching function for call to
> 'Digikam::DMetadata::getExifTagsDataList()'
>      setMetadataMap(data.getExifTagsDataList());
>
> Could be something in my ebuild I used from 3.5. Or I'm missing something.
> cheers, JD
>
>
>
>
>
>
>
> On Fri, Jan 3, 2014 at 1:16 PM, Jim Dory <[hidden email]> wrote:
>>
>> Peter, thanks for informative reply.
>>
>> 1) I don't use eix - I'll give it a try.
>> 2) I always use emerge -avuND @world when updating.
>> 3) I have the elogs emailed me automatically so I can read each one.
>> 4) yes, but only when it asks
>> 5) depclean not as often as I should, but occasionally
>> 6) first go-to when I have a problem, usually doesn't have anything to fix
>> these days.
>> 7) when my root partition starts filling up I do this.
>> 8) when it asks, not as matter of course.
>>
>> I will say I may have fixed problem but haven't had time to play around
>> much to be sure. Possibly things are still broken, but I am finally able to
>> get some accurate thumbnails. I will see what happens when I tag some - that
>> was throwing the thumbnails off previously.
>>
>> What I did was try to build an ebuild with digikam-4.0.0.beta1 but it
>> would fail during the compile. So I went ahead and as my user (not root)
>> installed it via "make && make install [as root]" in my home/Opt directory.
>> However, I forgot about specifying an install directory so it installed
>> globally. Oops.
>>
>> I had the exact same problem with the beta version so uninstalled it using
>> the make uninstall command. That removed a lot of KDE libraries, which I
>> reinstalled using my sets (i.e.: emerge -av @kdegraphics) and a few others.
>> So I'm back on dk 3.5, and it seems to be behaving better now.
>>
>> Not sure why I was having trouble with the dk beta1 ebuild, but that would
>> be another thread I guess and maybe something for the gentoo forums.
>>
>>
>> On Fri, Jan 3, 2014 at 12:04 AM, Peter Albrecht <[hidden email]>
>> wrote:
>>>
>>> Hi Jim,
>>>
>>> on my gentoo system "dev-ruby/sqlite3" is not installed and
>>> digikam works fine with sqlite datebase. So I guess, you
>>> don't need it.
>>>
>>> I am no gentoo expert, but
>>> "/usr/portage/media-gfx/digikam/digikam-3.5.0.ebuild"
>>> says:
>>> > CDEPEND="... || ( dev-qt/qtsql:4[mysql] dev-qt/qtsql:4[sqlite] ) ..."
>>>
>>> I would read this: You need QtSQL (slot 4) with USE-Flag
>>> "mysql" or "sqlite" enabled.
>>>
>>> While "/usr/portage/dev-qt/qtsql/qtsql-4.8.5.ebuild" says:
>>> > DEPEND="... sqlite? ( dev-db/sqlite:3 )"
>>>
>>> Which, I would read like: I you enable "sqlite" USE-Flag,
>>> install "dev-db/sqlite slot 3".
>>> And "eix ^sqlite$" tells you, slot 3 contains version 3.7.x
>>> and 3.8.x.
>>>
>>> To sum up:
>>> If build dev-qt/qtsql with USE-Flag sqlite, sqlite 3.x will
>>> be installed automatically.
>>>
>>> I use at the moment:
>>>  - media-gfx/digikam-3.5.0
>>>  - dev-db/sqlite-3.7.17
>>>  - dev-qt/qtsql-4.8.5
>>>
>>> This works fine for me. Maybe you try these versions.
>>>
>>>
>>> As for gentoo in general:
>>> Maybe you missed some step at your last system update. Wenn
>>> I do updates, I go through the following steps:
>>>
>>>  1) eix-sync   or   emerge --sync; eix-update
>>>
>>>  2) emerge -vpt --update --newuse --deep world
>>>
>>>  3) check elogs (if enabled) with "elogv"
>>>
>>>  4) emerge -va @preserved-rebuild
>>>
>>>  5) emerge -va --depclean
>>>
>>>  6) revdep-rebuild -i
>>>
>>>  7) eclean-dist --destructive
>>>
>>>  8) dispatch-conf
>>>
>>>
>>> Regards,
>>>         Peter
>>>
>>>
>>> On 02.01.2014 23:33, Jim Dory wrote:
>>> > Ok, I may have it already as my version is sqlite-3.8.2
>>> >
>>> > I did enable a sqlite3 USE flag in the make.conf but when doing an
>>> > "emerge
>>> > -avuND @world" no package picks it up. There is a dev-ruby/sqlite3 that
>>> > says this: "An extension library to access a SQLite database from Ruby"
>>> > so
>>> > not sure that would do anything for me. Thanks much for the response.
>>> >  cheers, Jim
>>> >
>>> >
>>> > On Thu, Jan 2, 2014 at 12:25 PM, Gilles Caulier
>>> > <[hidden email]>wrote:
>>> >
>>> >> yes, you need SQlite3 Qt plugin... not SQlite directly. We use Qt DB
>>> >> SDK
>>> _______________________________________________
>>> 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
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Peter Albrecht
In reply to this post by Jim Dory-2
Hello Jim,

trying to build digikam betas on gentoo is something I never
tried. I don't have time at the moment. But it sounds like
an interesting adventure. ;)

I wish you good luck with this!

As for your DK-3.5 crashes:
Maybe some one can help, if you paste a backtrace of this
new crash, again?

Regards,
        Peter

On 04.01.2014 08:44, Jim Dory wrote:
> Peter,
>
> Just an FYI, the DK-3.5 is still crashing on me but the thumbnails are
> tamed down a bit. I did try again to build DK-4.0.0-beta1 by renaming the
> 3.5 ebuild into my local overlay and pointing it at the tarball. I get
> about 41% compiled before the first error. I googled it but found nothing.
> For what its worth here's the errors:
> ...
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Digikam 3.5 is crashing

Jim Dory-2
I don't know if this is enough info or not. When I start Digikam with the gdb, it does say this sometimes:
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
[New Thread 0x7fffd5389700 (LWP 12304)]
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.

Curious if maybe I should switch to Mysql. I've not really wanted to but if it fixes this crash?

Anyway, this was all I came up with.. using splitdebug in the make.conf FEATURES section, recompiling DK.

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe09c8ab1 in ?? () from /usr/lib64/libsqlite3.so.0
(gdb) bt
#0  0x00007fffe09c8ab1 in ?? () from /usr/lib64/libsqlite3.so.0
#1  0x00007fffe09c8c73 in ?? () from /usr/lib64/libsqlite3.so.0
#2  0x00007fffe09dd818 in ?? () from /usr/lib64/libsqlite3.so.0
#3  0x00007fffe0a07877 in ?? () from /usr/lib64/libsqlite3.so.0
#4  0x00007fffe0a1009e in sqlite3_step () from /usr/lib64/libsqlite3.so.0
#5  0x00007fffd4983b4f in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
#6  0x00007fffd49848ef in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so
#7  0x00007ffff7bac687 in QSqlQuery::exec() () from /usr/lib64/qt4/libQtSql.so.4
#8  0x00007ffff555e866 in Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from /usr/lib64/libdigikamcore.so.3
#9  0x00007ffff555e8ec in Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
#10 0x00007ffff555f9e0 in Digikam::DatabaseCoreBackend::execQuery(QString const&, QVariant const&) () from /usr/lib64/libdigikamcore.so.3
#11 0x00007ffff555fa29 in Digikam::DatabaseCoreBackend::execSql(QString const&, QVariant const&, QList<QVariant>*, QVariant*) () from /usr/lib64/libdigikamcore.so.3
#12 0x00007ffff4ef2eee in Digikam::AlbumDB::getSetting(QString const&) () from /usr/lib64/libdigikamdatabase.so.3
#13 0x00007ffff4ef381c in Digikam::AlbumDB::getFilterSettings(QStringList*, QStringList*, QStringList*) () from /usr/lib64/libdigikamdatabase.so.3
#14 0x0000000000644b05 in Digikam::AlbumSettings::getRawFileFilter() const ()
#15 0x00000000005358e6 in Digikam::KipiInterface::hostSetting(QString const&) ()
#16 0x0000000000535254 in Digikam::KipiInterface::currentSelection() ()
#17 0x00007fffbc1b2d46 in KIPIPlugins::KPImagesList::loadImagesFromCurrentSelection() () from /usr/lib64/libkipiplugins.so.3
#18 0x00007fff258dfe7b in ?? () from /usr/lib64/kde4/kipiplugin_facebook.so
#19 0x00007fff258dcbe0 in ?? () from /usr/lib64/kde4/kipiplugin_facebook.so
#20 0x00007fff258d9fca in ?? () from /usr/lib64/kde4/kipiplugin_facebook.so
#21 0x00007ffff2bce458 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007ffff35df5f2 in QAction::triggered(bool) () from /usr/lib64/qt4/libQtGui.so.4
#23 0x00007ffff35e0978 in QAction::activate(QAction::ActionEvent) () from /usr/lib64/qt4/libQtGui.so.4
#24 0x00007ffff3a26843 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#25 0x00007ffff3a2b9e9 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#26 0x00007ffff44012e5 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libkdeui.so.5
#27 0x00007ffff3633773 in QWidget::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#28 0x00007ffff3a2d133 in QMenu::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#29 0x00007ffff35e5b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#30 0x00007ffff35e8e31 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#31 0x00007ffff43433aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#32 0x00007ffff2bba0ac in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#33 0x00007ffff35ebce2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
   from /usr/lib64/qt4/libQtGui.so.4
#34 0x00007ffff365f8ec in ?? () from /usr/lib64/qt4/libQtGui.so.4
#35 0x00007ffff365e7e1 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#36 0x00007ffff36873e2 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#37 0x00007fffeaf95df4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#38 0x00007fffeaf96164 in ?? () from /usr/lib64/libglib-2.0.so.0
#39 0x00007fffeaf9622c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#40 0x00007ffff2be7cce in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#41 0x00007ffff36874c6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#42 0x00007ffff2bb8c0f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#43 0x00007ffff2bb8f4d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#44 0x00007ffff2bbe26b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#45 0x00000000004908a8 in main ()
(gdb) 


/jd


On Sat, Jan 4, 2014 at 12:32 AM, Peter Albrecht <[hidden email]> wrote:
Hello Jim,

trying to build digikam betas on gentoo is something I never
tried. I don't have time at the moment. But it sounds like
an interesting adventure. ;)

I wish you good luck with this!

As for your DK-3.5 crashes:
Maybe some one can help, if you paste a backtrace of this
new crash, again?

Regards,
        Peter

On 04.01.2014 08:44, Jim Dory wrote:
> Peter,
>
> Just an FYI, the DK-3.5 is still crashing on me but the thumbnails are
> tamed down a bit. I did try again to build DK-4.0.0-beta1 by renaming the
> 3.5 ebuild into my local overlay and pointing it at the tarball. I get
> about 41% compiled before the first error. I googled it but found nothing.
> For what its worth here's the errors:
> ...
_______________________________________________
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