digikam 5.1 and 5.2 not starting on WIndows 10

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

digikam 5.1 and 5.2 not starting on WIndows 10

Eduard Zalar
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
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.

3. There have been several changes in the digikamapp.cpp since V5.0
I am not a C++ nor Qt nor Linux development expert, but I am also a developer (C# most of the time...). 
So I recognize that some lines have been changed/rearranged which may be important for the start sequence of digiKam.
As I wrote: With V5.0.0 I didn't had these problems.  The problems began with V5.1.0.


I really hope that all this information helps you to determine the root cause of this strange hang up.
I would really love to use digiKam!

With best regards
Eddie


digiKamLib.gz (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: digikam 5.1 and 5.2 not starting on WIndows 10

Gilles Caulier-4


2016-09-26 10:15 GMT+02:00 Eduard Zalar <[hidden email]>:
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
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
Reply | Threaded
Open this post in threaded view
|

Re: digikam 5.1 and 5.2 not starting on WIndows 10

Eduard Zalar
Hello Gilles,

my images collection is located in folder:
\Our Pictures
I organize my pictures per year, so the subfolders of this folder are 2011 to 2016.

I tried to place the library folder besides the images.  So I tried to configure:
\Our Pictures\digiKamLib

With this config, and starting digiKam the very first time after installation, the folder "\Our Pictures\digiKamLib" does not exist.
In this case the file "\Our Pictures\digiKamLib" is created first and the folder can not be created anymore...

I tried the same also using the folder:
\Users\<My account name>\digiKamLib
This folder is definitely outside of the folder where the images collection is located.
But it was the same behavior.

I also tried to use "\digiKam" and "\digiKam.lib" as folder names.  Every time, a file with the same name is created first and then the folder for the library can not be created anymore.

I hope this is better understandable.

BTW: Could you please tell me which is the default folder for the library?  
I installed and uninstalled digiKam so many times that I forgot the default locaton.  
Maybe I should configure digiKam to search and put the library folder in the default location and see what happens.

With best regards
Eddie

Gilles Caulier <[hidden email]> schrieb am Mo., 26. Sep. 2016 um 12:52 Uhr:
2016-09-26 10:15 GMT+02:00 Eduard Zalar <[hidden email]>:
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
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
Reply | Threaded
Open this post in threaded view
|

Re: digikam 5.1 and 5.2 not starting on WIndows 10

Eduard Zalar
Hello,

finally, I solved my "digiKam is not starting" problem by:

Uninstalling digiKam V5.2.
Deleting each and every digiKam related file which I found on my disk after uninstalling.
Rebooting.
Installing digiKam V5.2 and stepping again through the initial configuration.

Now, it works well.

With best regards
Eddie

Eduard Zalar <[hidden email]> schrieb am Mo., 26. Sep. 2016 um 16:32 Uhr:
Hello Gilles,

my images collection is located in folder:
\Our Pictures
I organize my pictures per year, so the subfolders of this folder are 2011 to 2016.

I tried to place the library folder besides the images.  So I tried to configure:
\Our Pictures\digiKamLib

With this config, and starting digiKam the very first time after installation, the folder "\Our Pictures\digiKamLib" does not exist.
In this case the file "\Our Pictures\digiKamLib" is created first and the folder can not be created anymore...

I tried the same also using the folder:
\Users\<My account name>\digiKamLib
This folder is definitely outside of the folder where the images collection is located.
But it was the same behavior.

I also tried to use "\digiKam" and "\digiKam.lib" as folder names.  Every time, a file with the same name is created first and then the folder for the library can not be created anymore.

I hope this is better understandable.

BTW: Could you please tell me which is the default folder for the library?  
I installed and uninstalled digiKam so many times that I forgot the default locaton.  
Maybe I should configure digiKam to search and put the library folder in the default location and see what happens.

With best regards
Eddie

Gilles Caulier <[hidden email]> schrieb am Mo., 26. Sep. 2016 um 12:52 Uhr:
2016-09-26 10:15 GMT+02:00 Eduard Zalar <[hidden email]>:
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
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