Bug 196063 - crash after moving cursor over a samba-shares workgroup icon
Summary: crash after moving cursor over a samba-shares workgroup icon
Status: RESOLVED DUPLICATE of bug 185551
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 18:28 UTC by Mario Bruckschwaiger
Modified: 2009-06-12 00:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Bruckschwaiger 2009-06-11 18:28:14 UTC
Version:           1.2.1 (using KDE 4.2.3)
OS:                Linux
Installed from:    Fedora RPMs

When opening dolphin, clicking on "Network" then clicking on "Samba Shares", the workgroup icons appear. As soon as the mouse pointer is moved on an icon, the background gets highlighted. But now, before the "tooltip"-text is displayed, dolphin crashes with the following details:

Application: Dolphin (dolphin), signal SIGABRT
0x00007ffccde78e30 in __nanosleep_nocancel () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7ffccef4f820 (LWP 3126))]

Thread 1 (Thread 0x7ffccef4f820 (LWP 3126)):
[KCrash Handler]
#5  0x00007ffccde082f5 in raise () from /lib64/libc.so.6
#6  0x00007ffccde09b20 in abort () from /lib64/libc.so.6
#7  0x00007ffccde012fa in __assert_fail () from /lib64/libc.so.6
#8  0x0000003c6721805c in Strigi::AnalysisResult::Private::Private(std::string const&, long, Strigi::IndexWriter&, Strigi::StreamAnalyzer&, std::string const&, Strigi::AnalysisResult&) ()
   from /usr/lib64/libstreamanalyzer.so.0
#9  0x0000003c672181ef in Strigi::AnalysisResult::AnalysisResult(std::string const&, long, Strigi::IndexWriter&, Strigi::StreamAnalyzer&, std::string const&) () from /usr/lib64/libstreamanalyzer.so.0
#10 0x0000003c669362c2 in ?? () from /usr/lib64/libkio.so.5
#11 0x0000003c669378d4 in KFileMetaInfo::KFileMetaInfo(KUrl const&) () from /usr/lib64/libkio.so.5
#12 0x0000003c66927670 in KFileItem::metaInfo(bool, int) const () from /usr/lib64/libkio.so.5
#13 0x0000003c6692a5b1 in KFileItem::getToolTipText(int) const () from /usr/lib64/libkio.so.5
#14 0x00007ffcce91bbcc in ?? () from /usr/lib64/libdolphinprivate.so.4
#15 0x00007ffcce91be74 in ?? () from /usr/lib64/libdolphinprivate.so.4
#16 0x0000003c63358612 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#17 0x0000003c63352353 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x0000003c64b8deac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x0000003c64b954de in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x0000003c65c06076 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x0000003c63342b7c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x0000003c6336e562 in ?? () from /usr/lib64/libQtCore.so.4
#23 0x0000003c6336c05d in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00007ffccb8e918e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x00007ffccb8ec8e8 in ?? () from /lib64/libglib-2.0.so.0
#26 0x00007ffccb8eca5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x0000003c6336bfa6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x0000003c64c220de in ?? () from /usr/lib64/libQtGui.so.4
#29 0x0000003c63341452 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x0000003c63341824 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x0000003c63343919 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x000000000043fb35 in _start ()
Comment 1 Dario Andres 2009-06-12 00:22:30 UTC
This is another form of bug 185551 (a Strigi bug already fixed in current versions). Thanks

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