Bug 275578 - Error while to init digiKam under ubuntu natty i386
Summary: Error while to init digiKam under ubuntu natty i386
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (show other bugs)
Version: 1.9.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-13 20:15 UTC by Antonio
Modified: 2016-07-14 12:49 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio 2011-06-13 20:15:02 UTC
Application: digikam (1.9.0)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:
Sólo tenía abierto nautilus y era la primera vez que abría digikam. He dejado las opciones por defecto de la configuración. La colección de imágenes ya existía y tenía la base de datos de digikam creada con la versión de Ubuntu Maverick, donde funcionaba bien.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0xb653d960 (LWP 7701))]

Thread 3 (Thread 0xb6173b70 (LWP 7702)):
#0  0x01ade72a in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x01adf03a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x01adf92b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x02095304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#4  0x01b082df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x00bd1e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0x018f273e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb3119b70 (LWP 7704)):
[KCrash Handler]
#7  0x0473552f in Exiv2::Value::toString() const () from /usr/lib/libexiv2.so.10
#8  0x04689800 in Exiv2::Exifdatum::toString() const () from /usr/lib/libexiv2.so.10
#9  0x04722049 in ?? () from /usr/lib/libexiv2.so.10
#10 0x04715fd4 in ?? () from /usr/lib/libexiv2.so.10
#11 0x0468bbfd in Exiv2::ExifParser::encode(std::vector<unsigned char, std::allocator<unsigned char> >&, unsigned char const*, unsigned int, Exiv2::ByteOrder, Exiv2::ExifData const&) () from /usr/lib/libexiv2.so.10
#12 0x00789499 in encode (this=0xb311696c, addExifHeader=false) at /usr/include/exiv2/exif.hpp:624
#13 KExiv2Iface::KExiv2::getExifEncoded (this=0xb311696c, addExifHeader=false) at ../../../../libs/libkexiv2/libkexiv2/kexiv2exif.cpp:95
#14 0x08c4e31f in Digikam::DImgLoader::uniqueHash (filePath=..., img=..., loadMetadata=false) at /build/buildd/digikam-1.9.0/libs/dimg/loaders/dimgloader.cpp:240
#15 0x08c4076e in Digikam::DImg::getUniqueHash (this=0xb3118c60) at /build/buildd/digikam-1.9.0/libs/dimg/dimg.cpp:2440
#16 0x071f445a in Digikam::ImageScanner::uniqueHash (this=0xb3118c50) at /build/buildd/digikam-1.9.0/libs/database/imagescanner.cpp:664
#17 0x071f4592 in Digikam::ImageScanner::prepareImage (this=0xb3118c50) at /build/buildd/digikam-1.9.0/libs/database/imagescanner.cpp:213
#18 0x071f46cf in Digikam::ImageScanner::addImage (this=0xb3118c50, albumId=413) at /build/buildd/digikam-1.9.0/libs/database/imagescanner.cpp:218
#19 0x071f99e1 in Digikam::ImageScanner::newFile (this=0xb3118c50, albumId=413) at /build/buildd/digikam-1.9.0/libs/database/imagescanner.cpp:100
#20 0x071a5c33 in Digikam::CollectionScanner::scanNewFile (this=0xb31192b0, info=..., albumId=413) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:861
#21 0x071a7f43 in Digikam::CollectionScanner::scanAlbum (this=0xb31192b0, location=..., album=...) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:746
#22 0x071a7b03 in Digikam::CollectionScanner::scanAlbum (this=0xb31192b0, location=..., album=...) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:769
#23 0x071a7b03 in Digikam::CollectionScanner::scanAlbum (this=0xb31192b0, location=..., album=...) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:769
#24 0x071a7b03 in Digikam::CollectionScanner::scanAlbum (this=0xb31192b0, location=..., album=...) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:769
#25 0x071a7b03 in Digikam::CollectionScanner::scanAlbum (this=0xb31192b0, location=..., album=...) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:769
#26 0x071a8897 in Digikam::CollectionScanner::scanAlbumRoot (this=0xb31192b0, location=...) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:530
#27 0x071a8b32 in Digikam::CollectionScanner::completeScan (this=0xb31192b0) at /build/buildd/digikam-1.9.0/libs/database/collectionscanner.cpp:282
#28 0x08220e2b in Digikam::ScanController::run (this=0x9a66ea8) at /build/buildd/digikam-1.9.0/digikam/scancontroller.cpp:600
#29 0x06ca1da2 in QThreadPrivate::start (arg=0x9a66ea8) at thread/qthread_unix.cpp:320
#30 0x00bd1e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#31 0x018f273e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb653d960 (LWP 7701)):
#0  0x00505416 in __kernel_vsyscall ()
#1  0x00bd90b9 in __lll_lock_wait () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x00bd454b in _L_lock_791 () from /lib/i386-linux-gnu/libpthread.so.0
#3  0x00bd4371 in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0
#4  0x01900616 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6
#5  0x01ae0851 in g_main_context_wakeup () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x06dc379d in QEventDispatcherGlib::wakeUp (this=0x9a5f740) at kernel/qeventdispatcher_glib.cpp:578
#7  0x06d99310 in QCoreApplication::postEvent (receiver=0x9a69548, event=0x9a630d8, priority=0) at kernel/qcoreapplication.cpp:1194
#8  0x06d994cc in QCoreApplication::postEvent (receiver=0x9a69548, event=0x9a630d8) at kernel/qcoreapplication.cpp:1093
#9  0x06d9f73c in QMetaMethod::invoke (this=0xbfba431c, object=0x9a69548, connectionType=Qt::QueuedConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1618
#10 0x06da036d in QMetaObject::invokeMethod (obj=0x9a69548, member=0x6e54332 "quit", type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1151
#11 0x06d770ef in invokeMethod (this=0x9a69548) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:424
#12 QInotifyFileSystemWatcherEngine::stop (this=0x9a69548) at io/qfilesystemwatcher_inotify.cpp:343
#13 0x06d69c64 in QFileSystemWatcher::~QFileSystemWatcher (this=0x9a5d480, __in_chrg=<value optimized out>) at io/qfilesystemwatcher.cpp:445
#14 0x06d69d42 in QFileSystemWatcher::~QFileSystemWatcher (this=0x9a5d480, __in_chrg=<value optimized out>) at io/qfilesystemwatcher.cpp:462
#15 0x06da9b87 in QObjectPrivate::deleteChildren (this=0x9a5d428) at kernel/qobject.cpp:1964
#16 0x06dae39f in QObject::~QObject (this=0x9a5d410, __in_chrg=<value optimized out>) at kernel/qobject.cpp:946
#17 0x008b05ab in Solid::Backends::Fstab::FstabWatcher::~FstabWatcher (this=0x9a5d410, __in_chrg=<value optimized out>) at ../../../solid/solid/backends/fstab/fstabwatcher.cpp:48
#18 0x008b05e2 in Solid::Backends::Fstab::FstabWatcher::~FstabWatcher (this=0x9a5d410, __in_chrg=<value optimized out>) at ../../../solid/solid/backends/fstab/fstabwatcher.cpp:51
#19 0x008b0455 in destroy () at ../../../solid/solid/backends/fstab/fstabwatcher.cpp:30
#20 0x00838feb in Solid::CleanUpGlobalStatic::~CleanUpGlobalStatic (this=0x8cc8c8, __in_chrg=<value optimized out>) at ../../../solid/solid/soliddefs_p.h:67
#21 0x01851a6f in ?? () from /lib/i386-linux-gnu/libc.so.6
#22 0x01851acf in exit () from /lib/i386-linux-gnu/libc.so.6
#23 0x021fea90 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#24 0x0156a11a in KApplication::xioErrhandler (this=0xbfba4d08, dpy=0x98e1ca8) at ../../kdeui/kernel/kapplication.cpp:419
#25 0x0156a156 in kde_xio_errhandler (dpy=0x98e1ca8) at ../../kdeui/kernel/kapplication.cpp:126
#26 0x019bd166 in _XIOError () from /usr/lib/i386-linux-gnu/libX11.so.6
#27 0x019ba81f in _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
#28 0x019ab4eb in XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
#29 0x02b93555 in x11EventSourceCheck (s=0x98d2840) at kernel/qguieventdispatcher_glib.cpp:85
#30 0x01ade71d in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#31 0x01adf03a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#32 0x01adf524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#33 0x06dc3577 in QEventDispatcherGlib::processEvents (this=0x9868488, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#34 0x02b93775 in QGuiEventDispatcherGlib::processEvents (this=0x9868488, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#35 0x06d95289 in QEventLoop::processEvents (this=0x9a66800, flags=...) at kernel/qeventloop.cpp:149
#36 0x06d95522 in QEventLoop::exec (this=0x9a66800, flags=...) at kernel/qeventloop.cpp:201
#37 0x0821e8df in Digikam::ScanController::completeCollectionScan (this=0x9a66ea8, splash=0x9b245c8) at /build/buildd/digikam-1.9.0/digikam/scancontroller.cpp:415
#38 0x081d5852 in Digikam::DigikamApp::DigikamApp (this=0x9b21fd0, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/digikam-1.9.0/digikam/digikamapp.cpp:200
#39 0x08265716 in main (argc=) at /build/buildd/digikam-1.9.0/digikam/main.cpp:177

