Bug 196439

Summary: dolphin crashes when is trying to enter a machine in a workgroup
Product: [Applications] dolphin Reporter: alirio <alricu89>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frank78ac
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description alirio 2009-06-14 05:17:36 UTC
Version:           1.2.1 (using KDE 4.2.4)
OS:                Linux
Installed from:    I Don't Know

when i m trying to enter in a computer in my local network with samba and using dolphin it always crash,
i can see the other machine but when i click on the computer icon dolphin crashes 

how to reproduce:
1. open dolphin
2. click on network icon
3. click on samba shares
4. choose the workgroup (in my case workgroup)
5. click on the icon of the other computer
6. it will crash(or at least it always happens to me )


this is the report bug


Application: Dolphin (dolphin), signal SIGABRT

Thread 1 (Thread 0xb5c39700 (LWP 8304)):
[KCrash Handler]
#6  0xb7f8a430 in __kernel_vsyscall ()
#7  0xb639a6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb639c098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb63935ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb62fcb6d in Strigi::AnalysisResult::Private::Private () from /usr/lib/libstreamanalyzer.so.0
#11 0xb62fcc9a in Strigi::AnalysisResult::AnalysisResult () from /usr/lib/libstreamanalyzer.so.0
#12 0xb7e1915e in ?? () from /usr/lib/libkio.so.5
#13 0xb7e1a842 in KFileMetaInfo::KFileMetaInfo () from /usr/lib/libkio.so.5
#14 0xb7e09932 in KFileItem::metaInfo () from /usr/lib/libkio.so.5
#15 0xb7e0ccc9 in KFileItem::getToolTipText () from /usr/lib/libkio.so.5
#16 0xb7be9be1 in ?? () from /usr/lib/libdolphinprivate.so.4
#17 0xb7be9ed3 in ?? () from /usr/lib/libdolphinprivate.so.4
#18 0xb6757ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb6758932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0xb6793717 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#21 0xb675d6fe in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#22 0xb675215f in QObject::event () from /usr/lib/libQtCore.so.4
#23 0xb6979e9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#24 0xb698219e in QApplication::notify () from /usr/lib/libQtGui.so.4
#25 0xb76d3e0d in KApplication::notify () from /usr/lib/libkdeui.so.5
#26 0xb6741a3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#27 0xb6770d71 in ?? () from /usr/lib/libQtCore.so.4
#28 0xb676d4e0 in ?? () from /usr/lib/libQtCore.so.4
#29 0xb5ebfb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb5ec30eb in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb5ec3268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb676d438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#33 0xb6a1b365 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb674006a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb67404aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0xb6742959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#37 0xb6979d17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#38 0x08085a5f in _start ()
Comment 1 Frank Reininghaus 2009-06-14 12:35:16 UTC
Thanks for the bug report! The backtrace looks like it's the same issue as bug 185551 (a Stigi bug which is fixed in trunk), I'll mark it as a duplicate.

To be 100% sure, you could run Dolphin from a Konsole and verify that the error output before the crash contains

Strigi::AnalysisResult::Private::Private(const std::string&, time_t,
Strigi::IndexWriter&, Strigi::StreamAnalyzer&, const std::string&,
Strigi::AnalysisResult&): Assertion `pos != m_path.size()-1' failed.

If this is *not* the case, please reopen this bug report. Thanks!

*** This bug has been marked as a duplicate of bug 185551 ***
Comment 2 Frank Reininghaus 2009-06-15 19:10:35 UTC
I'm not 100% sure I was right in comment 1 - today I realized that also other asserts can be hit in Strigi::AnalysisResult::Private::Private(), see bug 196576 for an example (which is also related to Samba). Sorry if I made a mistake here.

To be sure, it would really help if you could run Dolphin from a console and post the error message (especially the part containing "Assertion ... failed") here. Also your Strigi version might help, you can probably find it out using "strigidaemon --version".

Thanks.