After restarting digikam, I noticed that the file not found message is thrown right after starting. Seems the only relevant error is coming from:
terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc digikam: Fatal IO error: client killed KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/rd/.kde/socket-blackbox/kdeinit4__0 On the command line, I can ls the directory without problems. Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/
signature.asc
Description: This is a digitally signed message part.
