Summary: | Konqueror crash when clicking on tab with SIG 6 | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Avuton Olrich <avuton> |
Component: | tabbing | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | mgolden, oleg.atamanenko+kde, vdboor, vkrevs, zahl |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Avuton Olrich
2005-09-30 12:53:01 UTC
Same happened to me with 3.5 svn a while ago. #11 0x00c3dc24 in KonqViewManager::removeTab (this=0x9899500, tab=0x9bebadc) at konq_viewmgr.cc:563 #12 0x00c6aa33 in KonqMainWindow::slotRemoveTabPopupDelayed (this=0x988fe50) at konq_mainwindow.cc:2743 #13 0x00c7ff31 in KonqMainWindow::qt_invoke (this=0x988fe50, _id=163, _o=0xbff102d0) at konq_mainwindow.moc:681 #14 0x01411450 in QObject::activate_signal () *** Bug 135715 has been marked as a duplicate of this bug. *** And a similar case for me (was the slotRemoveTabPopupDelayed optimized away?): Konqueror 3.5.1 (KDE 3.5.1 Level "a" SUSE 10.1) #10 0x00002b0ef5ed735f in __cxa_pure_virtual () from /usr/lib64/libstdc++.so.6 #11 0x00002b0ef8c10a7d in KonqViewManager::removeTab () from /opt/kde3/lib64/libkdeinit_konqueror.so #12 0x00002b0ef8c21269 in KonqMainWindow::qt_invoke () from /opt/kde3/lib64/libkdeinit_konqueror.so #13 0x00002b0ef54fe7ac in QObject::activate_signal () I wonder if this is due to an interaction with gestures. (The bug report says nothing about when closing a tab, and I do not think I did that either) But there is (I have) TWO gesture defined that closes a tab: Press, move right, move down, move right, release Press, mowe down, move right, release This could easily interact with clicking on tabs... So, getting both a key click to show a tab and a keyboard shortcut to close it at the same time... IMHO gestures should be integrated with other shortcuts in the menu bug:73553 *** Bug 148672 has been marked as a duplicate of this bug. *** *** Bug 161546 has been marked as a duplicate of this bug. *** *** Bug 163360 has been marked as a duplicate of this bug. *** Does anybody have this problem in 3.5.10? I can't reproduce this bug since 3.5.10. (I haven't either...) If that changes and somebody hits it somehow, please reopen. Thanks! |