Bug 308268 - Digikam crashes during startup
Summary: Digikam crashes during startup
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 2.5.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-12 02:00 UTC by Geoff Tayler
Modified: 2016-07-10 13:25 UTC (History)
1 user (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 Geoff Tayler 2012-10-12 02:00:02 UTC
Application: digikam (2.5.0)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-31-generic i686
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Starting Digikam. Crash occurrs regardless of config files, database, empty library etc. during the splash screen at phase "initialising main view"

Behaviour started a few days after an apparently succesful upgrade to Kubuntu 12.04, but Digikam was working after the upgrade.

- Custom settings of the application:
Crash always occurs in the same place during start up even if config files are removed

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Bus error
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb51788c0 (LWP 2537))]

Thread 5 (Thread 0xb3388b40 (LWP 2541)):
#0  0x00921416 in __kernel_vsyscall ()
#1  0x0324596b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x023ce85c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x07d7d350 in wait (time=4294967295, this=0xa238548) at thread/qwaitcondition_unix.cpp:86
#4  QWaitCondition::wait (this=0xa2384b4, mutex=0xa2384b0, time=4294967295) at thread/qwaitcondition_unix.cpp:158
#5  0x0820346e in Digikam::ScanController::run (this=0xa245008) at /build/buildd/digikam-2.5.0/core/digikam/database/scancontroller.cpp:647
#6  0x07d7cde0 in QThreadPrivate::start (arg=0xa245008) at thread/qthread_unix.cpp:298
#7  0x03241d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x023c0f4e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 4 (Thread 0xb29ffb40 (LWP 2542)):
#0  0x08dfb1fc in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x07ec48e7 in QEventDispatcherGlib::processEvents (this=0xb2000468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#2  0x07e9050d in QEventLoop::processEvents (this=0xb29ff0c0, flags=...) at kernel/qeventloop.cpp:149
#3  0x07e907a9 in QEventLoop::exec (this=0xb29ff0c0, flags=...) at kernel/qeventloop.cpp:204
#4  0x07d7994c in QThread::exec (this=0xa238db8) at thread/qthread.cpp:501
#5  0x07e6db5d in QInotifyFileSystemWatcherEngine::run (this=0xa238db8) at io/qfilesystemwatcher_inotify.cpp:248
#6  0x07d7cde0 in QThreadPrivate::start (arg=0xa238db8) at thread/qthread_unix.cpp:298
#7  0x03241d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x023c0f4e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xb1fffb40 (LWP 2545)):
#0  0x00921416 in __kernel_vsyscall ()
#1  0x0324596b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x023ce85c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x07d7d350 in wait (time=4294967295, this=0xa651b68) at thread/qwaitcondition_unix.cpp:86
#4  QWaitCondition::wait (this=0xa6519a8, mutex=0xa6519a4, time=4294967295) at thread/qwaitcondition_unix.cpp:158
#5  0x012d0b2c in Digikam::ParkingThread::run (this=0xa651998) at /build/buildd/digikam-2.5.0/core/libs/threads/threadmanager.cpp:119
#6  0x07d7cde0 in QThreadPrivate::start (arg=0xa651998) at thread/qthread_unix.cpp:298
#7  0x03241d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x023c0f4e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb0fffb40 (LWP 2546)):
#0  0x00921416 in __kernel_vsyscall ()
#1  0x023b2800 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x08e08a7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x08dfb0ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x08dfb201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x07ec48e7 in QEventDispatcherGlib::processEvents (this=0xa145100, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x07e9050d in QEventLoop::processEvents (this=0xb0fff0c0, flags=...) at kernel/qeventloop.cpp:149
#7  0x07e907a9 in QEventLoop::exec (this=0xb0fff0c0, flags=...) at kernel/qeventloop.cpp:204
#8  0x07d7994c in QThread::exec (this=0xa1457f8) at thread/qthread.cpp:501
#9  0x07e6db5d in QInotifyFileSystemWatcherEngine::run (this=0xa1457f8) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x07d7cde0 in QThreadPrivate::start (arg=0xa1457f8) at thread/qthread_unix.cpp:298
#11 0x03241d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x023c0f4e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb51788c0 (LWP 2537)):
[KCrash Handler]
#7  0x024121ae in ?? () from /lib/i386-linux-gnu/libc.so.6
#8  0x08997137 in qstrncmp (len=<optimized out>, str2=0xa7a5ac8 "$kico_image-missing_16_1:1:trans", str1=<optimized out>) at /usr/include/qt4/QtCore/qbytearray.h:104
#9  SharedMemory::findNamedEntry (this=0xafdf4000, key=...) at ../../kdecore/util/kshareddatacache.cpp:786
#10 0x08993f57 in KSharedDataCache::find (this=0xa16bd00, key=..., destination=0xbfba52a4) at ../../kdecore/util/kshareddatacache.cpp:1637
#11 0x04d6045b in KIconLoaderPrivate::findCachedPixmapWithPath (this=0xa16f720, key=..., data=..., path=...) at ../../kdeui/icons/kiconloader.cpp:861
#12 0x04d60801 in KIconLoader::loadIcon (this=0xa16b2f0, _name=..., group=KIconLoader::Desktop, size=16, state=2, overlays=..., path_store=0x0, canReturnNull=false) at ../../kdeui/icons/kiconloader.cpp:1225
#13 0x00c33097 in khtml::Cache::init () at ../../khtml/misc/loader.cpp:1389
#14 0x00a62538 in KHTMLGlobal::KHTMLGlobal (this=0xa167308) at ../../khtml/khtml_global.cpp:66
#15 0x00a627e6 in KHTMLGlobal::ref () at ../../khtml/khtml_global.cpp:133
#16 0x00a6292a in KHTMLGlobal::registerPart (part=0xa1671a8) at ../../khtml/khtml_global.cpp:158
#17 0x00a35c3f in KHTMLPart::KHTMLPart (this=0xa1671a8, __vtt_parm=0x84494e4, parentWidget=0xa64b3c0, parent=0x0, prof=KHTMLPart::DefaultGUI, __in_chrg=<optimized out>) at ../../khtml/khtml_part.cpp:186
#18 0x08296b4d in Digikam::WelcomePageView::WelcomePageView (this=0xa1671a8, parent=0xa64b3c0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /build/buildd/digikam-2.5.0/core/digikam/views/welcomepageview.cpp:62
#19 0x0828690d in Digikam::StackedView::StackedView (this=0xa64b3c0, parent=0xa645208) at /build/buildd/digikam-2.5.0/core/digikam/views/stackedview.cpp:110
#20 0x0828db47 in Digikam::DigikamView::DigikamView (this=0xa2793c8, parent=0xa27cfa8, modelCollection=0xa4cd7d0) at /build/buildd/digikam-2.5.0/core/digikam/views/digikamview.cpp:200
#21 0x081a413d in Digikam::DigikamApp::setupView (this=0xa27cfa8) at /build/buildd/digikam-2.5.0/core/digikam/main/digikamapp.cpp:534
#22 0x081c2e94 in Digikam::DigikamApp::DigikamApp (this=0xa27cfa8, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /build/buildd/digikam-2.5.0/core/digikam/main/digikamapp.cpp:250
#23 0x080b6762 in main (argc=<error reading variable: Cannot access memory at address 0xac8>, argv=<error reading variable: Cannot access memory at address 0xacc>) at /build/buildd/digikam-2.5.0/core/digikam/main/main.cpp:188

Reported using DrKonqi
Comment 1 caulier.gilles 2012-10-12 07:43:34 UTC
It crash in KHTML WHEN IT TRY TO GET ICON FROM KDE install. Sound like your system is not properly installed. Check your system...

Also, i recommend to use last 2.9.0 and try again.

Gilles Caulier
Comment 2 caulier.gilles 2015-06-27 13:45:23 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 3 caulier.gilles 2015-08-22 06:38:15 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 4 caulier.gilles 2016-07-10 13:25:45 UTC
This problem is not reproducible with last 5.0.0.
I close this file now. Don't hesitate to re-open it if necessary.
Gilles Caulier