[Digikam-users] DigiKam won't start

[John Carrick Smith]

Running openSUSE 11.4, DigiKam failed to start. It was suggested that I change 
the backed to xine - did this but no change. When starting digikam from a 
prompt this is the response:

KGlobal::locale::Warning your global KLocale is being recreated with a valid 
main component instead of a fake component, this usually means you tried to 
call i18n related functions before your main component was created. You should 
not do that since it most likely will not work 
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in 
use, all queries will cease to work.
Time elapsed: 42 ms
Model: Time elapsed: 1 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 21 ms
Time elapsed: 3 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 21 ms
digikam(6208)/KIPI (general) Plugin_DebianScreenshots::setup: virtual void 
Plugin_DebianScreenshots::setup(QWidget*) 
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
Qt Concurrent has caught an exception thrown from a worker thread.
This is not supported, exceptions thrown in worker threads must be
caught before control returns to Qt Concurrent.
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
QSocketNotifier: Invalid socket 39 and type 'Read', disabling...
QSocketNotifier: Invalid socket 42 and type 'Read', disabling...


Any ideas on how to cure?

I will need some guidance on how to produce diagnostics if required.

Thanks. John