Created attachment 50928 [details]
crash.jpg

crash.jpg

The problem is more likely a bug in libexif then just having "the wrong  
version".  
  
worksforme on final 10.0. 

I have an i586 system. 
 
Regarding exif: a search in YaST shows only: 
koffice-database 
libexif  
libexif-gtk 
php4-exif 
picfolio 
 
and 
rpm -ql libexif | grep bin 
returns nothing. 

install the "exif" RPM if you need the commandline exif viewer. 

Ok, indeed there is an exif package in  
opensuse/distribution/SL-OSS-current/inst-source/suse/i586, just that it was  
not on the beta4 CD's.  
  
But, even if I used the libexif from the above location, it still crashes.   
rpm -qi libexif  
Name        : libexif                      Relocations: (not relocatable)  
Version     : 0.6.13                            Vendor: SUSE LINUX Products  
GmbH, Nuernberg, Germany  
Release     : 5                             Build Date: Sat 03 Sep 2005  
02:04:07 PM EEST  
Install date: Tue 27 Sep 2005 02:59:29 PM EEST      Build Host: f225.suse.de  
Group       : Development/Libraries/C and C++   Source RPM:  
libexif-0.6.13-5.src.rpm  
Size        : 3535516                          License: LGPL  
Signature   : DSA/SHA1, Sat 03 Sep 2005 02:13:43 PM EEST, Key ID  
a84edae89c800aca  
Packager    : http://www.suse.de/feedback  
URL         : http://libexif.sourceforge.net  
Summary     : An EXIF tag parsing library for digital cameras  
Description :  
This library is used to parse EXIF information from JPEGs created by  
digital cameras.  
  
Is the one in "final" newer/different?  
 
Updated backtrace with debug info for libexif is below: 
Using host libthread_db library "/lib/tls/libthread_db.so.1". 
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. 
[Thread debugging using libthread_db enabled] 
[New Thread 1102041632 (LWP 8956)] 
[KCrash handler] 
#3  0x41a44571 in strlen () from /lib/tls/libc.so.6 
#4  0x418a0e73 in exif_entry_get_value (e=0x8191870,  
    val=0xbf8b90d4 "[None] (Photographer)", maxlen=<value optimized out>) 
    at exif-entry.c:685 
#5  0x408fb4b8 in KExifEntry::readEntry (this=0x816cbf0) 
    
at /data/development/sources/kde-3.5/extragear/libs/libkexif/kexifentry.cpp:104 
#6  0x408fb559 in KExifEntry::setEntry (this=0x816cbf0, exifEntry=0x8191870) 
    
at /data/development/sources/kde-3.5/extragear/libs/libkexif/kexifentry.cpp:92 
#7  0x408fb70b in KExifEntry (this=0x816cbf0, exifEntry=0x8191870) 
    
at /data/development/sources/kde-3.5/extragear/libs/libkexif/kexifentry.cpp:54 
#8  0x408fe5d0 in KExifIfd::setContent (this=0x8161a10, content=0x8196b18) 
    
at /data/development/sources/kde-3.5/extragear/libs/libkexif/kexififd.cpp:95 
#9  0x408fe7d0 in KExifIfd (this=0x8161a10, name=@0xbf8b959c,  
    content=0x8196b18) 
    
at /data/development/sources/kde-3.5/extragear/libs/libkexif/kexififd.cpp:45 
#10 0x408fc0ec in KExifData::readFromData (this=0xbf8b9858,  
    data=0x81c3870 "Exif", size=21672) 
    
at /data/development/sources/kde-3.5/extragear/libs/libkexif/kexifdata.cpp:146 
#11 0x40177353 in Digikam::readJPEGMetaData () 
   from /data/kde-35/lib/libdigikam.so.0 
#12 0x400da48c in ScanLib::storeItemInDatabase () 
   from /data/kde-35/lib/libdigikam.so.0 
#13 0x400dbe6f in ScanLib::allFiles () from /data/kde-35/lib/libdigikam.so.0 
#14 0x400dc265 in ScanLib::findMissingItems () 
   from /data/kde-35/lib/libdigikam.so.0 
#15 0x400dce5f in ScanLib::startScan () from /data/kde-35/lib/libdigikam.so.0 
#16 0x4007487e in AlbumManager::setLibraryPath () 
   from /data/kde-35/lib/libdigikam.so.0 
#17 0x08049fa8 in main () 
 

can confirm with commandline client. (but not with digikam). 
 
will check 

Yeah, it crashes the command line client as well, I just did not notice the  
segmentation fault before...  
  
You must have digikam 0.8.0 (or the SVN version) as I understood.  

I opened this bug in the libexif tracker: 
 
http://sourceforge.net/tracker/index.php?func=detail&aid=1306193&group_id=12272&atid=112272 
 
and i have actually just fixed it there. 

Created attachment 51298 [details]
exif.pat

the patch i used.

AJ, can we fix this for 10.0? 
 
It can be used to crash applications using libexif to show info 

Approved, Maintenance-Tracker-2667

Packages fail in 10.0, please submit working packages...

released