Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-15-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I hade two tabs open, one remote (fish) and one local. The local one was highlighted. Then I dubbel clicked on the tab-bar for a new tab. An empty tab was created, instantly followed by Dolphin crashing. It happened trice in a row, the exact same way.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0x0336f4bc in QTabBarPrivate::_q_moveTabFinished (this=0x8affd08, index=2) at widgets/qtabbar.cpp:1847
#7  0x033713b7 in QTabBarPrivate::refresh (this=0x8affd08) at widgets/qtabbar.cpp:667
#8  0x03371711 in QTabBar::setTabText (this=0x8aa04f0, index=2, text=...) at widgets/qtabbar.cpp:961
#9  0x01166ab9 in KAcceleratorManagerPrivate::calculateAccelerators (item=0x909e1f0, used=...) at ../../kdeui/shortcuts/kacceleratormanager.cpp:229
#10 0x011690a0 in KAcceleratorManagerPrivate::manage (widget=0x89c61c0) at ../../kdeui/shortcuts/kacceleratormanager.cpp:192
#11 0x011692fe in KAcceleratorManager::manage (widget=0x89c61c0, programmers_mode=false) at ../../kdeui/shortcuts/kacceleratormanager.cpp:505
#12 0x0116accd in KCheckAccelerators::checkAccelerators (this=0x8a46b58, automatic=true) at ../../kdeui/shortcuts/kcheckaccelerators.cpp:243
#13 0x0116b13a in KCheckAccelerators::autoCheckSlot (this=0x8a46b58) at ../../kdeui/shortcuts/kcheckaccelerators.cpp:197
#14 0x0116b1f1 in KCheckAccelerators::qt_metacall (this=0x8a46b58, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfeb6f6c) at ./kcheckaccelerators.moc:68
#15 0x02644263 in QMetaObject::activate (sender=0x8a46b6c, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#16 0x02644ec2 in QMetaObject::activate (sender=0x8a46b6c, m=0x271f904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#17 0x0267e667 in QTimer::timeout (this=0x8a46b6c) at .moc/release-shared/moc_qtimer.cpp:128
#18 0x026499ae in QTimer::timerEvent (this=0x8a46b6c, e=0xbfeb7400) at kernel/qtimer.cpp:261
#19 0x0263e3bf in QObject::event (this=0x8a46b6c, e=0xbfeb7400) at kernel/qobject.cpp:1075
#20 0x02ef2f54 in QApplicationPrivate::notify_helper (this=0x89cefa0, receiver=0x8a46b6c, e=0xbfeb7400) at kernel/qapplication.cpp:4056
#21 0x02efa67c in QApplication::notify (this=0xbfeb776c, receiver=0x8a46b6c, e=0xbfeb7400) at kernel/qapplication.cpp:3603
#22 0x0111014a in KApplication::notify (this=0xbfeb776c, receiver=0x8a46b6c, event=0xbfeb7400) at ../../kdeui/kernel/kapplication.cpp:302
#23 0x0262e6cb in QCoreApplication::notifyInternal (this=0xbfeb776c, receiver=0x8a46b6c, event=0xbfeb7400) at kernel/qcoreapplication.cpp:610
#24 0x0265b7ce in QCoreApplication::sendEvent (this=0x89ca384) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 QTimerInfoList::activateTimers (this=0x89ca384) at kernel/qeventdispatcher_unix.cpp:572
#26 0x026590e0 in timerSourceDispatch (source=0x89ca350) at kernel/qeventdispatcher_glib.cpp:165
#27 0x06dbce78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#28 0x06dc0720 in ?? () from /lib/libglib-2.0.so.0
#29 0x06dc0853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#30 0x0265902c in QEventDispatcherGlib::processEvents (this=0x89aaa30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#31 0x02f93be5 in QGuiEventDispatcherGlib::processEvents (this=0x89aaa30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#32 0x0262cc79 in QEventLoop::processEvents (this=0xbfeb76c4, flags=) at kernel/qeventloop.cpp:149
#33 0x0262d0ca in QEventLoop::exec (this=0xbfeb76c4, flags=...) at kernel/qeventloop.cpp:201
#34 0x0262f53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#35 0x02ef2dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#36 0x0807a6f5 in _start ()

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

Reported using DrKonqi