Bug 190792

Summary:	dolphin crash when asked to show properties of "/"
Product:	[Applications] dolphin	Reporter:	bmayesky
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	frank78ac
Priority:	NOR
Version First Reported In:	16.12.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description bmayesky 2009-04-27 04:50:18 UTC

Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

dolphin crash when asked to show properties of "/".
Nothing to add except that it's at the end of a day I'm using and configure my Kubuntu 9.04.

Application : Dolphin (dolphin), signal SIGABRT

Thread 1 (Thread 0xb5ba4700 (LWP 18212)):
[KCrash Handler]
#6  0xb7ef3430 in __kernel_vsyscall ()
#7  0xb63056d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6307098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb62fe5ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb6267b6d in Strigi::AnalysisResult::Private::Private () from /usr/lib/libstreamanalyzer.so.0
#11 0xb6267c9a in Strigi::AnalysisResult::AnalysisResult () from /usr/lib/libstreamanalyzer.so.0
#12 0xb7d8698e in ?? () from /usr/lib/libkio.so.5
#13 0xb7d88072 in KFileMetaInfo::KFileMetaInfo () from /usr/lib/libkio.so.5
#14 0xb7d77198 in KFileItem::metaInfo () from /usr/lib/libkio.so.5
#15 0xb7e42d3e in KFileMetaPropsPlugin::KFileMetaPropsPlugin () from /usr/lib/libkio.so.5
#16 0xb7e6b410 in KPropertiesDialog::KPropertiesDialogPrivate::insertPages () from /usr/lib/libkio.so.5
#17 0xb7e6b6e2 in KPropertiesDialog::KPropertiesDialogPrivate::init () from /usr/lib/libkio.so.5
#18 0xb7e6cca1 in KPropertiesDialog::KPropertiesDialog () from /usr/lib/libkio.so.5
#19 0x08077ebf in _start ()

Comment 1 Frank Reininghaus 2009-04-27 20:36:48 UTC

Thanks for the bug report! This issue is known already, it is a Strigi bug
which is fixed in trunk. I don't know though when a new Strigi version
containing the fix will be released.

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