[digiKam-users] Digikam 7.0 & 7.1 won't load past the flash screen

[Kent Dutton]

I have just installed Digikam 7.1 on a Windows 10 PC. It will not get past the splash screen, loading tools. 

As a user, not a programmer, I have not been able to find any help with my online searches.

I have re-installed version 6.1 and that will still work.

I look forward to any help you can suggest. I am sorry if this is the wrong place to ask for this help but it seems to be my last resort

[Gilles Caulier-4]

Hi,

Under Windows we need an extra tool from Microsoft to get extra debug
traces while digiKam run : DebugView.

Look more details at this page :

https://www.digikam.org/contribute/

Best

Gilles Caulier

Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a écrit :
>
> I have just installed Digikam 7.1 on a Windows 10 PC. It will not get past the splash screen, loading tools.
> As a user, not a programmer, I have not been able to find any help with my online searches.
> I have re-installed version 6.1 and that will still work.
> I look forward to any help you can suggest. I am sorry if this is the wrong place to ask for this help but it seems to be my last resort
> Kent Dutton

[Kent Dutton]

Hello Gilles

I have run the Debug View and have attached a file, hopes this is what you need.

Not sure what or where I am supposed to do this:

On Windows, application text output is not sent to the terminal. You need to install DebugView tool to capture text traces generated by digiKam.

Before to start digiKam and DebugView, from your Windows System Info panel, add a new user variable with these criteria:

    name: "QT_LOGGING_RULES"
    value: "digikam*=true"

On Thu, 31 Dec 2020 at 09:57, Gilles Caulier <[hidden email]> wrote:

Hi,

Under Windows we need an extra tool from Microsoft to get extra debug
traces while digiKam run : DebugView.

Look more details at this page :

https://www.digikam.org/contribute/

Best

Gilles Caulier

Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a écrit :
>
> I have just installed Digikam 7.1 on a Windows 10 PC. It will not get past the splash screen, loading tools.
> As a user, not a programmer, I have not been able to find any help with my online searches.
> I have re-installed version 6.1 and that will still work.
> I look forward to any help you can suggest. I am sorry if this is the wrong place to ask for this help but it seems to be my last resort
> Kent Dutton

[Maik Qualmann]

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.

But please remove this file as a test: C:/Users/Kent/Pictures/Family Tree/Dick
Ja 599-03.jpg

Maik

Am Donnerstag, 31. Dezember 2020, 07:20:59 CET schrieb Kent Dutton:

> Hello Gilles
> I have run the Debug View and have attached a file, hopes this is what you
> need.
> Not sure what or where I am supposed to do this:
>
> On Windows, application text output is not sent to the terminal. You need
> to install DebugView tool
> <http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx> to capture
> text traces generated by digiKam.
>
> Before to start digiKam and DebugView, from your Windows System Info panel,
> add a new user variable with these criteria:
>
>     name: "QT_LOGGING_RULES"
>     value: "digikam*=true"
>
> Kent Dutton
>
>
> On Thu, 31 Dec 2020 at 09:57, Gilles Caulier <[hidden email]>
>
> wrote:
> > Hi,
> >
> > Under Windows we need an extra tool from Microsoft to get extra debug
> > traces while digiKam run : DebugView.
> >
> > Look more details at this page :
> >
> > https://www.digikam.org/contribute/
> >
> > Best
> >
> > Gilles Caulier
> >
> > Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a
> >
> > écrit :
> > > I have just installed Digikam 7.1 on a Windows 10 PC. It will not get
> >
> > past the splash screen, loading tools.
> >
> > > As a user, not a programmer, I have not been able to find any help with
> >
> > my online searches.
> >
> > > I have re-installed version 6.1 and that will still work.
> > > I look forward to any help you can suggest. I am sorry if this is the
> >
> > wrong place to ask for this help but it seems to be my last resort
> >
> > > Kent Dutton

[Kent Dutton]

Hello

I have changed the file and removed it.

I'm sorry I do not understand what you mean by:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.  

 

I do not understand:

Before to start digiKam and DebugView, from your Windows System Info panel, add a new user variable with these criteria:

    name: "QT_LOGGING_RULES"
    value: "digikam*=true"

I have uninstalled then re-installed version 7.1 with no luck, I have re-installed version 6.1 and it works, I have attached another debugger file for you.

On Thu, 31 Dec 2020 at 18:12, Maik Qualmann <[hidden email]> wrote:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.

But please remove this file as a test: C:/Users/Kent/Pictures/Family Tree/Dick
Ja 599-03.jpg

Maik

