Bug 233168 - Dolphin closed out of the blue
Summary: Dolphin closed out of the blue
Status: RESOLVED DUPLICATE of bug 226725
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-03 14:19 UTC by dragos64
Modified: 2010-05-12 14:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dragos64 2010-04-03 14:19:07 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.32.9-70.fc12.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
This time it just closed, a few seconds after I opened a new tab.

Otherwise Dolphin got stuck several time. I had to reboot or logout to start working again.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#5  _dbus_connection_lock (connection=0x6f007200670065) at dbus-connection.c:355
#6  0x0000003653c1d25d in _dbus_pending_call_get_connection_and_lock (pending=0x24ffbb0) at dbus-pending-call.c:307
#7  0x0000003653c0f40e in reply_handler_timeout (data=0x24ffbb0) at dbus-connection.c:3156
#8  0x0000003507e18997 in q_dbus_timeout_handle (this=0x1e5b020, e=0x7fff5ceb5c50) at qdbus_symbols_p.h:172
#9  QDBusConnectionPrivate::timerEvent (this=0x1e5b020, e=0x7fff5ceb5c50) at qdbusintegrator.cpp:1035
#10 0x000000350756663e in QObject::event (this=0x1e5b020, e=0x7fff5ceb5c50) at kernel/qobject.cpp:1212
#11 0x00000035099aa9dc in QApplicationPrivate::notify_helper (this=0x1e681f0, receiver=0x1e5b020, e=0x7fff5ceb5c50) at kernel/qapplication.cpp:4300
#12 0x00000035099b0aab in QApplication::notify (this=<value optimized out>, receiver=0x1e5b020, e=0x7fff5ceb5c50) at kernel/qapplication.cpp:4183
#13 0x00000038ec606846 in KApplication::notify (this=0x7fff5ceb5fa0, receiver=0x1e5b020, event=0x7fff5ceb5c50) at /usr/src/debug/kdelibs-4.4.1/kdeui/kernel/kapplication.cpp:302
#14 0x000000350755774c in QCoreApplication::notifyInternal (this=0x7fff5ceb5fa0, receiver=0x1e5b020, event=0x7fff5ceb5c50) at kernel/qcoreapplication.cpp:704
#15 0x000000350757fe02 in sendEvent (this=0x1e74720) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x1e74720) at kernel/qeventdispatcher_unix.cpp:603
#17 0x000000350757d374 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 0x000000350583923e in g_main_dispatch (context=0x1e73520) at gmain.c:1960
#19 IA__g_main_context_dispatch (context=0x1e73520) at gmain.c:2513
#20 0x000000350583cc28 in g_main_context_iterate (context=0x1e73520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#21 0x000000350583cd4a in IA__g_main_context_iteration (context=0x1e73520, may_block=1) at gmain.c:2654
#22 0x000000350757d063 in QEventDispatcherGlib::processEvents (this=0x1e41c60, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#23 0x0000003509a49a4e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x0000003507556192 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x000000350755645c in QEventLoop::exec (this=0x7fff5ceb5ef0, flags=...) at kernel/qeventloop.cpp:201
#26 0x0000003507558749 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#27 0x0000000000437585 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-4.4.1/apps/dolphin/src/main.cpp:101

Possible duplicates by query: bug 232669, bug 230650, bug 229551, bug 229144, bug 227115.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-05-12 14:52:09 UTC
Thanks for the bug report! This seems to be a duplicate of a bug in D-Bus.

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