DK crashes when using Batch Queue Manager

[Gilles Caulier]

>From You log :

00000347    8.95806599    [10928] digikam.general: Event is dispatched
using KDE desktop notifier
00000348    8.97414207    [10196]  "C:\\Program
Files\\digiKam\\SnoreToast.exe" v 0.8.0
00000349    8.97414207    [10196]   class
std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class
std::allocator<wchar_t> > __cdecl getAppId(const class
std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class
std::allocator<wchar_t> > &,const class
std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class
std::allocator<wchar_t> > &)
00000350    8.97414207    [10196]    Failed to retreive appid for
10928  Process is a desktop application
00000351    8.97932529    [10196]  "C:\\Program
Files\\digiKam\\SnoreToast.exe" v 0.8.0
00000352    8.97932529    [10196]   void __cdecl SnoreToasts::printXML(void)
00000353    8.97932529    [10196]    ------------------------
00000354    8.97932529    [10196]     <toast
launch="action=clicked;notificationId=1;pipe=\\.\pipe\13370466737138538959;version=0.8.0;"
duration="short"><visual><binding
template="ToastImageAndText02"><image id="1"
src="C:\Users\aval\AppData\Local\Temp\digikam-pdDKYz\1"/><text
id="1">digiKam</text><text id="2">Process is done. Duration:
00:00:00</text></binding></visual><audio
src="ms-winsoundevent:Notification.Default" silent="false"/></toast>
00000355    8.97932529    [10196]    ------------------------
00000356    15.39396191    [10196]  "C:\\Program
Files\\digiKam\\SnoreToast.exe" v 0.8.0
00000357    15.39396191    [10196]   long __cdecl
ToastEventHandler::Invoke(struct
ABI::Windows::UI::Notifications::IToastNotification *,struct
ABI::Windows::UI::Notifications::IToastDismissedEventArgs *)
00000358    15.39396191    [10196]    The toast has timed out
00000359    15.39419174    [10196]  "C:\\Program
Files\\digiKam\\SnoreToast.exe" v 0.8.0
00000360    15.39419174    [10196]   bool __cdecl
Utils::writePipe(const class std::filesystem::path &,const class
std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class
std::allocator<wchar_t> > &,bool)
00000361    15.39419174    [10196]    Wrote:
action=timedout;notificationId=1;pipe=\\.\pipe\13370466737138538959;version=0.8.0;
 to  "\\\\.\\pipe\\13370466737138538959"
00000362    25.61992455    [5872] Suspending
00000363    27.64163208    [10928] digikam.geoiface: ----
00000364    41.25556564    [10928] digikam.general: Cannot find an
album for  QUrl("")

Did you see a notification from digiKam on your Windows desktop before
the crash ?

Best regards

Gilles Caulier

Le mer. 29 avr. 2026 à 09:23, Gilles Caulier
<caulier.gilles at gmail.com> a écrit :
>
> Hi,
>
> It's not reproducible at all on my laptop DELL Windows 11 (up-to-date)
> using build from today :
>
> https://flic.kr/p/2sacPxh
>
> Which GPU card did you use ? Here it's CPU i5-8265U + 32Gb of RAM +
> GPU Intel 620 HUD.
>
> Best Regards
>
> Gilles Caulier
>
> Le mer. 29 avr. 2026 à 08:32, Andrej Valencic
> <andrej.valencic at zoho.com> a écrit :
> >
> > Hello!
> >
> > I'm using the latest version of DK on Windows 11:
> >
> > digiKam: 9.1.0
> > KDE Frameworks: 6.25.0
> > Qt: Using 6.10.2 and built against 6.10.2
> > Windows 11 Version 25H2
> > Build ABI: x86_64-little_endian-llp64
> > Kernel: winnt 10.0.26200
> >
> > Every time I try to use the BQM the program just crashes. For example
> > when I add and item ( <Ctrl-b>) to the queue and try to assign one of
> > the saved Workflows to this queue DK crashes. The same happens if I add
> > an item and then choose Remove Queue - DK crashes. On the other hand it
> > works OK if I add an item and then just add some of the Base Tools and
> > run the Queue - but this is very inconvenient to use every time. And
> > removing items from the queue also works without problem.
> >
> > I tried to capture the logs but there seems to be nothing regarding this
> > issue (enclosed is the log from start of the DK to the final crash).
> >
> > Any ideas of what is happening and is there something else I could try
> > to get this working?
> >
> > P.S. It was working fine a couple of versions before but I'm not sure
> > which one started to expose this error.
> >
> > Regards,
> > Andrej