Am Donnerstag, 31. Dezember 2020, 07:20:59 CET schrieb Kent Dutton:
> Hello Gilles
> I have run the Debug View and have attached a file, hopes this is what you
> need.
> Not sure what or where I am supposed to do this:
>
> On Windows, application text output is not sent to the terminal. You need
> to install DebugView tool
> <http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx> to capture
> text traces generated by digiKam.
>
> Before to start digiKam and DebugView, from your Windows System Info panel,
> add a new user variable with these criteria:
>
>     name: "QT_LOGGING_RULES"
>     value: "digikam*=true"
>
> Kent Dutton
>
>
> On Thu, 31 Dec 2020 at 09:57, Gilles Caulier <[hidden email]>
>
> wrote:
> > Hi,
> >
> > Under Windows we need an extra tool from Microsoft to get extra debug
> > traces while digiKam run : DebugView.
> >
> > Look more details at this page :
> >
> > https://www.digikam.org/contribute/
> >
> > Best
> >
> > Gilles Caulier
> >
> > Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a
> >
> > écrit :
> > > I have just installed Digikam 7.1 on a Windows 10 PC. It will not get
> >
> > past the splash screen, loading tools.
> >
> > > As a user, not a programmer, I have not been able to find any help with
> >
> > my online searches.
> >
> > > I have re-installed version 6.1 and that will still work.
> > > I look forward to any help you can suggest. I am sorry if this is the
> >
> > wrong place to ask for this help but it seems to be my last resort
> >
> > > Kent Dutton

[Gilles Caulier-4]

Hi Kent

Happy new year.

On operating systems such as Linux, macOS and Windows, it's possible to set up environment variables (strings tuple) to tune features at run time. This is the case to activate verbose debug trace from digiKam.

These env.var do not exist on your computer. You just need to append these variables on the list from the Windows computer properties panel. An example is given here, for assigning PATH variable :

https://www.computerhope.com/issues/ch000549.htm

This is exactly the same way to do for digiKam variables.

Gilles Caulier

Le jeu. 31 déc. 2020 à 22:01, Kent Dutton <[hidden email]> a écrit :

Hello

I have changed the file and removed it.

I'm sorry I do not understand what you mean by:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.  

 

I do not understand:

Before to start digiKam and DebugView, from your Windows System Info panel, add a new user variable with these criteria:

    name: "QT_LOGGING_RULES"
    value: "digikam*=true"

I have uninstalled then re-installed version 7.1 with no luck, I have re-installed version 6.1 and it works, I have attached another debugger file for you.

Kent Dutton

On Thu, 31 Dec 2020 at 18:12, Maik Qualmann <[hidden email]> wrote:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.

But please remove this file as a test: C:/Users/Kent/Pictures/Family Tree/Dick
Ja 599-03.jpg

Maik

Am Donnerstag, 31. Dezember 2020, 07:20:59 CET schrieb Kent Dutton:
> Hello Gilles
> I have run the Debug View and have attached a file, hopes this is what you
> need.
> Not sure what or where I am supposed to do this:
>
> On Windows, application text output is not sent to the terminal. You need
> to install DebugView tool
> <http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx> to capture
> text traces generated by digiKam.
>
> Before to start digiKam and DebugView, from your Windows System Info panel,
> add a new user variable with these criteria:
>
>     name: "QT_LOGGING_RULES"
>     value: "digikam*=true"
>
> Kent Dutton
>
>
> On Thu, 31 Dec 2020 at 09:57, Gilles Caulier <[hidden email]>
>
> wrote:
> > Hi,
> >
> > Under Windows we need an extra tool from Microsoft to get extra debug
> > traces while digiKam run : DebugView.
> >
> > Look more details at this page :
> >
> > https://www.digikam.org/contribute/
> >
> > Best
> >
> > Gilles Caulier
> >
> > Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a
> >
> > écrit :
> > > I have just installed Digikam 7.1 on a Windows 10 PC. It will not get
> >
> > past the splash screen, loading tools.
> >
> > > As a user, not a programmer, I have not been able to find any help with
> >
> > my online searches.
> >
> > > I have re-installed version 6.1 and that will still work.
> > > I look forward to any help you can suggest. I am sorry if this is the
> >
> > wrong place to ask for this help but it seems to be my last resort
> >
> > > Kent Dutton

[Kent Dutton]

Hello Gilles

Thank you very much for that.

I will get that setup over the weekend and try again for you.

On Sat, 2 Jan 2021 at 05:15, Gilles Caulier <[hidden email]> wrote:

Hi Kent

Happy new year.

On operating systems such as Linux, macOS and Windows, it's possible to set up environment variables (strings tuple) to tune features at run time. This is the case to activate verbose debug trace from digiKam.

These env.var do not exist on your computer. You just need to append these variables on the list from the Windows computer properties panel. An example is given here, for assigning PATH variable :

https://www.computerhope.com/issues/ch000549.htm