Reported using DrKonqi
Comment 1 caulier.gilles 2011-06-13 22:41:03 UTC
Trash appears in Exiv2 library, not digiKam

Gilles Caulier
Comment 2 Andreas Huggel 2011-06-14 02:12:19 UTC
Crash happens while encoding metadata. Can you identify the image that causes the crash and send it to me / attach it here?

Thanks, Andreas
Comment 3 Marcel Wiesweg 2011-06-18 14:47:08 UTC
Antonio: If you look at the console output of digikam, the path of the relevant image will usually be printed before the crash. You can also paste us the last lines of console output from the crash here.
Comment 4 Antonio 2011-06-18 15:19:35 UTC
Siento no poder ayudaros más, pero se ha solucionado.

Lo que hice fue borrar la base de datos de imágenes con lo que al ejecutar el programa creó una nueva y funcionó.

Después cambié la base de datos nueva por la vieja y siguió funcionando.

Un saludo.
Comment 5 Francesco Riosa 2011-06-18 15:51:47 UTC
<courtesy google translator>
Sorry I can not help you more, but has been fixed.

What I did was delete the database of images with which to run the
created a new program and it worked.

After I changed the new database for the old and continued working.

Regards.
Comment 6 caulier.gilles 2015-07-03 05:58:22 UTC
New digiKam 4.11.0 is available.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 7 caulier.gilles 2015-08-24 05:13:40 UTC
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.
Comment 8 caulier.gilles 2016-07-14 12:49:08 UTC
This problem is not reproducible using last digiKam 5.0.0 + Exiv2 0.25.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier