Hi:
I did a fresh install of NetrunnerOS 13.06. I reformated the disk ext4 and repartitioned the drive. I installed the OS. I then updated the OS, I updated KDE to 4.11. I then copied my data into the new home directory. When I staart Digikam 3.3.0 I get the following error:

No album library path has been found in the configuration file. Giving up the schema updating process. Please try with an empty database, or repair your configuration.

In the terminal I see the following:

Code: Select all

cubbybear@cubbybear-HP-Pavilion-g7-Notebook-PC:~$ digikam
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
"/org/freedesktop/UDisks2/drives/Canon_MP560_series_20DAFB" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/hp_______CDDVDW_SN_208BB_R8HB6GOC400SAA" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/ST31000524AS_5VP9X2JX" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_2_2e0_5B631F00026D" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Hitachi_HTS547564A9E384_J2130053E0MZBA" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Hitachi_HTS547564A9E384_J2130053E0MZBA" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/Hitachi_HTS547564A9E384_J2130053E0MZBA" : property "Device" does not exist
"/org/freedesktop/UDisks2/drives/ST31000524AS_5VP9X2JX" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/ST31000524AS_5VP9X2JX" : property "Device" does not exist
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
digikam(11042)/digikam (core): Album library path from config file is empty. Aborting update.
[0x28d5398] main services discovery error: no suitable services discovery module
"/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_2_2e0_5B631F00026D" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_2_2e0_5B631F00026D" : property "Device" does not exist
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::setPen: Painter not active
QPainter::setFont: Painter not active
QPainter::fontMetrics: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setFont: Painter not active
QPainter::fontMetrics: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setFont: Painter not active
QPainter::fontMetrics: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setFont: Painter not active
QPainter::fontMetrics: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setFont: Painter not active
QPainter::fontMetrics: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setFont: Painter not active
QPainter::fontMetrics: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setFont: Painter not active
QPainter::fontMetrics: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
cubbybear@cubbybear-HP-Pavilion-g7-Notebook-PC:~$

How can I correct the problem? I do not want to loose my tags. The settings are pointing to the correct directory. Can some one help?

look in ~/.kde/share/config/digikamrc the 2 lines with the term Path, are the paths listed still correct in your reformatted system? is there anything listed? if not you'll need to manually add the full paths

alternatively you could rename your digikamrc file and folder ~/.kde/share/apps/digikam and start fresh

ps - when posting large amounts of the please use code tags available in preview mode

Sorry for the long info post. I looked in the digikamrc file and saw no path statements. When I restored data I only restored the pictures directory and sub directorys. .kde.share/apps and config files were new created on first run. The only statements close to a path were in the Database section and they were correct. Here they are:

[Database Settings]
Database Connectoptions=
Database Hostname=
Database Name=/home/cubbybear/Pictures/
Database Name Thumbnails=/home/cubbybear/Pictures/
Database Password=
Database Port=-1
Database Type=QSQLITE
Database Username=
Internal Database Server=false

Where would I add the path section? What is the format? Hope this helps.

look in settings -> database, is there a database file path ?

seems to me that if you did not copy your ~/.kde folder that something went bad during your Digikam 1st run, may wish to remove the file config/digicamrc and folder apps/digikam and start fresh

this is a snippet from my digikamrc

[Album Settings]
Album Collections=Category,Friends,Holidays,Miscellaneous,Nature,Party,Todo,Travel
Album Path=/home/smiley/DoNotBackup
Album Sort Order=0
Database File Path=/home/smiley/DoNotBackup
Default Icon Size=157

notice how I added tags to original post,

Added the two paths to the rc Album section as shown now I get segmentation fault on start up. I am going to remove Digikam and reinstall. Will remove .kde stuff and will restart process.

Removed digikam and it's .kde files. Reinstalled digikam and all dependencies. I get the same results. I wonder if this is KDE 4.11 or Digikam 3.3.0 problem?

"same results" you mean segmentation fault or the same output when running in Konsole?

can you look in the file ~/.xsession-errors

open kdebugdialog -> deselect all, then search for digikam -> select all, then apply and exit

start digikam and after it crashes open ~/.xsession-errors and look towards the end for digikam output

does showfoto also crash?

Showphoto does not crash. This is the crash backtrace after entering the two path statments manually into the config file.

This is the backtrace:

Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f707054ba40 (LWP 16851))]


[KCrash Handler]
#6 QReadWriteLock::lockForWrite (this=0x8) at thread/qreadwritelock.cpp:277
#7 0x00007f706d6b9194 in relock (this=0x7f7047cc5450) at /usr/include/qt4/QtCore/qreadwritelock.h:155
#8 QWriteLocker (areadWriteLock=<optimized out>, this=0x7f7047cc5450) at /usr/include/qt4/QtCore/qreadwritelock.h:175
#9 Digikam::CollectionScanner::scanFileNormal (this=this@entry=0x7f7047cc62a0, fi=..., scanInfo=...) at /build/buildd/digikam-3.3.0/core/libs/database/collectionscanner.cpp:1102
#10 0x00007f706d6bcc69 in Digikam::CollectionScanner::scanAlbum (this=this@entry=0x7f7047cc62a0, location=..., album=...) at /build/buildd/digikam-3.3.0/core/libs/database/collectionscanner.cpp:1032
#11 0x00007f706d6bcb62 in Digikam::CollectionScanner::scanAlbum (this=this@entry=0x7f7047cc62a0, location=..., album=...) at /build/buildd/digikam-3.3.0/core/libs/database/collectionscanner.cpp:1066
#12 0x00007f706d6bcb62 in Digikam::CollectionScanner::scanAlbum (this=this@entry=0x7f7047cc62a0, location=..., album=...) at /build/buildd/digikam-3.3.0/core/libs/database/collectionscanner.cpp:1066
#13 0x00007f706d6bd67b in Digikam::CollectionScanner::scanAlbumRoot (this=this@entry=0x7f7047cc62a0, location=...) at /build/buildd/digikam-3.3.0/core/libs/database/collectionscanner.cpp:785
#14 0x00007f706d6bdf75 in Digikam::CollectionScanner::completeScan (this=this@entry=0x7f7047cc62a0) at /build/buildd/digikam-3.3.0/core/libs/database/collectionscanner.cpp:452
#15 0x00007f706d72ac99 in Digikam::SchemaUpdater::updateV4toV6 (this=this@entry=0x7f7047cc68e0) at /build/buildd/digikam-3.3.0/core/libs/database/schemaupdater.cpp:1108
#16 0x00007f706d72ceea in Digikam::SchemaUpdater::makeUpdates (this=this@entry=0x7f7047cc68e0) at /build/buildd/digikam-3.3.0/core/libs/database/schemaupdater.cpp:438
#17 0x00007f706d72e240 in Digikam::SchemaUpdater::startUpdates (this=this@entry=0x7f7047cc68e0) at /build/buildd/digikam-3.3.0/core/libs/database/schemaupdater.cpp:295
#18 0x00007f706d72ea98 in Digikam::SchemaUpdater::update (this=this@entry=0x7f7047cc68e0) at /build/buildd/digikam-3.3.0/core/libs/database/schemaupdater.cpp:143
#19 0x00007f706d6d4fc0 in Digikam::DatabaseBackend::initSchema (this=<optimized out>, updater=updater@entry=0x7f7047cc68e0) at /build/buildd/digikam-3.3.0/core/libs/database/databasebackend.cpp:79
#20 0x00007f706d6cfe12 in Digikam::DatabaseAccess::checkReadyForUse (observer=observer@entry=0x2bc1f00) at /build/buildd/digikam-3.3.0/core/libs/database/databaseaccess.cpp:303
#21 0x00000000005d2816 in Digikam::ScanController::run (this=0x2bc1ef0) at /build/buildd/digikam-3.3.0/core/digikam/database/scancontroller.cpp:734
#22 0x00007f706ac9bbec in QThreadPrivate::start (arg=0x2bc1ef0) at thread/qthread_unix.cpp:338
#23 0x00007f70651eff8e in start_thread (arg=0x7f7047cc7700) at pthread_create.c:311
#24 0x00007f7069ea9e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f70474c6700 (LWP 16853)):
#0 __GI___pthread_mutex_lock (mutex=0x7f7038000a60) at pthread_mutex_lock.c:50
#1 0x00007f70628005c1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f70627c090b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f70627c10fe in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f70627c1304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f706adc7036 in QEventDispatcherGlib::processEvents (this=0x7f70380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6 0x00007f706ad9738f in QEventLoop::processEvents (this=this@entry=0x7f70474c5b10, flags=...) at kernel/qeventloop.cpp:149
#7 0x00007f706ad97618 in QEventLoop::exec (this=this@entry=0x7f70474c5b10, flags=...) at kernel/qeventloop.cpp:204
#8 0x00007f706ac99410 in QThread::exec (this=this@entry=0x2b6ab20) at thread/qthread.cpp:542
#9 0x00007f706ad78edf in QInotifyFileSystemWatcherEngine::run (this=0x2b6ab20) at io/qfilesystemwatcher_inotify.cpp:256
#10 0x00007f706ac9bbec in QThreadPrivate::start (arg=0x2b6ab20) at thread/qthread_unix.cpp:338
#11 0x00007f70651eff8e in start_thread (arg=0x7f70474c6700) at pthread_create.c:311
#12 0x00007f7069ea9e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f707054ba40 (LWP 16851)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007f706ac9c14b in wait (time=18446744073709551615, this=0x2b76cf0) at thread/qwaitcondition_unix.cpp:86
#2 QWaitCondition::wait (this=this@entry=0x2b76ca0, mutex=0x2b76c78, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3 0x00007f706ac9b7bc in QThread::wait (this=this@entry=0x2bc1ef0, time=time@entry=18446744073709551615) at thread/qthread_unix.cpp:691
#4 0x00000000005ce505 in Digikam::ScanController::shutDown (this=this@entry=0x2bc1ef0) at /build/buildd/digikam-3.3.0/core/digikam/database/scancontroller.cpp:361
#5 0x00000000005d1c9b in Digikam::ScanController::~ScanController (this=0x2bc1ef0, __in_chrg=<optimized out>) at /build/buildd/digikam-3.3.0/core/digikam/database/scancontroller.cpp:337
#6 0x00000000005d1e47 in ~ScanControllerCreator (this=0x2bc1ef0, __in_chrg=<optimized out>) at /build/buildd/digikam-3.3.0/core/digikam/database/scancontroller.cpp:277
#7 destroy () at /build/buildd/digikam-3.3.0/core/digikam/database/scancontroller.cpp:284
#8 0x00007f7069dec121 in __run_exit_handlers (status=1, listp=0x7f706a1716a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:77
#9 0x00007f7069dec1a5 in __GI_exit (status=<optimized out>) at exit.c:99
#10 0x00007f706b7ed2d8 in qt_xio_errhandler () at kernel/qapplication_x11.cpp:782
#11 0x00007f706c48c6a8 in KApplication::xioErrhandler (this=0x7fff72b97a70, dpy=0x29fcae0) at ../../kdeui/kernel/kapplication.cpp:419
#12 0x00007f70683855be in _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#13 0x00007f706838308d in _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#14 0x00007f706837465b in XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#15 0x00007f706b828b6c in x11EventSourceCheck (s=0x29d43d0) at kernel/qguieventdispatcher_glib.cpp:85
#16 0x00007f70627c0c69 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f70627c1175 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f70627c1304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f706adc7016 in QEventDispatcherGlib::processEvents (this=0x292aa60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#20 0x00007f706b82913e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#21 0x00007f706ad9738f in QEventLoop::processEvents (this=this@entry=0x2b8a610, flags=...) at kernel/qeventloop.cpp:149
#22 0x00007f706ad97618 in QEventLoop::exec (this=0x2b8a610, flags=...) at kernel/qeventloop.cpp:204
#23 0x00000000005d0ccb in Digikam::ScanController::databaseInitialization (this=0x2bc1ef0) at /build/buildd/digikam-3.3.0/core/digikam/database/scancontroller.cpp:425
#24 0x00000000005aab9e in Digikam::AlbumManager::setDatabase (this=0x2bc3240, params=..., priority=priority@entry=false, suggestedAlbumRoot=...) at /build/buildd/digikam-3.3.0/core/digikam/album/albummanager.cpp:717
#25 0x00000000004924ef in main (argc=5, argv=0x7fff72b97ca8) at /build/buildd/digikam-3.3.0/core/digikam/main/main.cpp:186

[/quote]

Hope this helps

no idea other than it appears to be album related
can you try as a new user or rename your and digikam rc and folder

ps - large amounts of text should be bracketed by code tags, quoted by quote tags

Code: Select all

 [code] large amounts of test [/code]
     [quote] quoted text [/quote]

google01103 wrote:no idea other than it appears to be album related
can you try as a new user or rename your and digikam rc and folder

ps - large amounts of text should be bracketed by code tags, quoted by quote tags

Code: Select all

 [code] large amounts of test [/code]
     [quote] quoted text [/quote]

Have already tried the removeal and renaming of the .kde digikam stuff. Will try the new user stuff latter this evening or tomorrow. I still think it may be related to KDE 4.11 and udisks2 stuff. When 4.11 first came out it was packaged with udisks1 and would not properly see USB's that were attached to systems, that was corrected with udisks2 being installed. But do not know that much about the original problem just drawing a uneducated guess. I noticed in the bugs data base that I was not the only one with a similar problem. I submitted and attached this one to a similar one.

I have been doing some more looking around and abandoning the idea of a problem created by KDE 4.11 and udisks2, instead I think that my database my have become corrupt during the conversion process see this article [urlhttp://ymartin59.free.fr/wordpress/index.php/2011/04/29/digikam-does-not-start-do-not-drop-your-database-yet-it-may-be-fixed/][/url] . Now my problem is that I have never used any database software. I probably can do the integerty check but the rest makes me to nervous to have any confidence that I could accomplish it correctly.

your use of tags is still a bit off, the "]" needs to follow "[url" not the actual url, also the forum automatically will make urls clickable it there's the http://

you could make a copy of the db before attempting anything

you might want to query the digikam mailinglist as suggested by the link you posted as that is the official method of Digikam support

I have done some more looking around and found a how to on using sqlite to look at the database. My data base is not corrupted. Using the data browser it seems all data is there, I also noted that the database is at version 4. I tried changing the data base version number to 5 and running digikam to convert it to version 6 but that failed. I then looked around for a earlier distro that contained a earlier version of digikam to try and convert but could not find one. If some one is running a earlier version of digikam that is using version 5 of the database would you be willing to try and convert the database for me? Thanks.

you should post on the mailinglist or irc as that's where the Digikam devs hang out