Bug 397554 - Digikam crashes while running BatchQueueManager
Summary: Digikam crashes while running BatchQueueManager
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: BatchQueueManager-Core (show other bugs)
Version: 5.6.0
Platform: Mint (Ubuntu based) Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-17 16:12 UTC by Tayvok
Modified: 2020-08-10 10:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0
Sentry Crash Report:


Attachments
Screenshot of log. (95.13 KB, image/png)
2018-08-17 16:12 UTC, Tayvok
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tayvok 2018-08-17 16:12:08 UTC
Created attachment 114466 [details]
Screenshot of log.

I previously used Lubuntu (18.04), and just barely switched to Mint 19 Tara XFCE release.

I've added several photos to the current batch queue manager, added about 7 steps in the workflow, and started running the queue.  It will run fine for at least five minutes, processing several photos successfully.  I'll leave my desk, and come back sometime later to find that Digikam has closed completely, crashed, with no explanation.  This particular problem was not happening in Lubuntu 18.04 before I switched, but I've repeated it three times in Mint.  In Lubuntu, whenever Digikam would crash, I would get the bug report prompt, but that isn't happening this time.  I will investigate that.  However, I did check the directories where the photos were being stored, and there were several that were not processed and or cut short of being processed fully.

My technical skill level is slightly above average - I've been using GNU+Linux for about ten years, but I may need instructions on how to provide any further relevant information.

I did search my system logs and found the following message.

Thread (pooled)[313]: segfault at 0 ip 00007ff87a4924b0 sp 00007ff761577da0 error 4 in libdigikamcore.so.5.6.0[7ff87a0da000+d18000]
Comment 1 caulier.gilles 2018-08-17 16:24:12 UTC
Sound like a broken binary compatibility from your native package.

Please test with official 5.9.0 Linux AppImage bundle to see if the problem is reproducible.

Gilles Caulier
Comment 2 Tayvok 2018-08-17 19:08:53 UTC
I completed a test with the official 5.9.0 Linux AppImage, as you suggested.

It did not have the same issue.  It seemed to work perfectly.
Comment 3 caulier.gilles 2018-08-17 21:09:53 UTC
Thanks for the feedback.

So the problem is certainly in the native DK package from your linux box.

Report this problem as your Linux team if necessary

Gilles Caulier
Comment 4 Tayvok 2018-08-17 21:13:11 UTC
Thank you for your help!