Bug 234537 - dolphin crash ( not sure: posible after when restarting x server .. )
Summary: dolphin crash ( not sure: posible after when restarting x server .. )
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-04-16 14:59 UTC by Suhan Andrei
Modified: 2010-04-17 05:28 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 Suhan Andrei 2010-04-16 14:59:47 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.x86_64 x86_64
Distribution: "Fedora release 10 (Cambridge)"

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  _dbus_connection_lock (connection=0x3e00000070) at dbus-connection.c:355
#6  0x000000302021cb7d in _dbus_pending_call_get_connection_and_lock (pending=0x7fbed4001010) at dbus-pending-call.c:309
#7  0x000000302020fc5f in reply_handler_timeout (data=0x3e00000070) at dbus-connection.c:3116
#8  0x0000003e3ee19896 in q_dbus_timeout_handle () at ./qdbus_symbols_p.h:172
#9  QDBusConnectionPrivate::timerEvent (this=0x13fe990, e=0x7fff10fcf610) at qdbusintegrator.cpp:1023
#10 0x0000003e3c353473 in QObject::event (this=0x13fe990, e=0x11) at kernel/qobject.cpp:1074
#11 0x00000032fd39001d in QApplicationPrivate::notify_helper (this=0x1409ef0, receiver=0x13fe990, e=0x7fff10fcf610) at kernel/qapplication.cpp:4065
#12 0x00000032fd39825a in QApplication::notify (this=0x7fff10fcf950, receiver=0x13fe990, e=0x7fff10fcf610) at kernel/qapplication.cpp:4030
#13 0x00000032fea1351b in KApplication::notify (this=0x7fff10fcf950, receiver=0x13fe990, event=0x7fff10fcf610) at /usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#14 0x0000003e3c34378c in QCoreApplication::notifyInternal (this=0x7fff10fcf950, receiver=0x13fe990, event=0x7fff10fcf610) at kernel/qcoreapplication.cpp:610
#15 0x0000003e3c370859 in QCoreApplication::sendEvent () at kernel/qcoreapplication.h:213
#16 QTimerInfoList::activateTimers (this=0x140d5b0) at kernel/qeventdispatcher_unix.cpp:580
#17 0x0000003e3c36cd5d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#18 0x00000035bb8377bb in g_main_dispatch () at gmain.c:2144
#19 IA__g_main_context_dispatch (context=0x140c920) at gmain.c:2697
#20 0x00000035bb83af8d in g_main_context_iterate (context=0x140c920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2778
#21 0x00000035bb83b14b in IA__g_main_context_iteration (context=0x140c920, may_block=1) at gmain.c:2841
#22 0x0000003e3c36ccbf in QEventDispatcherGlib::processEvents (this=0x13e4d50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#23 0x00000032fd42753f in QGuiEventDispatcherGlib::processEvents (this=0x3e00000070, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#24 0x0000003e3c342022 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#25 0x0000003e3c3423f4 in QEventLoop::exec (this=0x7fff10fcf8c0, flags=) at kernel/qeventloop.cpp:201
#26 0x0000003e3c3446c4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x00000000004372ad in main (argc=3, argv=0x7fff10fcfe38) at /usr/src/debug/kdebase-4.3.3/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Suhan Andrei 2010-04-16 23:01:37 UTC
On this machine I have all updates to day . I there is any more info you need form the machine please let me know and I post it. what I was doing is that I had killed the X and then after relogin it ocured this crash , still not sure if this was the cause. 
 
Thanks.
Comment 2 Jonathan Thomas 2010-04-17 05:28:22 UTC

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