Bug 155950 - raw file open with action causes two instances
Summary: raw file open with action causes two instances
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Usability-OpenWith (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-16 22:11 UTC by Simon Oosthoek
Modified: 2022-01-31 07:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Oosthoek 2008-01-16 22:11:56 UTC
Version:           0.9.3 (using 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.1)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-14-generic

When I try to open a .ARW (sony raw) file in the gimp, for which I made a new entry in the file associations of KDE, I get the active instance of the gimp via gimp-remote (as configured) and a second instance of the gimp after a while (say 20s later). This is very annoying, because it consumes CPU and memory, thus slowing down whetever I'm doing, which is also CPU/mem intensive...

I don't know if my specific situation is causing this, but I'm willing to try suggestions if this cannot be explained by a bug...

Cheers

Simon
Comment 1 caulier.gilles 2008-03-10 16:32:32 UTC
Arnd,

This entry is relevant of Gimp not digiKam directly...

Gilles Caulier
Comment 2 Arnd Baecker 2008-03-10 17:15:22 UTC
Simon, could you try to associate a shell script with .ARW
files and let this script gives some "debug" output,
like
   echo "Starting shell script"
   gimp-remote ...
   echo "finished shell script"
maybe with the passed filename etc.
This should reveal, whether digikam calls this script twice,
or whether it is a gimp-remote problem (i.e. by running the script
from the command line).

Best, Arnd
 
Comment 3 Simon Oosthoek 2008-03-10 20:31:38 UTC
While trying to implement this test script, I noticed I had two entries for .arw in the file associations found in kcontrol. One (image/x-raw), to which I think I remember adding the .arw extension. The other is image/x-sony-raw. The list of applications is different and also the way gimp is called of those options is different. I also think I remember adding the image/x-sony-raw type (in an attempt to get digikam to list applications for the .arw raw format).

In the image/x-raw type, gimp is called as "gimp", the other image/x-sony-raw is using gimp-remote. If both associations are followed and called, it would explain the double instance of the gimp, due to one of them calling gimp, instead of gimp-remote. I don't think this can be a bug of gimp-remote, since I usually use that to open files with the gimp and only digikam shows this behaviour. I suspect it may be a strange interaction between digikam and the kde file associations, of which I understand very little...

I hope this helps (I assume the test-script is no longer necessary, since this appears to be a much saner explanation than a weird double execute in gimp-remote ;-)

Cheers

Simon
Comment 4 Arnd Baecker 2008-03-10 21:11:44 UTC
Shouldn't then removing the .arw entry for image/x-raw solve the problem
so that this bug can be closed?
Comment 5 Simon Oosthoek 2008-03-10 21:27:14 UTC
I suppose so, as I can't tell whether this is caused by digikam or the file associations API...
Comment 6 caulier.gilles 2019-12-23 17:47:19 UTC
Not reproducible with digiKam 7.0.0-beta1.