Bug 245582 - When you try to save the blended image it will some times say can not save jpg such and such
Summary: When you try to save the blended image it will some times say can not save jp...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-ExpoBlending (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-23 22:30 UTC by Von Wallace
Modified: 2016-07-07 13:23 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Von Wallace 2010-07-23 22:30:25 UTC 
Version:           1.4.0
OS:                Linux

When you try to save the blended image it will some times say can not save jpg such and such... the jpg will not be saved or added to the digikam album but the png will be there and it is much bigger... I can work around this but it would be nice if it worked... I would say this happens every 4 to five times I use the program...

Also when this happens the wheel keeps spinning and the program is not aware of the problem... and it keeps spinning until you x out of the blending program...

 

Reproducible: Didn't try




OS: Linux (i686) release 2.6.32-24-generic
Compiler: cc
Comment 1 caulier.gilles 2010-07-24 09:13:36 UTC 
"to save the blended image" ??? from what ? image editor ? ExpoBlending tool ?

Gilles Caulier
Comment 2 caulier.gilles 2011-12-20 17:37:25 UTC 
Von,

Do you see my comment #1 ?

Gilles Caulier
Comment 3 caulier.gilles 2015-05-19 10:05:38 UTC 
Von,

This file still valid using last kipi-plugins 4.10.0 ?

Gilles Caulier
Comment 4 caulier.gilles 2015-06-29 17:53:05 UTC 
New Kipiplugins 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 5 caulier.gilles 2016-07-07 13:23:30 UTC 
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier