Bug 207469 - Dolphin Crashed when Opening a New Tab
Summary: Dolphin Crashed when Opening a New Tab
Status: RESOLVED DUPLICATE of bug 202767
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-09-15 16:54 UTC by Anthony Scire
Modified: 2009-09-15 21:29 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 Anthony Scire 2009-09-15 16:54:59 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH x86_64

What I was doing when the application crashed:
I am almost certain this is a duplicate of #202767, but for completeness sake, I am reporting using the crash reporting assistant.

I double-clicked the empty space next to an existing tab.  The new tab opened, and immediately after, the application crashed.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f947db7927a in ?? () from /usr/lib/libQtGui.so.4
#6  0x00007f947db7b02d in ?? () from /usr/lib/libQtGui.so.4
#7  0x00007f947db7b32a in QTabBar::setTabText () from /usr/lib/libQtGui.so.4
#8  0x00007f947eae0593 in KAcceleratorManagerPrivate::calculateAccelerators (item=0x21e7a70, used=@0x7fff18908320)
    at /home/phil/kdemod/core/kdelibs/src/kdelibs-4.3.1/kdeui/shortcuts/kacceleratormanager.cpp:229
#9  0x00007f947eae2a0e in KAcceleratorManagerPrivate::manage (widget=<value optimized out>) at /home/phil/kdemod/core/kdelibs/src/kdelibs-4.3.1/kdeui/shortcuts/kacceleratormanager.cpp:192
#10 0x00007f947eae2c3b in KAcceleratorManager::manage (widget=0x21a6b20, programmers_mode=false) at /home/phil/kdemod/core/kdelibs/src/kdelibs-4.3.1/kdeui/shortcuts/kacceleratormanager.cpp:505
#11 0x00007f947eae4376 in KCheckAccelerators::checkAccelerators (this=0x2192e10, automatic=true) at /home/phil/kdemod/core/kdelibs/src/kdelibs-4.3.1/kdeui/shortcuts/kcheckaccelerators.cpp:243
#12 0x00007f947eae47de in KCheckAccelerators::autoCheckSlot (this=0x2192e10) at /home/phil/kdemod/core/kdelibs/src/kdelibs-4.3.1/kdeui/shortcuts/kcheckaccelerators.cpp:197
#13 0x00007f947eae4858 in KCheckAccelerators::qt_metacall (this=0x2192e10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff189085c0)
    at /home/phil/kdemod/core/kdelibs/src/build/kdeui/kcheckaccelerators.moc:68
#14 0x00007f947d2e7dec in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0x00007f947d2e1d93 in QObject::event () from /usr/lib/libQtCore.so.4
#16 0x00007f947d76566c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#17 0x00007f947d76c93e in QApplication::notify () from /usr/lib/libQtGui.so.4
#18 0x00007f947ea938f6 in KApplication::notify (this=0x7fff18908f10, receiver=0x2192e30, event=0x7fff18908bc0) at /home/phil/kdemod/core/kdelibs/src/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#19 0x00007f947d2d2cec in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#20 0x00007f947d2fe302 in ?? () from /usr/lib/libQtCore.so.4
#21 0x00007f947d2fb26d in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007f9479002dbe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007f9479006568 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#24 0x00007f9479006690 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007f947d2fb1b6 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0x00007f947d7f861e in ?? () from /usr/lib/libQtGui.so.4
#27 0x00007f947d2d15f2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0x00007f947d2d19c4 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0x00007f947d2d3b79 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#30 0x0000000000439515 in _start ()

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

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-09-15 21:29:45 UTC
Thanks for the bug report.

> I am almost certain this is a duplicate of #202767

I agree. Frames #5 and #6 are not visible due to missing debugging symbols, but I think it's impossible to crash in QTabBar::setTabText () in the described use case in any other way.

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