digikam 5.1 and 5.2 not starting on WIndows 10

Gilles Caulier caulier.gilles at gmail.com
Mon Sep 26 11:51:28 BST 2016


2016-09-26 10:15 GMT+02:00 Eduard Zalar <eduard at zalar.de>:

> Hello again,
>
> I still experience the same problem: I start digiKam 5.2.0 (the new
> installer, downloaded today.) - but it hangs up with a stale process in
> windows task manager.
> Only if I delete the library folder, digiKam starts up with the UI.  It
> creates the library folder with the 3 .db files inside.
> Now I close digiKam.
> I try to restart it - it again hangs up.
>
>
> I did some additional investigation:
>
> 1. There already exists a bug report with a similar description of the
> behavior in a comment: 345245
> <https://bugs.kde.org/show_bug.cgi?id=345245>
> The debug view output described here is basically the same as mine:
> 5568] ds\security\umstartup\usermgr\cli\usermgrcli.cxx(165)\
> usermgrcli.dll!00007FFF4BCA10FF: (caller: 00007FFF488391AB)
> ReturnHr[PreRelease](21) tid(22c0) 80070005 Zugriff verweigert
> [5568] base\appmodel\execmodel\modern\lifetimemanager\
> appxexecutionutil.cpp(40)\modernexecserver.dll!00007FFF4883928C: (caller:
> 00007FFF4884DCA5) ReturnHr[PreRelease](76) tid(22c0) 80070005 Zugriff
> verweigert
> [7320] Suspending
> "Zugriff verweigert" means "Access denied".
> Even if the initial bug report does not report the same behavior, the
> comments added later on describe it.
>
> 2. A file exists with the same name as the library folder
>
I observed the folder where the digiKam library should be created.  And
> here I recognized that a file is created with the same name as the library
> folder should have.  And that file is created before the folder is created
> and before the digiKam UI is shown.
> Sometimes, I also get the error message at digiKam startup that the folder
> can not be created - because there already exists a file with the same
> name.  But I can not reproduce this behaviour by now.
>
> If I delete the file, but NOT the library folder, digiKam starts up
> normally.
> Closing digiKam and restarting it results again in the hang up.
>
> I opened the file and it seems that this is a log file from the SQLite
> engine...  I attached it for your reference.
>

The file attched is a sqlite3 databse binary container, in fact the digiKam
database file...

I don't understand your investigations. You talk about a file name that is
the same than the library folder... Can you list exactly the contents of
you root directory where images collection and Sqlite database are hosted ?

Gilles Caulier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20160926/f3cabd0d/attachment.html>


More information about the Digikam-users mailing list