Crash appears in Exiv2, not digiKam.

Please update to last Exiv2 0.15 and last libkexiv2 0.1.2

Gilles Caulier

Op zaterdag 13-10-2007 om 18:48 uur [tijdzone +0000], schreef Gilles
Caulier:
[bugs.kde.org quoted mail]

Gilles, thanks for the fast reply.

I have installed:  libexiv2c2a_0.7-9.1ubuntu1_i386.deb ---> OK
(not libkexiv )

Ihave tried to install: exiv2_0.15-1ubuntu2_i386.deb  
---> error depenedncy is not satisfiable libc6

OK, whats next ;-) ?

Harry

Achim,

As Debian packager, have you few tips to give in this room ?

Gilles

Harry,

It may be faster if you install Exiv2 from source. Download it from www.exiv2.org and install as per the README.

Before you do that: Can you run the exiv2 command line utility with all the images in your collection to see if any of the images causes the problem. If you manage to crash the utility with a specific image, please post or send me the image.

Andreas

Op zondag 14-10-2007 om 09:23 uur [tijdzone +0000], schreef Andreas
Huggel:
[bugs.kde.org quoted mail]


Andreas, thanks for teh quick reply.
I have done following:

========================================

wolf@WolfZorrito:/media/photofat32/0319$ exiv2
The program 'exiv2' is currently not installed.  You can install it by
typing:
sudo apt-get install exiv2
bash: exiv2: opdracht niet gevonden

=====================================================


wolf@WolfZorrito:/media/photofat32/0319$ sudo apt-get install exiv2
Password:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd       
Reading state information... Klaar
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
  linux-headers-2.6.20-15-generic libkexif1 libgphoto2-2-dev libusb-dev
linux-headers-2.6.20-15
Gebruik 'apt-get autoremove' om deze te verwijderen.
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
  exiv2
0 pakketten opgewaardeerd, 1 nieuwe pakketten geïnstalleerd, 0
verwijderen en 0 niet opgewaardeerd.
Er moeten 75,6kB aan archieven opgehaald worden.
Na het uitpakken zal er 225kB extra schijfruimte gebruikt worden.
Ophalen:1 http://archive.ubuntu.com feisty/universe exiv2 0.12-0ubuntu2
[75,6kB]
75,6kB opgehaald in 0s (276kB/s)
Selecteren van voorheen niet geselecteerd pakket exiv2.
(Database inlezen ... 128139 bestanden en mappen geïnstalleerd.)
Uitpakken van exiv2 (uit .../exiv2_0.12-0ubuntu2_i386.deb) ...
Instellen van exiv2 (0.12-0ubuntu2) ...

======================================================


wolf@WolfZorrito:/media/photofat32/0319$exiv2 read *





Exiv2 exception in print action for file _dsc0104.ppm:
_dsc0104.ppm: The file contains data of an unknown image type
_dsc0105.nef         Filename        : _dsc0105.nef
_dsc0105.nef         Filesize        : 5434675 Bytes
_dsc0105.nef         Camera make     : NIKON CORPORATION
_dsc0105.nef         Camera model    : NIKON D50
_dsc0105.nef         Image timestamp : 2007:10:13 16:43:28
_dsc0105.nef         Image number    : 
_dsc0105.nef         Exposure time   : 1/640 s
_dsc0105.nef         Aperture        : F4
_dsc0105.nef         Exposure bias   : -2/3
_dsc0105.nef         Flash           : No flash
_dsc0105.nef         Flash bias      : 
_dsc0105.nef         Focal length    : 105.0 mm (35 mm equivalent: 157.0
mm)
_dsc0105.nef         Subject distance: 
_dsc0105.nef         ISO speed       : 400
_dsc0105.nef         Exposure mode   : Aperture priority
_dsc0105.nef         Metering mode   : Multi-segment
_dsc0105.nef         Macro mode      : 
_dsc0105.nef         Image quality   : RAW    
_dsc0105.nef         Exif Resolution : 3040 x 2014
_dsc0105.nef         White balance   : AUTO        
_dsc0105.nef         Thumbnail       : None
_dsc0105.nef         Copyright       : 
_dsc0105.nef         Exif comment    : 


=================================================


removing *.ppm or *.db does not change anything.

===================================================

OK, what is next ?

Harry

Op zondag 14-10-2007 om 09:23 uur [tijdzone +0000], schreef Andreas
Huggel:
[bugs.kde.org quoted mail]

