Bug 606549

Summary: [abrt] crash in kdebase-runtime-4.4.4-1.fc13: OJPEGReadBufferFill: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Daniel Scott <dan>
Component: libtiffAssignee: Tom Lane <tgl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: fedora, hhorak, jreznik, kevin, ltinkl, rdieter, smparrish, tgl, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:d6fd85a6285e13c98f92e3677290a1b71480ab68
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-22 16:09:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Daniel Scott 2010-06-21 22:47:02 UTC 
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)
Comment 1 Daniel Scott 2010-06-21 22:47:05 UTC 
Created attachment 425770 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-22 00:17:09 UTC 
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
Comment 3 Daniel Scott 2010-06-22 00:36:48 UTC 
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
Comment 4 Rex Dieter 2010-06-22 14:51:11 UTC 
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.
Comment 5 Rex Dieter 2010-06-22 14:59:02 UTC 
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
Comment 6 Rex Dieter 2010-06-22 15:11:18 UTC 
per comment #5 , reassigning to libtiff
Comment 7 Daniel Scott 2010-06-22 15:35:43 UTC 
This could well be related to another problem that I have reported:

https://bugzilla.redhat.com/show_bug.cgi?id=600303
Comment 8 Tom Lane 2010-06-22 16:09:45 UTC 
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 ***