Bug 201948

Summary: dolphin crashed after I highlighted a file
Product: [Applications] dolphin Reporter: Freeman <freemanthomason>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description Freeman 2009-07-30 00:04:16 UTC
Version:           1.2.1 (using KDE 4.2.2)
Installed from:    Ubuntu Packages

I opened dolphin to move a .jar file and every time I highlight the .jar file dolphin crashes, I have tried to highlighting and moving other files and there are no problems with the exception of individual file.

"A Fatal Error Occurred
The application Dolphin (dolphin) crashed and caused the signal 6 (SIGABRT).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc."

"Application: Dolphin (dolphin), signal SIGABRT

Thread 1 (Thread 0xb5cc0700 (LWP 4517)):
[KCrash Handler]
#6  0xb801d430 in __kernel_vsyscall ()
#7  0xb64216d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6423098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb641a5ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb6382c40 in Strigi::AnalysisResult::Private::Private () from /usr/lib/libstreamanalyzer.so.0
#11 0xb6382d23 in Strigi::AnalysisResult::AnalysisResult () from /usr/lib/libstreamanalyzer.so.0
#12 0xb63838c1 in Strigi::AnalysisResult::indexChild () from /usr/lib/libstreamanalyzer.so.0
#13 0xb63c16fe in ?? () from /usr/lib/libstreamanalyzer.so.0
#14 0xb63a910f in ?? () from /usr/lib/libstreamanalyzer.so.0
#15 0xb7ea1a07 in KFileMetaInfoPrivate::init (this=0x891cfb8, stream=@0xbfb3a0f8, url=@0xbfb3a0f0, mtime=1248078871) at /build/buildd/kde4libs-4.2.2/kio/kio/kfilemetainfo.cpp:201
#16 0xb7ea2c74 in KFileMetaInfo (this=0xbfb3a1b8, path=@0xbfb3a1bc) at /build/buildd/kde4libs-4.2.2/kio/kio/kfilemetainfo.cpp:228
#17 0x08083154 in _start ()"
Comment 1 Peter Penz 2009-07-30 00:27:37 UTC

*** This bug has been marked as a duplicate of bug 185551 ***