This is exactly the same way to do for digiKam variables.

Gilles Caulier

Le jeu. 31 déc. 2020 à 22:01, Kent Dutton <[hidden email]> a écrit :

Hello

I have changed the file and removed it.

I'm sorry I do not understand what you mean by:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.  

 

I do not understand:

Before to start digiKam and DebugView, from your Windows System Info panel, add a new user variable with these criteria:

    name: "QT_LOGGING_RULES"
    value: "digikam*=true"

I have uninstalled then re-installed version 7.1 with no luck, I have re-installed version 6.1 and it works, I have attached another debugger file for you.

Kent Dutton

On Thu, 31 Dec 2020 at 18:12, Maik Qualmann <[hidden email]> wrote:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.

But please remove this file as a test: C:/Users/Kent/Pictures/Family Tree/Dick
Ja 599-03.jpg

Maik

Am Donnerstag, 31. Dezember 2020, 07:20:59 CET schrieb Kent Dutton:
> Hello Gilles
> I have run the Debug View and have attached a file, hopes this is what you
> need.
> Not sure what or where I am supposed to do this:
>
> On Windows, application text output is not sent to the terminal. You need
> to install DebugView tool
> <http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx> to capture
> text traces generated by digiKam.
>
> Before to start digiKam and DebugView, from your Windows System Info panel,
> add a new user variable with these criteria:
>
>     name: "QT_LOGGING_RULES"
>     value: "digikam*=true"
>
> Kent Dutton
>
>
> On Thu, 31 Dec 2020 at 09:57, Gilles Caulier <[hidden email]>
>
> wrote:
> > Hi,
> >
> > Under Windows we need an extra tool from Microsoft to get extra debug
> > traces while digiKam run : DebugView.
> >
> > Look more details at this page :
> >
> > https://www.digikam.org/contribute/
> >
> > Best
> >
> > Gilles Caulier
> >
> > Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a
> >
> > écrit :
> > > I have just installed Digikam 7.1 on a Windows 10 PC. It will not get
> >
> > past the splash screen, loading tools.
> >
> > > As a user, not a programmer, I have not been able to find any help with
> >
> > my online searches.
> >
> > > I have re-installed version 6.1 and that will still work.
> > > I look forward to any help you can suggest. I am sorry if this is the
> >
> > wrong place to ask for this help but it seems to be my last resort
> >
> > > Kent Dutton

[Kent Dutton]

Hello Gilles

I have followed yout instructions and now have Digikam 7.2 BETA working. 

I am going to continue using this version as it seems to be working very well, it seems very much quicker than v6.1

I want to thank you guys for all the time and help, keep up the great work.

Thanks

On Sat, 2 Jan 2021 at 06:54, Kent Dutton <[hidden email]> wrote:

Hello Gilles

Thank you very much for that.

I will get that setup over the weekend and try again for you.

Kent Dutton

On Sat, 2 Jan 2021 at 05:15, Gilles Caulier <[hidden email]> wrote:

Hi Kent

Happy new year.

On operating systems such as Linux, macOS and Windows, it's possible to set up environment variables (strings tuple) to tune features at run time. This is the case to activate verbose debug trace from digiKam.

These env.var do not exist on your computer. You just need to append these variables on the list from the Windows computer properties panel. An example is given here, for assigning PATH variable :

https://www.computerhope.com/issues/ch000549.htm

This is exactly the same way to do for digiKam variables.

Gilles Caulier

Le jeu. 31 déc. 2020 à 22:01, Kent Dutton <[hidden email]> a écrit :

Hello

I have changed the file and removed it.

I'm sorry I do not understand what you mean by:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.  

 

I do not understand:

Before to start digiKam and DebugView, from your Windows System Info panel, add a new user variable with these criteria:

    name: "QT_LOGGING_RULES"
    value: "digikam*=true"

I have uninstalled then re-installed version 7.1 with no luck, I have re-installed version 6.1 and it works, I have attached another debugger file for you.

Kent Dutton

On Thu, 31 Dec 2020 at 18:12, Maik Qualmann <[hidden email]> wrote:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.

But please remove this file as a test: C:/Users/Kent/Pictures/Family Tree/Dick
Ja 599-03.jpg

Maik

