Bug 203604 - Trying to browse FUSE-mounted directory, Dolphin crashed
Summary: Trying to browse FUSE-mounted directory, Dolphin crashed
Status: RESOLVED DUPLICATE of bug 199219
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-12 20:12 UTC by Dotan Cohen
Modified: 2009-08-12 20:27 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 Dotan Cohen 2009-08-12 20:12:01 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-14-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I tryed to browse a FUSE-mounted directory, and Dolphin crashed on me. I do not know if the directory was successfully mounted or not. It was an Amazon S3 directory, and I performed the connection in the CLI window (F4) in Dolphin.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0xb6f253fa in QAbstractScrollArea::viewport (this=0x987ed98) at widgets/qabstractscrollarea.cpp:537
#7  0x08084c38 in KTreeView::KTreeViewPrivate::qt_metacall (this=0x987ed98, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfdc8e58)
    at /build/buildd/kdebase-4.3.0/obj-i486-linux-gnu/apps/dolphin/src/ktreeview_p.moc:69
#8  0xb687c1b8 in QMetaObject::activate (sender=0x98de368, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#9  0xb687ce42 in QMetaObject::activate (sender=0x98de368, m=0xb6959904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#10 0xb68b8687 in QTimer::timeout (this=0x98de368) at .moc/release-shared/moc_qtimer.cpp:128
#11 0xb68825ce in QTimer::timerEvent (this=0x98de368, e=0xbfdc92dc) at kernel/qtimer.cpp:261
#12 0xb687716f in QObject::event (this=0x98de368, e=0xbfdc92dc) at kernel/qobject.cpp:1075
#13 0xb6a7dd3c in QApplicationPrivate::notify_helper (this=0x8a46b70, receiver=0x98de368, e=0xbfdc92dc) at kernel/qapplication.cpp:4056
#14 0xb6a8603e in QApplication::notify (this=0xbfdc9574, receiver=0x98de368, e=0xbfdc92dc) at kernel/qapplication.cpp:3603
#15 0xb77c25cd in KApplication::notify (this=0xbfdc9574, receiver=0x98de368, event=0xbfdc92dc) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#16 0xb6866bcb in QCoreApplication::notifyInternal (this=0xbfdc9574, receiver=0x98de368, event=0xbfdc92dc) at kernel/qcoreapplication.cpp:610
#17 0xb6895d51 in QTimerInfoList::activateTimers (this=0x8a4ccf4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0xb68923a0 in timerSourceDispatch (source=0x8a4ccc0) at kernel/qeventdispatcher_glib.cpp:165
#19 0xb5fe3b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb5fe70eb in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb5fe7268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb68922f8 in QEventDispatcherGlib::processEvents (this=0x8a479e0, flags={i = -1076063144}) at kernel/qeventdispatcher_glib.cpp:327
#23 0xb6b1fa75 in QGuiEventDispatcherGlib::processEvents (this=0x8a479e0, flags={i = -1076063096}) at kernel/qguieventdispatcher_glib.cpp:202
#24 0xb68651fa in QEventLoop::processEvents (this=0xbfdc9500, flags={i = -1076063032}) at kernel/qeventloop.cpp:149
#25 0xb6865642 in QEventLoop::exec (this=0xbfdc9500, flags={i = -1076062968}) at kernel/qeventloop.cpp:201
#26 0xb6867ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0xb6a7dbb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#28 0x0807aa4f in main (argc=5, argv=0xbfdc9724) at /build/buildd/kdebase-4.3.0/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Dario Andres 2009-08-12 20:27:16 UTC
Merging with bug 199219. Thanks

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