Bug 209142 - no many space disk ?
Summary: no many space disk ?
Status: RESOLVED DUPLICATE of bug 190535
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-10-01 23:11 UTC by Julien MÊME
Modified: 2009-10-12 00:15 UTC (History)
2 users (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 Julien MÊME 2009-10-01 23:11:26 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic i686
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 0 (LWP 25072)]

Thread 2 (Thread 0xb401ab90 (LWP 26060)):
#0  0xb8004430 in __kernel_vsyscall ()
#1  0xb6143412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb64e9344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xae77fae3 in ?? () from /usr/lib/libxine.so.1

Thread 1 (Thread 0xb5cbb700 (LWP 25072)):
[KCrash Handler]
#6  0xb7e70e08 in KDirModelNode::rowNumber (this=0x0) at /build/buildd/kde4libs-4.3.1/kio/kio/kdirmodel.cpp:120
#7  0xb7e70eb0 in KDirModelPrivate::indexForNode (this=0x8cedb18, node=0x0, rowNumber=-1) at /build/buildd/kde4libs-4.3.1/kio/kio/kdirmodel.cpp:284
#8  0xb7e7598e in KDirModelPrivate::_k_slotNewItems (this=0x8cedb18, directoryUrl=@0x8ce4028, items=@0x8ce4030) at /build/buildd/kde4libs-4.3.1/kio/kio/kdirmodel.cpp:377
#9  0xb7e76d2c in KDirModel::qt_metacall (this=0x95fc398, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe21398) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/kdirmodel.moc:82
#10 0xb67d71b8 in QMetaObject::activate (sender=0x99dac10, from_signal_index=14, to_signal_index=14, argv=0xbfe21398) at kernel/qobject.cpp:3113
#11 0xb67d7e42 in QMetaObject::activate (sender=0x99dac10, m=0x80b7410, local_signal_index=10, argv=0xbfe21398) at kernel/qobject.cpp:3187
#12 0xb7e597b9 in KDirLister::itemsAdded (this=0x99dac10, _t1=@0x8ce4028, _t2=@0x8ce4030) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/kdirlister.moc:268
#13 0xb7e5a6d6 in KDirLister::Private::emitItems (this=0x8d947b0) at /build/buildd/kde4libs-4.3.1/kio/kio/kdirlister.cpp:2303
#14 0xb7e5d224 in KDirListerCache::processPendingUpdates (this=0x8a84680) at /build/buildd/kde4libs-4.3.1/kio/kio/kdirlister.cpp:1796
#15 0xb7e6c28d in KDirListerCache::slotFilesChanged (this=0x8a84680, fileList=@0x9a40a68) at /build/buildd/kde4libs-4.3.1/kio/kio/kdirlister.cpp:850
#16 0xb7e6ce42 in KDirListerCache::qt_metacall (this=0x8a84680, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe2161c) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/kdirlister_p.moc:93
#17 0xb67d71b8 in QMetaObject::activate (sender=0x8a8e3b8, from_signal_index=8, to_signal_index=8, argv=0xbfe2161c) at kernel/qobject.cpp:3113
#18 0xb67d7e42 in QMetaObject::activate (sender=0x8a8e3b8, m=0xb7fe5274, local_signal_index=3, argv=0xbfe2161c) at kernel/qobject.cpp:3187
#19 0xb7e788e3 in OrgKdeKDirNotifyInterface::FilesChanged (this=0x8a8e3b8, _t1=@0x9a40a68) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/kdirnotify.moc:118
#20 0xb7e78aaa in OrgKdeKDirNotifyInterface::qt_metacall (this=0x8a8e3b8, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfe217b8)
    at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/kdirnotify.moc:82
#21 0xb727ee5a in QDBusConnectionPrivate::deliverCall (this=0x890a610, object=0x8a8e3b8, msg=@0x8cef484, metaTypes=@0x8cef488, slotIdx=8) at qdbusintegrator.cpp:891
#22 0xb7286eb7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8cef458, object=0x8a8e3b8) at qdbusintegrator_p.h:101
#23 0xb67d23b0 in QObject::event (this=0x8a8e3b8, e=0x8cef458) at kernel/qobject.cpp:1111
#24 0xb69d8d3c in QApplicationPrivate::notify_helper (this=0x8911c28, receiver=0x8a8e3b8, e=0x8cef458) at kernel/qapplication.cpp:4056
#25 0xb69e103e in QApplication::notify (this=0xbfe21ed4, receiver=0x8a8e3b8, e=0x8cef458) at kernel/qapplication.cpp:3603
#26 0xb771f85d in KApplication::notify (this=0xbfe21ed4, receiver=0x8a8e3b8, event=0x8cef458) at /build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302
#27 0xb67c1bcb in QCoreApplication::notifyInternal (this=0xbfe21ed4, receiver=0x8a8e3b8, event=0x8cef458) at kernel/qcoreapplication.cpp:610
#28 0xb67c2825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x88f3b38) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#29 0xb67c2a1d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#30 0xb67ed6af in postEventSourceDispatch (s=0x8913f18) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#31 0xb5f3db88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb5f410eb in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb5f41268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb67ed2f8 in QEventDispatcherGlib::processEvents (this=0x88f3d10, flags={i = -1075700296}) at kernel/qeventdispatcher_glib.cpp:327
#35 0xb6a7aa75 in QGuiEventDispatcherGlib::processEvents (this=0x88f3d10, flags={i = -1075700248}) at kernel/qguieventdispatcher_glib.cpp:202
#36 0xb67c01fa in QEventLoop::processEvents (this=0xbfe21e60, flags={i = -1075700184}) at kernel/qeventloop.cpp:149
#37 0xb67c0642 in QEventLoop::exec (this=0xbfe21e60, flags={i = -1075700120}) at kernel/qeventloop.cpp:201
#38 0xb67c2ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0xb69d8bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#40 0x0807aaff in _start ()

Reported using DrKonqi
Comment 1 FiNeX 2009-10-01 23:23:29 UTC
Please, would you like to explain how you did make dolphin crash?

Many thanks.
Comment 2 Dario Andres 2009-10-02 01:02:14 UTC
This is bug 190535, but useful steps are needed.
Thanks
Comment 3 Dario Andres 2009-10-12 00:15:08 UTC

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