Bug 210063 - dolphin crashes suddenly when opening a folder.
Summary: dolphin crashes suddenly when opening a folder.
Status: RESOLVED NOT A BUG
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-10 12:48 UTC by Pedro Martin
Modified: 2009-10-11 16:49 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 Pedro Martin 2009-10-10 12:48:28 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1) "release 169"
Qt Version: 4.5.2
Operating System: Linux 2.6.27.29-0.1-default x86_64
Distribution: "openSUSE 11.1 (x86_64)"

What I was doing when the application crashed:
dolphin crashed suddenly tryng to opening a standard folder, Documents or any other.
It happens aleatory, sometimes dolphin works as expected and sometimes crashes.
Opensuse 11.1 x86-64 is already clean installed in the computer.
KDE version 4.3.1 release 169

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f765e8d5ddc in QMutex::lock (this=0x1144d90) at thread/qmutex.cpp:152
#6  0x00007f765f8b27a9 in mutex_lock (mutex=0x1144d90) at qdbusthread.cpp:69
#7  0x00007f76593c7ebd in _dbus_connection_lock (connection=0x7f765dee1a60) at dbus-connection.c:355
#8  0x00007f76593d951d in _dbus_pending_call_get_connection_and_lock (pending=0x9a5fc0) at dbus-pending-call.c:309
#9  0x00007f76593cc54f in reply_handler_timeout (data=0x1144d90) at dbus-connection.c:3116
#10 0x00007f765f88a446 in QDBusConnectionPrivate::timerEvent (this=0x6a3290, e=0x7ffff0d3e650) at ./qdbus_symbols_p.h:172
#11 0x00007f765e9d4533 in QObject::event (this=0x6a3290, e=0x17) at kernel/qobject.cpp:1075
#12 0x00007f765ee58abd in QApplicationPrivate::notify_helper (this=0x6ae9d0, receiver=0x6a3290, e=0x7ffff0d3e650) at kernel/qapplication.cpp:4056
#13 0x00007f765ee60d4a in QApplication::notify (this=0x7ffff0d3ea40, receiver=0x6a3290, e=0x7ffff0d3e650) at kernel/qapplication.cpp:4021
#14 0x00007f76603baa8b in KApplication::notify (this=0x7ffff0d3ea40, receiver=0x6a3290, event=0x7ffff0d3e650) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#15 0x00007f765e9c494c in QCoreApplication::notifyInternal (this=0x7ffff0d3ea40, receiver=0x6a3290, event=0x7ffff0d3e650) at kernel/qcoreapplication.cpp:610
#16 0x00007f765e9f1b60 in QTimerInfoList::activateTimers (this=0x6b5430) at kernel/qcoreapplication.h:213
#17 0x00007f765e9edddd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#18 0x00007f765ad600fb in IA__g_main_context_dispatch (context=0x6b4920) at gmain.c:2144
#19 0x00007f765ad638cd in g_main_context_iterate (context=0x6b4920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2778
#20 0x00007f765ad63a8b in IA__g_main_context_iteration (context=0x6b4920, may_block=1) at gmain.c:2841
#21 0x00007f765e9edd3f in QEventDispatcherGlib::processEvents (this=0x689730, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007f765eeeffaf in QGuiEventDispatcherGlib::processEvents (this=0x1144d90, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f765e9c31d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -254547600}) at kernel/qeventloop.cpp:149
#24 0x00007f765e9c35a4 in QEventLoop::exec (this=0x7ffff0d3e9b0, flags={i = -254547520}) at kernel/qeventloop.cpp:201
#25 0x00007f765e9c5894 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x000000000043980d in _start ()

This bug may be a duplicate of or related to bug 209820

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-10 15:27:46 UTC
Merging with bug 208921. Thanks

*** This bug has been marked as a duplicate of bug 208921 ***
Comment 2 Pedro Martin 2009-10-11 16:34:38 UTC
I think it was produced by uncorrect nepomuk/strigi configuration in my machine.
I have an extra ext3 partition that wasn't included in nepomuk/strigi db.

Thanks for your excellent work.

Best regards
Pedro Martin
Comment 3 Dario Andres 2009-10-11 16:49:49 UTC
I'm glad it works now. Thanks