Bug 269528

Summary: Schema updating process from v4 to v5
Product: [Applications] digikam Reporter: nicolasmf
Component: Database-SchemaAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles
Priority: NOR    
Version: 1.4.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 2.5.0
Sentry Crash Report:

Description nicolasmf 2011-03-27 11:53:42 UTC 
Application: digikam (1.4.0)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-28-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
On digikam startup, I get the following message (pop-up):
"The schema updating process from version 4 to version 5 failed, caused by an error that we did not expect. You can try to discard your old database and start with an empty one. [...]"
Last time I used digiKam, the only "relevant" thing I did was to remove a collecion from removable media...

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7fd557698700 (LWP 2148)):
#0  __pthread_mutex_lock (mutex=0xf8ca88) at pthread_mutex_lock.c:62
#1  0x00007fd56042806e in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fd5604287b5 in g_main_loop_run () from /lib/libglib-2.0.so.0
#3  0x00007fd557dcf3c4 in ?? () from /usr/lib/libgio-2.0.so.0
#4  0x00007fd56044d7e4 in ?? () from /lib/libglib-2.0.so.0
#5  0x00007fd564ad6971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#6  0x00007fd5635a992d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 6 (Thread 0x7fd545277700 (LWP 2414)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fd564d61e3b in wait (this=<value optimized out>, mutex=0x15dbb98, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x15dbb98, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007fd568d7b5e4 in Digikam::ParkingThread::run (this=0x15dbb80) at /build/buildd/digikam-1.4.0/libs/threads/threadmanager.cpp:101
#4  0x00007fd564d6127e in QThreadPrivate::start (arg=0x15dbb80) at thread/qthread_unix.cpp:266
#5  0x00007fd564ad6971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#6  0x00007fd5635a992d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7fd544a76700 (LWP 2415)):
#0  0xffffffffff60014c in ?? ()
#1  0x00007fd544a75a70 in ?? ()
#2  0x00007fff1fdff852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0x7fd544275700 (LWP 2416)):
#0  0x00007fd56359d203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fd560428009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fd56042845c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fd564e811e6 in QEventDispatcherGlib::processEvents (this=0x13d3b80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fd564e53a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fd564e53dec in QEventLoop::exec (this=0x7fd544274d90, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fd564d5e2fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fd564d6127e in QThreadPrivate::start (arg=0x13d5eb0) at thread/qthread_unix.cpp:266
#8  0x00007fd564ad6971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#9  0x00007fd5635a992d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fd53b508700 (LWP 2417)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:212
#1  0x00007fd54124d0d1 in ?? () from /usr/lib/libxine.so.1
#2  0x00007fd564ad6971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#3  0x00007fd5635a992d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fd539cdb700 (LWP 2419)):
#0  0x00007fd56359d203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fd560428009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fd56042845c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fd564e811e6 in QEventDispatcherGlib::processEvents (this=0x159eda0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fd564e53a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fd564e53dec in QEventLoop::exec (this=0x7fd539cdad30, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fd564d5e2fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fd5414a92b0 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#8  0x00007fd564d6127e in QThreadPrivate::start (arg=0x159e850) at thread/qthread_unix.cpp:266
#9  0x00007fd564ad6971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007fd5635a992d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd56bd557c0 (LWP 2147)):
[KCrash Handler]
#6  KDirWatch::contains (this=0x0, _path=...) at ../../kdecore/io/kdirwatch.cpp:1830
#7  0x000000000063d598 in Digikam::AlbumManager::addAlbumRoot (this=0x119e400, location=...) at /build/buildd/digikam-1.4.0/digikam/albummanager.cpp:1131
#8  0x0000000000645ca1 in Digikam::AlbumManager::slotCollectionLocationStatusChanged (this=0x119e400, location=..., oldStatus=0) at /build/buildd/digikam-1.4.0/digikam/albummanager.cpp:1102
#9  0x0000000000647d75 in Digikam::AlbumManager::qt_metacall (this=0x119e400, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1fdeaad0) at /build/buildd/digikam-1.4.0/obj-x86_64-linux-gnu/digikam/albummanager.moc:185
#10 0x00007fd564e6cb27 in QMetaObject::activate (sender=0x11afab0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff1fdeaa01) at kernel/qobject.cpp:3280
#11 0x00007fd5687ea053 in Digikam::CollectionManager::locationStatusChanged (this=0x0, _t1=<value optimized out>, _t2=0) at /build/buildd/digikam-1.4.0/obj-x86_64-linux-gnu/digikam/collectionmanager.moc:108
#12 0x00007fd5687f0b26 in Digikam::CollectionManager::updateLocations (this=<value optimized out>) at /build/buildd/digikam-1.4.0/libs/database/collectionmanager.cpp:1376
#13 0x00007fd5687f181a in Digikam::CollectionManager::deviceAdded (this=0x11afab0, udi=<value optimized out>) at /build/buildd/digikam-1.4.0/libs/database/collectionmanager.cpp:1257
#14 0x00007fd5687f1959 in Digikam::CollectionManager::qt_metacall (this=0x11afab0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1fdeaf60) at /build/buildd/digikam-1.4.0/obj-x86_64-linux-gnu/digikam/collectionmanager.moc:92
#15 0x00007fd564e6cb27 in QMetaObject::activate (sender=0xf23720, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff1fdeaa01) at kernel/qobject.cpp:3280
#16 0x00007fd56a6aa352 in Solid::DeviceNotifier::deviceAdded (this=0x0, _t1=<value optimized out>) at ./devicenotifier.moc:87
#17 0x00007fd56a6ad603 in Solid::DeviceManagerPrivate::_k_deviceAdded (this=0xf23720, udi=...) at ../../../solid/solid/devicemanager.cpp:188
#18 0x00007fd56a6ad84c in Solid::DeviceManagerPrivate::qt_metacall (this=0xf23720, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1fdeb150) at ./devicemanager_p.moc:79
#19 0x00007fd564e6cb27 in QMetaObject::activate (sender=0x118a2f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff1fdeaa01) at kernel/qobject.cpp:3280
#20 0x00007fd56a6bf1b2 in Solid::Ifaces::DeviceManager::deviceAdded (this=0x0, _t1=<value optimized out>) at ./ifaces/devicemanager.moc:87
#21 0x00007fd56a6e921d in Solid::Backends::Hal::HalManager::qt_metacall (this=0x118a2f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1fdeb3c0) at ./backends/hal/halmanager.moc:77
#22 0x00007fd5648770ee in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:919
#23 0x00007fd5648820ef in QDBusCallDeliveryEvent::placeMetaCall (this=0x11449a0, object=0x7fff1fdea920) at qdbusintegrator_p.h:103
#24 0x00007fd564e66bde in QObject::event (this=0x118a2f0, e=0x0) at kernel/qobject.cpp:1219
#25 0x00007fd565a65fdc in QApplicationPrivate::notify_helper (this=0xf38740, receiver=0x118a2f0, e=0x1effaa0) at kernel/qapplication.cpp:4396
#26 0x00007fd565a6baed in QApplication::notify (this=0x7fff1fdebf90, receiver=0x118a2f0, e=0x1effaa0) at kernel/qapplication.cpp:4277
#27 0x00007fd5667b8156 in KApplication::notify (this=0x7fff1fdebf90, receiver=0x118a2f0, event=0x1effaa0) at ../../kdeui/kernel/kapplication.cpp:310
#28 0x00007fd564e54cdc in QCoreApplication::notifyInternal (this=0x7fff1fdebf90, receiver=0x118a2f0, event=0x1effaa0) at kernel/qcoreapplication.cpp:732
#29 0x00007fd564e57c22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xef9b90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xef9b90) at kernel/qcoreapplication.cpp:1373
#31 0x00007fd564e81653 in sendPostedEvents (s=0xf3c2c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#32 postEventSourceDispatch (s=0xf3c2c0) at kernel/qeventdispatcher_glib.cpp:277
#33 0x00007fd560424342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0x00007fd5604282a8 in ?? () from /lib/libglib-2.0.so.0
#35 0x00007fd56042845c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0x00007fd564e81193 in QEventDispatcherGlib::processEvents (this=0xef9280, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#37 0x00007fd565b18a4e in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#38 0x00007fd564e53a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#39 0x00007fd564e53dec in QEventLoop::exec (this=0x7fff1fdebe00, flags=) at kernel/qeventloop.cpp:201
#40 0x00007fd564e57ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#41 0x000000000077cc1d in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/digikam-1.4.0/digikam/main.cpp:195

Possible duplicates by query: bug 266506, bug 261740, bug 261228, bug 258002, bug 255054.

Reported using DrKonqi
Comment 1 caulier.gilles 2011-03-27 12:19:52 UTC 
Can you try again with 1.9.0. If i remember, this problem have been fixed...

Gilles Caulier
Comment 2 nicolasmf 2011-03-30 08:34:10 UTC 
I upgraded to 1.9 using the following package:
sudo apt-add-repository ppa:philip5/extra
I still get the "The schema updating process from version 4 to version 5 failed[...]" message and have to remove and add anew my collections every time. For some reason it lasts a lot more than with 1.4
Is there a known reason for this to happen in the first place? Everything worked beautifully one week ago. Throwing away the database would be really painful...
Comment 3 Marcel Wiesweg 2011-04-07 22:00:11 UTC 
Usually, this hint at a somehow broken database file. There is a report about that here and there, but no general cause. You can send me the database file by private mail for inspection if it's not too large.
Comment 4 caulier.gilles 2011-12-15 08:43:58 UTC 
Nicolas,

Do you see comment #3 from Marcel ?

Gilles Caulier
Comment 5 caulier.gilles 2011-12-15 08:46:01 UTC 
See also bug #277928

Gilles Caulier
Comment 6 nicolasmf 2011-12-15 08:55:50 UTC 
Thanks Gilles,
I thought I had posted this, sorry for the delay.
I performed a clean install of Ubuntu and for some reason the db seemed to work afterwards. An upgrade to Ubuntu 11.10 and the corresponding digikam version earlier this year did not cause any noticeable problem (from Digikam's side, that is). I am afraid this is not reproductible at all, but the hint in bug 277928 is worth keeping in mind in case this happens again. From my side, case closed. Thanks!

PS: can you take care of "closing" the bug? I don't know which category applies.