Am Donnerstag, 31. Dezember 2020, 07:20:59 CET schrieb Kent Dutton:
> Hello Gilles
> I have run the Debug View and have attached a file, hopes this is what you
> need.
> Not sure what or where I am supposed to do this:
>
> On Windows, application text output is not sent to the terminal. You need
> to install DebugView tool
> <http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx> to capture
> text traces generated by digiKam.
>
> Before to start digiKam and DebugView, from your Windows System Info panel,
> add a new user variable with these criteria:
>
>     name: "QT_LOGGING_RULES"
>     value: "digikam*=true"
>
> Kent Dutton
>
>
> On Thu, 31 Dec 2020 at 09:57, Gilles Caulier <[hidden email]>
>
> wrote:
> > Hi,
> >
> > Under Windows we need an extra tool from Microsoft to get extra debug
> > traces while digiKam run : DebugView.
> >
> > Look more details at this page :
> >
> > https://www.digikam.org/contribute/
> >
> > Best
> >
> > Gilles Caulier
> >
> > Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a
> >
> > écrit :
> > > I have just installed Digikam 7.1 on a Windows 10 PC. It will not get
> >
> > past the splash screen, loading tools.
> >
> > > As a user, not a programmer, I have not been able to find any help with
> >
> > my online searches.
> >
> > > I have re-installed version 6.1 and that will still work.
> > > I look forward to any help you can suggest. I am sorry if this is the
> >
> > wrong place to ask for this help but it seems to be my last resort
> >
> > > Kent Dutton

[Gilles Caulier-4]

Thanks for your feedback and happy new year.

Best regards

Gilles Caulier

Le sam. 2 janv. 2021 à 07:55, Kent Dutton <[hidden email]> a écrit :

Hello Gilles

I have followed yout instructions and now have Digikam 7.2 BETA working. 

I am going to continue using this version as it seems to be working very well, it seems very much quicker than v6.1

I want to thank you guys for all the time and help, keep up the great work.

Thanks

Kent Dutton

On Sat, 2 Jan 2021 at 06:54, Kent Dutton <[hidden email]> wrote:

Hello Gilles

Thank you very much for that.

I will get that setup over the weekend and try again for you.

Kent Dutton

On Sat, 2 Jan 2021 at 05:15, Gilles Caulier <[hidden email]> wrote:

Hi Kent

Happy new year.

On operating systems such as Linux, macOS and Windows, it's possible to set up environment variables (strings tuple) to tune features at run time. This is the case to activate verbose debug trace from digiKam.

These env.var do not exist on your computer. You just need to append these variables on the list from the Windows computer properties panel. An example is given here, for assigning PATH variable :

https://www.computerhope.com/issues/ch000549.htm

This is exactly the same way to do for digiKam variables.

Gilles Caulier

Le jeu. 31 déc. 2020 à 22:01, Kent Dutton <[hidden email]> a écrit :

Hello

I have changed the file and removed it.

I'm sorry I do not understand what you mean by:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.  

 

I do not understand:

Before to start digiKam and DebugView, from your Windows System Info panel, add a new user variable with these criteria:

    name: "QT_LOGGING_RULES"
    value: "digikam*=true"

I have uninstalled then re-installed version 7.1 with no luck, I have re-installed version 6.1 and it works, I have attached another debugger file for you.

Kent Dutton

On Thu, 31 Dec 2020 at 18:12, Maik Qualmann <[hidden email]> wrote:

The log contains many messages from other programs, but little from digiKam,
because the debug output is not active. The environment variable must be set.

But please remove this file as a test: C:/Users/Kent/Pictures/Family Tree/Dick
Ja 599-03.jpg

Maik

Am Donnerstag, 31. Dezember 2020, 07:20:59 CET schrieb Kent Dutton:
> Hello Gilles
> I have run the Debug View and have attached a file, hopes this is what you
> need.
> Not sure what or where I am supposed to do this:
>
> On Windows, application text output is not sent to the terminal. You need
> to install DebugView tool
> <http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx> to capture
> text traces generated by digiKam.
>
> Before to start digiKam and DebugView, from your Windows System Info panel,
> add a new user variable with these criteria:
>
>     name: "QT_LOGGING_RULES"
>     value: "digikam*=true"
>
> Kent Dutton
>
>
> On Thu, 31 Dec 2020 at 09:57, Gilles Caulier <[hidden email]>
>
> wrote:
> > Hi,
> >
> > Under Windows we need an extra tool from Microsoft to get extra debug
> > traces while digiKam run : DebugView.
> >
> > Look more details at this page :
> >
> > https://www.digikam.org/contribute/
> >
> > Best
> >
> > Gilles Caulier
> >
> > Le mer. 30 déc. 2020 à 21:12, Kent Dutton <[hidden email]> a
> >
> > écrit :
> > > I have just installed Digikam 7.1 on a Windows 10 PC. It will not get
> >
> > past the splash screen, loading tools.
> >
> > > As a user, not a programmer, I have not been able to find any help with
> >
> > my online searches.
> >
> > > I have re-installed version 6.1 and that will still work.
> > > I look forward to any help you can suggest. I am sorry if this is the
> >
> > wrong place to ask for this help but it seems to be my last resort
> >
> > > Kent Dutton