[Digikam-devel] [digikam] [Bug 335937] Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

[Gerrit Holl]

https://bugs.kde.org/show_bug.cgi?id=335937

--- Comment #1 from Gerrit Holl <gerrit.holl at gmail.com> ---
I upgraded to 3.5.0.  The crash persists and is reproducable, but the error
messages are not always the same:

$ digikam
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
terminate called recursively
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
Error: Could not determine display.
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
terminate called recursively
Unable to start Dr. Konqi
Not forwarding the crash to Apport.
$ digikam
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
terminate called recursively
terminate called recursively
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
Error: Could not determine display.
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
Error: Could not determine display.
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
terminate called recursively
Unable to start Dr. Konqi
terminate called after throwing an instance of 'St9bad_alloc'
terminate called recursively
terminate called recursively
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
digikam: Fatal IO error 9 (Bad file descriptor) on X server :0.0.
  what():  std::bad_alloc
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
Not forwarding the crash to Apport.

-- 
You are receiving this mail because:
You are the assignee for the bug.