abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice component: kdebase-runtime crash_function: OJPEGReadBufferFill executable: /usr/bin/nepomukservicestub global_uuid: d6fd85a6285e13c98f92e3677290a1b71480ab68 kernel: 2.6.33.5-124.fc13.x86_64 package: kdebase-runtime-4.4.4-1.fc13 rating: 4 reason: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
Created attachment 425770 [details] File: backtrace
KDE Version 4.4.4 is now available. Please update to the this latest release and retest the application. Please advise if you are still having the same issue as documented. Any reports not updated within 30 days will be closed. Thanks from the Fedora KDE Team
Hi, I am already running KDE 4.4.4 dan@dscott:~$ rpm -qa|grep kdebase-runtime kdebase-runtime-libs-4.4.4-1.fc13.x86_64 kdebase-runtime-4.4.4-1.fc13.x86_64 dan@dscott:~$ Thanks, Dan
I would venture there's a possibility of a corrupted or truncated jpeg file in your $HOME somewhere, that nepomuk is hitting here. I'll try to come up with a script to help find it, so we can reproduce this, and send upstream.
I take it back, the backtrace comes from a function in libtiff, Core was generated by `/usr/bin/nepomukservicestub nepomukstrigiservice'. Program terminated with signal 11, Segmentation fault. #0 0x00000035a0028fd4 in OJPEGReadBufferFill (sp=0x7f398485b460) at tif_ojpeg.c:1912 1912 sp->in_buffer_file_pos=sp->tif->tif_dir.td_stripoffset[sp->in_buffer_next_strile]; find -name tif_ojpeg.c ./tiff-3.9.2/libtiff/tif_ojpeg.c
per comment #5 , reassigning to libtiff
This could well be related to another problem that I have reported: https://bugzilla.redhat.com/show_bug.cgi?id=600303
Yeah, I think this is a duplicate. The back trace is the same, and most likely all TIFFs from this particular camera manufacturer are going to provoke that same bug. *** This bug has been marked as a duplicate of bug 600303 ***