Removed the latest image directories, deleted the digikam.db in the
root.  reboot the machine. starting Digikam he correctly builds a new
dtatabase and having done so it fails signal 11:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1246857520 (LWP 5563)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb5b93df3 in memmove () from /lib/tls/i686/cmov/libc.so.6
#7  0xb74219ff in std::vector<unsigned char, std::allocator<unsigned
char> >::_M_assign_aux<unsigned char const*> ()
from /usr/lib/libexiv2-0.12.so
#8  0xb741e3f4 in Exiv2::DataValue::read ()
from /usr/lib/libexiv2-0.12.so
#9  0xb73e4c3c in Exiv2::IptcData::readData ()
from /usr/lib/libexiv2-0.12.so
#10 0xb73e4e68 in Exiv2::IptcData::load ()
from /usr/lib/libexiv2-0.12.so
#11 0xb741ae27 in Exiv2::TiffMetadataDecoder::decodeIrbIptc ()
   from /usr/lib/libexiv2-0.12.so
#12 0xb7416663 in Exiv2::TiffMetadataDecoder::decodeTiffEntry ()
   from /usr/lib/libexiv2-0.12.so
#13 0xb7416874 in Exiv2::TiffMetadataDecoder::visitEntry ()
   from /usr/lib/libexiv2-0.12.so
#14 0xb7412198 in Exiv2::TiffEntry::doAccept ()
from /usr/lib/libexiv2-0.12.so
#15 0xb7412170 in Exiv2::TiffComponent::accept ()
   from /usr/lib/libexiv2-0.12.so
#16 0xb74123c8 in Exiv2::TiffDirectory::doAccept ()
   from /usr/lib/libexiv2-0.12.so
#17 0xb7412170 in Exiv2::TiffComponent::accept ()
   from /usr/lib/libexiv2-0.12.so
#18 0xb74151c8 in Exiv2::TiffParser::decode ()
from /usr/lib/libexiv2-0.12.so
#19 0xb74147f8 in Exiv2::TiffImage::readMetadata ()
   from /usr/lib/libexiv2-0.12.so
#20 0xb74657cb in KExiv2Iface::KExiv2::load ()
from /usr/lib/libkexiv2.so.0
#21 0xb7ee285c in Digikam::DMetadata::load ()
from /usr/lib/libdigikam.so.0
#22 0xb7ee28cc in Digikam::DMetadata::DMetadata ()
   from /usr/lib/libdigikam.so.0
#23 0xb7d2ee88 in Digikam::ScanLib::storeItemInDatabase ()
   from /usr/lib/libdigikam.so.0
#24 0xb7d41978 in Digikam::ScanLib::allFiles ()
from /usr/lib/libdigikam.so.0
#25 0xb7d41926 in Digikam::ScanLib::allFiles ()
from /usr/lib/libdigikam.so.0
#26 0xb7d421b9 in Digikam::ScanLib::findMissingItems ()
   from /usr/lib/libdigikam.so.0
#27 0xb7d4244f in Digikam::ScanLib::startScan ()
from /usr/lib/libdigikam.so.0
#28 0xb7d5d337 in Digikam::AlbumManager::setLibraryPath ()
   from /usr/lib/libdigikam.so.0
#29 0x0804ab79 in main ()


Next step ?

Is there only only image, _dsc0105.nef? If so, can you send it to me? ahuggel at gmx dot net. Then you'll need to upgrade libkexiv2 and libexiv2 to the latest versions as Gilles said too see if the problem persists.
-ahu.

Op zondag 14-10-2007 om 11:38 uur [tijdzone +0000], schreef Andreas
Huggel:
[bugs.kde.org quoted mail]

1- no,  there are in total 105 images, I just enclosed the 105 exif data
as an example and to show it runs the complete set.

2- I have upgraded libexiv2 already as indicated in a previous report,
upgrading libexiv2 via the ubuntu site tells me  I have already
installed a newer version.

3- I just installed the latest libkexiv2 using the ubuntu site.

4- problem persists

5- Strange thing is that I did run digikam and all image files, prior to
the crash, with great succes

Please submit instructions. Appreciate the help :-)
Harry

When you have upgraded Exiv2, are you take a care to uninstall old one ? I remember few problem when both version are installed in the same time, especially with Exiv2 < 0.15...

Gilles

Op zondag 14-10-2007 om 12:30 uur [tijdzone +0000], schreef Gilles
Caulier:
[bugs.kde.org quoted mail]

