Bug 161492 - crash when converting nikon raw (nef) image to anything
Summary: crash when converting nikon raw (nef) image to anything
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: BatchQueueManager-RAWProcessing (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-01 15:21 UTC by Arnaud de Villèle
Modified: 2018-03-23 11:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.3.0


Attachments
Backtrace produced by Kcrash (2.44 KB, text/plain)
2008-07-18 22:47 UTC, Stefan Nordhausen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arnaud de Villèle 2008-05-01 15:21:13 UTC
Version:            (using KDE 3.5.8)
Installed from:    SuSE RPMs

any conversion (single or batch) from nef files (raw ala nikon) crashes digikam, my dcraw version is 8.77, digikam is 0.9.3

weirdly, dcraw on command line works great...

I'll attach a sample file, don't know if bugzilla will like that kind of size.
Comment 1 caulier.gilles 2008-05-01 15:29:29 UTC
Arnaud,

This is RAW converter kipi-plugin. Which version of kipi-plugins you use ?

Gilles Caulier
Comment 2 Arnaud de Villèle 2008-05-01 16:39:06 UTC
rpm -qa | grep kipi :


kipi-plugins-0.1.4-38
libkipi-lang-0.1.5-84
libkipi-0.1.5-84
kipi-plugins-lang-0.1.4-38
Comment 3 Stefan Nordhausen 2008-07-18 22:47:47 UTC
Created attachment 26245 [details]
Backtrace produced by Kcrash
Comment 4 Stefan Nordhausen 2008-07-18 23:02:43 UTC
I had the same problem and tried to fix it by updating to the newest version of kipi. The result was that now even _opening_ the raw converter dialog crashes, even when there are no raws in the directory.

Just like Arnaud, I have a Suse system (openSuse 10.3)... I have the following versions installed:

$rpm -qa | grep kipi | sort
 kipi-plugins-0.1.5-1.pm.1
 kipi-plugins-debuginfo-0.1.5-1.pm.1
 libkipi-0.1.6-0.pm.1
 libkipi-debuginfo-0.1.6-0.pm.1

I have attached a trace produced by Kcrash. It indicates that something goes wrong while loading the settings. I get similar results when running strace on digikam:

open("/home/johndoe/.kde/share/config/kipirc", O_RDONLY|O_LARGEFILE) = 20
[...]
close(20)                               = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

So it crashes right after closing the file. If I remove the kipirc file I get this:

stat64("/home/johndoe/.kde/share/config/kipirc", 0xbfa636c8) = -1 ENOENT (No such file or directory)
stat64("/etc/opt/kde3/share/config/kipirc", 0xbfa636c8) = -1 ENOENT (No such file or directory)
stat64("/opt/kde3/share/config/kipirc", 0xbfa636c8) = -1 ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

Comment 5 Andi Clemens 2008-08-03 08:36:46 UTC
I can't confirm this right now. I have a Nikon D50, importing, converting single and batch just works fine.

I'm using the latest libs / digiKam / kipi-plugins from SVN, so this might not be any help...

Arnaud, you said you want to attach a sample file (this will not work because of the file-size I think), but you can sent the file by mail either to me or the mailing list (digikam-devel@kde.org, kde-imaging@kde.org). But I'm not sure if the mailing list will accept an attachment like that.

Andi
Comment 6 Arnaud de Villèle 2008-08-04 11:37:38 UTC
As soon as I get my hands back on my computer, i'll test again and put the
problematic file on an ftp for you

2008/8/3 Andi Clemens <andi.clemens@gmx.net>

[bugs.kde.org quoted mail]
<div dir="ltr">As soon as I get my hands back on my computer, i&#39;ll test again and put the problematic file on an ftp for you<br><br><div class="gmail_quote">2008/8/3 Andi Clemens <span dir="ltr">&lt;<a href="mailto:andi.clemens@gmx.net">andi.clemens@gmx.net</a>&gt;</span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>
You reported the bug, or are watching the reporter.<br>
<br>
<a href="http://bugs.kde.org/show_bug.cgi?id=161492" target="_blank">http://bugs.kde.org/show_bug.cgi?id=161492</a><br>
<br>
<br>
<br>
<br>
------- Additional Comments From andi.clemens gmx net &nbsp;2008-08-03 08:36 -------<br>
I can&#39;t confirm this right now. I have a Nikon D50, importing, converting single and batch just works fine.<br>
<br>
I&#39;m using the latest libs / digiKam / kipi-plugins from SVN, so this might not be any help...<br>
<br>
Arnaud, you said you want to attach a sample file (this will not work because of the file-size I think), but you can sent the file by mail either to me or the mailing list (digikam-devel kde org, kde-imaging kde org) &nbsp;But I&#39;m not sure if the mailing list will accept an attachment like that.<br>

<font color="#888888"><br>
Andi<br>
<br>
</font></blockquote></div><br></div>
Comment 7 caulier.gilles 2008-12-07 21:29:12 UTC
Arnaud,

This file still valid using kipi-plugins 0.1.6 ?

Gilles Caulier
Comment 8 Andi Clemens 2009-05-10 10:07:28 UTC
I will test this now again, if I can't reproduce it, I will close it. We haven't heard from Arnaud since 5 months, so we need to make a cut someday :-)

Andi
Comment 9 Andi Clemens 2009-05-10 10:14:23 UTC
Ok, works fine here. Nikon D50 NEF files, latest KIPI of course and those additional libs and components: 

digiKam version 0.11.0-svn
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibExiv2: 0.18
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.2.3 (KDE 4.2.3)
LibKExiv2: 0.6.0
LibKdcraw: 0.5.0
LibLCMS: 118
LibPNG: 1.2.36
LibQt: 4.5.1
LibRaw: 0.7.2-Release
LibTIFF: LIBTIFF, Version 3.8.2 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble widget: 0.7.1
Parallelized demosaicing: Yes
LibGphoto2: 2.4.4
LibKipi: 0.4.0


Arnaud,
if it is still happening to you, then please try to update to the newest packages available. If you still have these issues, it most be a packaging problem of SUSE, because it works in other distributions.
We cannot help in such a case, try contacting the SUSE packager directly.

I will close this bugreport now.

Andi