Bug 273508 - DigiKam doesn't shutdown after using BQM
Summary: DigiKam doesn't shutdown after using BQM
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: BatchQueueManager-Core (show other bugs)
Version: 1.9.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-17 20:32 UTC by regi.hops
Modified: 2012-06-27 10:11 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description regi.hops 2011-05-17 20:32:06 UTC
Version:           1.9.0 (using KDE 4.6.2) 
OS:                Linux

After using the BQM - lets say to resize some pictures - closing (shutdown) DigiKam, everything looks fine.
But when you take a look in the systemmonitor you will still see a DigiKam process in the list consuming resources.
You must manually kill the process.
This only happens if you use BQM, if you don't use it DigiKam exits normally.

Reproducible: Always

Steps to Reproduce:
Start DigiKam
Select a few pictures
Start BQM
Drag and drop the selected pictures into the queue
Resize the pictures
Close QBM
Close DigiKam


Actual Results:  
Look into the systemmonitor, DigiKam is still active


Expected Results:  
DigiKam should shutdown
Comment 1 caulier.gilles 2011-05-18 07:44:12 UTC
Which resize options you use ?

Gilles Caulier
Comment 2 regi.hops 2011-05-22 21:47:38 UTC
Mostly I use a userdefined size i.e. 1920.
But the problem is not bound to the resize tool.
It happens with all 3 tools from the transformation category.

These are the ones I often use, I will try some other tools and report if it's happens too.

Cheers
Regi
Comment 3 Andi Clemens 2011-10-24 22:01:15 UTC
Hmm I can not reproduce this bug.

regi.hops@gmx.net,
can you reproduce this behavior every time you use BQM and close digiKam?
Comment 4 regi.hops 2011-11-05 19:33:14 UTC
Sorry I couldn't reply earlier and test other versions, as my ISP had a long term problem which they solved this month.

I just updated my system and tested with version 2.2.0 and it did not happen anymore.

Thanks a lot for your assistance

Cheers
Regi