I just removed Exiv2 and re-installed it, using Synaptic.
Problem remains.

Harry

Harry, 
I am also an ubuntu user and may be able to help.  
Are you using the "feisty 7.04" version, if not which?
Where did you get the exiv2_0.15-1ubuntu2_i386.deb?  I don't think this is part of the standard ubuntu distribution?
Are you planning on upgrading to the "gutsy 7.10" release soon? It comes out later this week and may fix your problems.

I think what the others are suggesting you try, is to compile the newest version from the digikam website...

To do this you would need to first remove the existing digikam and related libraries using synaptic.  These would be digikam, exiv2, kipi-plugins (and maybe others - I can't try this right now).

Then install each of the source libraries and source code for digikam.  This will likely take a few steps/trials and a couple hours if it is your first time doing this. Let me know if you need more info on this. 

Geoff

Op maandag 15-10-2007 om 14:58 uur [tijdzone +0000], schreef Geoff King:
[bugs.kde.org quoted mail]

Geoff, 
Thanks for the reply.

1- I use the dapper version 6. At my bootscreen I see 2.6.20-16

2- The exiv2 I got via the official Ubuntu site. ( synaptic )
3- Since I have dapper 6, will I automatically be upgraded to gutsy 7 ?
4- I have a Ubuntu verion without compile utilities.
5- I reinstalled digikam and its plugins 
6- I feel the problem is not in digikam, I suspect that auto updates
received for dapper somehow screwed thing up. Cannot proof this.
7- So personally I opt for upgrade to gutsy 7, can you confirm that come
automatic since I am a 6 user ?

Harry

I'm guessing something is messed up with your install of ubuntu. The kernel version (2.6.20) suggests that you are using Feisty. Although Dapper is still supported for security updates, it's getting old and you would probably need to manually compile and install the source code versions of digikam and the required libs instead of using the packaged versions from synaptic. 
To your individual points..
1-This is not your normal "dapper" kernel, instead it looks like you have "feisty" installed (2.6.20 suggests)
2-okay
3-If you are truly on Dapper, you cannot upgrade to gutsy without first upgrading through the other versions (edgy then feisty). If you are on Feisty , then you can upgrade to gutsy by following the procedure on the ubuntu website. See http://www.ubuntu.com/testing/710rc. It might be best to wait a few days for the official version to come out.  However, you may have the best luck backing up all your data and doing a complete fresh install of gutsy from CD (this is what I would do). Or do the backup, try the upgrade and if it still has problems, do a fresh install.
4-All versions have the utilities needed, you just need to install them via synaptic and figure out how to use them.  There are lots of good examples to get you started such as http://www.digikam.org/?q=download/svn
5-What version is it?
6-You may be correct-something does appear strange in your setup.
7-See #3 above.  Upgrades to new "distribution" versions are not automatic, you have to follow the upgrade procedure or do a fresh install.

Gutsy would give you digikam version 0.9.2.
Feel free to email me directly if questions are about Ubuntu updates and not digikam.

Good Luck, Geoff

Op maandag 15-10-2007 om 18:16 uur [tijdzone +0000], schreef Geoff King:
[bugs.kde.org quoted mail]



Geoff e.a., 


I just installed Ubuntu 7.04 on a separate partition. 
Guess I will automatically be upgraded to 7.10

So now I can use Ubuntu 6.x  as well as 7.04 


And I installed digikam. When I now use Ubuntu 7.04 and attach the same
drive E as I did on Ubuntu 6 it also crashes.

Then I have cleaned drive E rigorously, everything on it, every file and
only left one directory with images present.

Now digikam runs smooth on Ubuntu 6.x  and Ubuntu 7.04

Conlusion, digikam crashed on one of the files on that drive e (a vfat
drive so I can interchange with DOS) either being a .tmp or db or volume
informatio or so.


Problem solved for me.

Thanks all for the help, if i find out what file was the guilty one, I
will let know.

Harry

Op maandag 15-10-2007 om 18:16 uur [tijdzone +0000], schreef Geoff King:
[bugs.kde.org quoted mail]



Geoff, 

I just got a message on my Ubuntu 6.x that an upgrade to 7.10 is
available. I just tried to re-run it and it will take an hour or so.
Will do that later.
So upgrade 6->7.10 it is 'automatic'.

Harry

#14: "Problem solved for me." ==> closing this bug, marking it as WORKSFORME.

Agree, works for me.

Created attachment 30804 [details]
Copy of the report...

Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4