Bug 207938 - Dolphin crashed while opening new tab by double clicking to the right of the current tab
Summary: Dolphin crashed while opening new tab by double clicking to the right of the ...
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-20 03:21 UTC by Victor Banke
Modified: 2009-09-20 10:36 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 Victor Banke 2009-09-20 03:21:45 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 i686

What I was doing when the application crashed:
I had a few tabs open with different file folders in each one, and Dolphin is crashing consistantly when I double-click to the right of the rightmost open tab to open a new tab.

Note that if the current tabs are the same (in the same folder) double clicking to open a new tab does NOT crasg Dolphin. Also, pressing Ctrl+T under any circumstances has not crashed Dolphin ever for me.


 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 0 (LWP 6970)]

Thread 2 (Thread 0xb3f2bb70 (LWP 7021)):
#0  0xb7f8c424 in __kernel_vsyscall ()
#1  0xb642aec2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb6515824 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb248e7e1 in metronom_sync_loop () from /usr/lib/libxine.so.1

Thread 1 (Thread 0xb5a01920 (LWP 6970)):
[KCrash Handler]
#6  0xb6e53fac in ?? () from /usr/lib/libQtGui.so.4
#7  0xb6e55eb7 in ?? () from /usr/lib/libQtGui.so.4
#8  0xb6e56211 in QTabBar::setTabText () from /usr/lib/libQtGui.so.4
#9  0xb77657e9 in KAcceleratorManagerPrivate::calculateAccelerators () from /usr/lib/libkdeui.so.5
#10 0xb7767dc0 in KAcceleratorManagerPrivate::manage () from /usr/lib/libkdeui.so.5
#11 0xb776801e in KAcceleratorManager::manage () from /usr/lib/libkdeui.so.5
#12 0xb7769a1d in KCheckAccelerators::checkAccelerators () from /usr/lib/libkdeui.so.5
#13 0xb7769e8a in KCheckAccelerators::autoCheckSlot () from /usr/lib/libkdeui.so.5
#14 0xb7769f41 in KCheckAccelerators::qt_metacall () from /usr/lib/libkdeui.so.5
#15 0xb67e39ac in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb67e45e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb681da87 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#18 0xb67e905e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#19 0xb67ddb5f in QObject::event () from /usr/lib/libQtCore.so.4
#20 0xb69e1964 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#21 0xb69e904c in QApplication::notify () from /usr/lib/libQtGui.so.4
#22 0xb770f46a in KApplication::notify () from /usr/lib/libkdeui.so.5
#23 0xb67cdfcb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#24 0xb67fb79e in ?? () from /usr/lib/libQtCore.so.4
#25 0xb67f8780 in ?? () from /usr/lib/libQtCore.so.4
#26 0xb5defd98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb5df33e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#28 0xb5df3513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb67f86cc in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb6a7f695 in ?? () from /usr/lib/libQtGui.so.4
#31 0xb67cc579 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#32 0xb67cc9ca in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#33 0xb67cee3f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#34 0xb69e17e7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#35 0x0807a725 in _start ()

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-09-20 10:36:46 UTC
Thanks for the bug report! This is an issue which is known already - it's a bug in Qt 4.5.2 which will be fixed in Qt 4.5.3.

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