Bug 197504

Summary: we cannot open properties description who is crashing in trash and root menu there is a SIGABRT BUGS
Product: [Applications] dolphin Reporter: azzdine djekmani <djekmani>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frank78ac
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description azzdine djekmani 2009-06-22 15:51:35 UTC
Version:           dolphin 1.2.1 (using KDE 4.2.2)
Compiler:          gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) 
OS:                Linux
Installed from:    Ubuntu Packages

 * no plugins loaded
 * backtraces :
Application: Dolphin (dolphin), signal SIGABRT

Thread 1 (Thread 0xb5d29700 (LWP 13312)):
[KCrash Handler]
#6  0xb8074430 in __kernel_vsyscall ()
#7  0xb648a6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb648c098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb64835ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb63ebb6d in Strigi::AnalysisResult::Private::Private () from /usr/lib/libstreamanalyzer.so.0
#11 0xb63ebc9a in Strigi::AnalysisResult::AnalysisResult () from /usr/lib/libstreamanalyzer.so.0
#12 0xb7f0a98e in ?? () from /usr/lib/libkio.so.5
#13 0xb7f0c072 in KFileMetaInfo::KFileMetaInfo () from /usr/lib/libkio.so.5
#14 0xb7efb198 in KFileItem::metaInfo () from /usr/lib/libkio.so.5
#15 0xb7fc6d3e in KFileMetaPropsPlugin::KFileMetaPropsPlugin () from /usr/lib/libkio.so.5
#16 0xb7fef410 in KPropertiesDialog::KPropertiesDialogPrivate::insertPages () from /usr/lib/libkio.so.5
#17 0xb7fef6e2 in KPropertiesDialog::KPropertiesDialogPrivate::init () from /usr/lib/libkio.so.5
#18 0xb7ff0ca1 in KPropertiesDialog::KPropertiesDialog () from /usr/lib/libkio.so.5
#19 0x08077ebf in _start ()
Comment 1 Frank Reininghaus 2009-06-22 18:52:18 UTC
Thanks for the bug report! This bug is known already, it's a Strigi issue which is fixed already in trunk (the current development version).

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