When right-clicking on a Raw image, I cannot open it in the Gimp

Bug #223400 reported by Spider
16
Affects Status Importance Assigned to Milestone
F-Spot
Won't Fix
Medium
f-spot (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

I have a mix of jpeg and RAW (.CR2, canon) images. When browsing with Nautilus, I can double-click an .CR2 image and it opens in The Gimp, ( meaning: my mime types are configured correctly) but from inside f-spot, it will only recognize UFRaw, and will not let me open it in the Gimp.

With normal JPEG's, I'm allowed to use the Gimp from inside f-spot.

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, what ubuntu version do you use? could you attach an image example to the bug?

Changed in f-spot:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Spider (spider-alternating) wrote :

Hardy Heron 32bit

Revision history for this message
Alex Lubberts (delub) wrote :

Same here with CRW-images: in Nautilus I get the options open with Gimp or F-Spot, but F-Spot claims there are no applications available to open my CRW-files (I only have gimp-ufraw installed, not the standalone ufraw). In Gutsy everything worked fine.

Revision history for this message
Alex Lubberts (delub) wrote :

On my system it works again. What I did:
* In /usr/share/applications/gimp.desktop I added at the end of the line MimeType= ... "image/x-dcraw;"
* In /usr/share/application-registry/gimp.applications I added at the end of the line Mime_typs ... ",image/x-dcraw"
* I ran 'sudo update-desktop-database /usr/share/applications/'
* logout / login

Revision history for this message
StuartYeates (stuart-yeates) wrote :

I can confirm that I see this bug too.

This is actually a bug in ufraw and gimp-ufraw, which should both add mimetype information.

Revision history for this message
StuartYeates (stuart-yeates) wrote :

change the package this bug is assigned too

Changed in f-spot:
status: Incomplete → Confirmed
Revision history for this message
Guilherme Salgado (salgado) wrote :

If your raw files happen to be from a Nikon camera (NEF), you can do what Alex Lubberts suggested, replacing x-dcraw with x-nikon-nef.

Revision history for this message
Kaspar Metz (kap) wrote :

I have a very similar, if not the same problem. I tried to be able to open .nef-files (image/x-nikon-nef) using f-spots context menu with gimp and rawtherapee. I did all steps Alex Lubberts suggested, but it didn't work. In the nautilus context menu the new "Open with RawTherapee" selection appears as expected - not in f-spot. The selection is also different between nautilsu and f-spot for other files/mimetypes, such as image/jpeg.

It seems to me that f-spot somehow lost sync to what nautilus/gnome does.

Revision history for this message
Olle E (olle-enander) wrote :

This bug seems to prevail in Intrepid (32-bit) as well.

I can choose open with Gimp in Nautilus, causing UFRaw to load the image. Right-clicking in F-spot on the other hand shows no available apps for editing.
It is hard to say as a layman/regular user if the problem is in F-spot, Gimp or UFRaw, however the "interaction-problem" seems to be in F-spot. This is quite annoying as I frequently shoot RAW, and this complicates the workflow.

I'm using gimp-ufraw 0.14.1

Revision history for this message
Olle E (olle-enander) wrote :

It seems that the fix by Alex Lubberts (above) works with a couple of tweaks:
For Canon add "image/x-canon-cr2;" and/or "image/x-canon-crw;"
Also note that the /usr/share/application-registry/gimp.applications should be:
/usr/share/application-registry/gnome-vfs.applications

After all it seems that UFRaw is the culprit here as it apparently does not add the mime types.

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

There is a gimp-ufraw package... Which allows GIMP to open the raws using UFRaw...

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

Is this bug still about F-Spot?

Anyway GIMP and F-Spot do not natively support raw files, and need UFRaw for that...

For GIMP there's the gimp-ufraw package...

For F-Spot there a plugin called "DevelopInUFRaw" which develops the raw file, and the resulting jpg/tif is re-imported into F-Spot as a new version of the older raw.

The raw preview f-spot displays is nothing more than a preview, and cannot be edited or exported...

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

Sorry for the seperate posts...

But you cannot open a raw using gimp(-ufraw) from within F-Spot, when F-Spot opens a file with the GIMP it copies the file, and opens the copy. F-Spot expects the GIMP to save to the same file, and you cannot save to raw. You save to a JPG (or whatever), but F-Spot cannot know to what JPEG you just saved...

This is where the F-Spot DevelopInUFRaw extension comes in... The extension calls the standalone UFRaw with the raw file as parameters _and_ a target jpeg as parameters. This way F-Spot determines which raw is developed into _what_ jpeg file. Once UFRaw has closed, the target jpeg to reimported as a new version.

The proper workflow:
 RAW file -> DevelopInUFRaw -> Open with GIMP

Revision history for this message
Olle E (olle-enander) wrote :

Thanks for the intended workflow clarification.
It seems that when launching ufraw from f-spot via the right-click =>"edit in gimp" (as enabled above) no new version of the pic is created in the f-spot database.
The problem then is that actually nothing happens when choosing "Develop in UF-raw". A separate bug perhaps..?

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

You need of course to have the standalone ufraw binary installed...

Also, you can run f-spot --debug and look at the terminal to see what's happening...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, is this still an issue with Intrepid or Jaunty? could you provide us of a f-spot log asked in the previous comment? thanks.

Changed in f-spot:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Spider (spider-alternating) wrote :

Intrepid still does not have the right Mime-types.
The "Develop in UF-raw" is _not_ an option for real use as it involves a meta-stage that is very lossy in comparison. (RAW->Jpeg->Edit is a _bad_ move compared to RAW->Edit) and frankly, even suggesting such a workflow shows an obvious lack of insight into why a photographer would use RAW to begin with.

Also, Do note that while f-spot might "expect" a distinct copy, it should be fully acceptable to use F-spot as the launcher for further editing in the Gimp and not be expected to save the files in the exact same place and work location. For example, Editing would commonly involve changing format to the gimp's internal state so you can keep track of layers/channels, and then exports from that format to others.

Now, Just what from this log is it that you expect to see, the page after page of

 [Debug 14:35:54.816] open uri = file:///media/store/ ...... ?

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

"even suggesting such a workflow shows an obvious lack of insight into why a photographer would use RAW to begin with"

Well, this is a bit of an elitist remark. Don't get me wrong, you're right, but the lossyness of JPEG at 100% isn't bad, and UFRaw disables subsampling at 92% or better.

The current solution is quite workable... But it's not ideal...

Revision history for this message
Spider (spider-alternating) wrote :

Yes, it is a bit elitistic, but we are talking about a Fair bit more than simple jpeg compression error, you lose 4 bits per pixel channel of information as well.

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

Yes, but that doesn't really matter. GIMP only does 8bit anyways... and Krita isn't really ready for prime time...

Revision history for this message
StuartYeates (stuart-yeates) wrote : Re: [Bug 223400] Re: When right-clicking on a Raw image, I cannot open it in the Gimp

I use RawTherapee, which seems to be ready.

cheers
stuart

On Sat, Jan 24, 2009 at 4:29 AM, Pascal de Bruijn <email address hidden> wrote:
> Yes, but that doesn't really matter. GIMP only does 8bit anyways... and
> Krita isn't really ready for prime time...
>
> --
> When right-clicking on a Raw image, I cannot open it in the Gimp
> https://bugs.launchpad.net/bugs/223400
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

RawTherapee is equivalent to UFRaw... not GIMP or Krita...

Anyway RawTherapee is quite limited in it's management capabilities, for instance the lack of tags, and export to the web...

And RawTherapee isn't open source...

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in jaunty?

Revision history for this message
Guilherme Salgado (salgado) wrote :

yes, it's still an issue in jaunty

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

Still this issue is not related to UFRaw... only to F-Spot...

Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug should be sent to the software writters on bugzilla.gnome.org by somebody having the issue

Changed in f-spot (Ubuntu):
status: Incomplete → New
Revision history for this message
Jean Levasseur (levasseur.jean) wrote :

I cannot reproduce the bug anymore on Karmic, as long as I have "gimp-ufraw" package installed. Perhaps, this bug shall fall into the "fix release" category?

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

Ugh, even then it's not recommended... Don't open RAW files straight in GIMP from F-Spot... There's a good chance F-Spot won't import them back right again.

Revision history for this message
Jean Levasseur (levasseur.jean) wrote :

Upstream bug linked and updated

Changed in f-spot:
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for sending the bug to GNOME

Changed in f-spot (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: New → Triaged
Changed in f-spot:
importance: Unknown → Medium
Changed in f-spot:
status: New → Won't Fix
Revision history for this message
Mathew Hodson (mhodson) wrote :

f-spot isn't included in recent Ubuntu releases. Changing to Won't Fix.

Changed in f-spot (Ubuntu):
status: Triaged → Won't Fix
no longer affects: ufraw (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.