Bug 226018 - dolphin crash when i tip F5 after zip of a folder
Summary: dolphin crash when i tip F5 after zip of a folder
Status: RESOLVED DUPLICATE of bug 208921
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: 2010-02-09 12:05 UTC by althor
Modified: 2010-02-10 13:11 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 althor 2010-02-09 12:05:52 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.27.41-170.2.117.fc10.i686 i686
Distribution: "Fedora release 10 (Cambridge)"

What I was doing when the application crashed:
dolphin crash when i tip F5 after zip of a folder

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77da770 (LWP 3225))]

Thread 2 (Thread 0xb5e47b90 (LWP 5093)):
#0  0x00157416 in __kernel_vsyscall ()
#1  0x00947432 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S:179
#2  0x0102ec11 in ?? () from /usr/lib/libxine.so.1
#3  0x0094351f in start_thread (arg=0xb5e47b90) at pthread_create.c:297
#4  0x0087904e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb77da770 (LWP 3225)):
[KCrash Handler]
#6  _dbus_connection_lock (connection=0xcccccccd) at dbus-connection.c:355
#7  0x00da8e35 in _dbus_pending_call_get_connection_and_lock (pending=0x9895070) at dbus-pending-call.c:309
#8  0x00d9b085 in reply_handler_timeout (data=0x9895070) at dbus-connection.c:3116
#9  0x00dae0e2 in dbus_timeout_handle (timeout=0xa0ff9f0) at dbus-timeout.c:473
#10 0x00a17fa7 in q_dbus_timeout_handle () at ./qdbus_symbols_p.h:172
#11 QDBusConnectionPrivate::timerEvent (this=0x94bc8a8, e=0xbfc1062c) at qdbusintegrator.cpp:1023
#12 0x02c0370f in QObject::event (this=0x94bc8a8, e=0xbfc1062c) at kernel/qobject.cpp:1074
#13 0x02f2a9ec in QApplicationPrivate::notify_helper (this=0x94d0b10, receiver=0x94bc8a8, e=0xbfc1062c) at kernel/qapplication.cpp:4065
#14 0x02f32cfe in QApplication::notify (this=0xbfc108c4, receiver=0x94bc8a8, e=0xbfc1062c) at kernel/qapplication.cpp:3605
#15 0x07766fad in KApplication::notify (this=0xbfc108c4, receiver=0x94bc8a8, event=0xbfc1062c) at /usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#16 0x02bf301b in QCoreApplication::notifyInternal (this=0xbfc108c4, receiver=0x94bc8a8, event=0xbfc1062c) at kernel/qcoreapplication.cpp:610
#17 0x02c22351 in QCoreApplication::sendEvent () at kernel/qcoreapplication.h:213
#18 QTimerInfoList::activateTimers (this=0x94cd924) at kernel/qeventdispatcher_unix.cpp:580
#19 0x02c1e950 in timerSourceDispatch (source=0x94cd8f0) at kernel/qeventdispatcher_glib.cpp:165
#20 0x02a04258 in g_main_dispatch () at gmain.c:2144
#21 IA__g_main_context_dispatch (context=0x94cd090) at gmain.c:2697
#22 0x02a07903 in g_main_context_iterate (context=0x94cd090, block=1, dispatch=1, self=0x94d39a8) at gmain.c:2778
#23 0x02a07ac1 in IA__g_main_context_iteration (context=0x94cd090, may_block=1) at gmain.c:2841
#24 0x02c1e8a8 in QEventDispatcherGlib::processEvents (this=0x94a6840, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327
#25 0x02fcacf5 in QGuiEventDispatcherGlib::processEvents (this=0x94a6840, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x02bf164a in QEventLoop::processEvents (this=0xbfc10850, flags={i = 36}) at kernel/qeventloop.cpp:149
#27 0x02bf1a92 in QEventLoop::exec (this=0xbfc10850, flags={i = 0}) at kernel/qeventloop.cpp:201
#28 0x02bf3f39 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x02f2a867 in QApplication::exec () at kernel/qapplication.cpp:3525
#30 0x0807862f in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-10 13:11:10 UTC
Most of those crashes are caused by the Nepomuk integration, and should be
fixed on KDE SC 4.4: bug 208921
As a workaround you can disable Nepomuk on
SystemSettings/Advanced/DesktopSearching
Regards

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