Summary: | Yakuake crashed when exiting from shell | ||
---|---|---|---|
Product: | [Applications] yakuake | Reporter: | Dennis Schridde <dschridde+kde> |
Component: | general | Assignee: | Eike Hein <hein> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | dschridde+kde |
Priority: | NOR | ||
Version: | 2.9.8 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi yakuakerc |
Description
Dennis Schridde
2012-06-13 15:56:28 UTC
Created attachment 71848 [details]
New crash information added by DrKonqi
yakuake (2.9.8) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
I created a new window/tab using ctrl+n (or ctrl+shift+n, not exactly sure anymore) and then closed that using ctrl+d. Instead of opening a new shell in that tab, yakuake crashed.
- Unusual behavior I noticed:
In the first tab tmux hung with "[exited]", which was the reason for me creating a new tab.
-- Backtrace (Reduced):
#7 0xb65f4474 in QWidget::focusWidget (this=0x0) at kernel/qwidget.cpp:6619
#8 0x0806d323 in SessionStack::raiseSession (this=0x8e38558, sessionId=6) at /build/buildd/yakuake-2.9.8/app/sessionstack.cpp:104
#9 0x08057884 in SessionStack::qt_metacall (this=0x8e38558, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0xbfe029d8) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_sessionstack.cpp:183
#10 0xb604ac9d in metacall (argv=0xbfe029d8, idx=47, cl=QMetaObject::InvokeMetaMethod, object=0x8e38558) at kernel/qmetaobject.cpp:245
[...]
#13 0x08057c55 in TabBar::tabSelected (this=0x8e38df8, _t1=6) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_tabbar.cpp:161
Created attachment 71986 [details]
New crash information added by DrKonqi
yakuake (2.9.8) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
I closed the shell running inside Yakuake using ^D.
-- Backtrace (Reduced):
#7 0xb652d474 in QWidget::focusWidget (this=0x0) at kernel/qwidget.cpp:6619
#8 0x0806d323 in SessionStack::raiseSession (this=0x89216a0, sessionId=12) at /build/buildd/yakuake-2.9.8/app/sessionstack.cpp:104
#9 0x08057884 in SessionStack::qt_metacall (this=0x89216a0, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0xbfeb42c8) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_sessionstack.cpp:183
#10 0xb5f83c9d in metacall (argv=0xbfeb42c8, idx=47, cl=QMetaObject::InvokeMetaMethod, object=0x89216a0) at kernel/qmetaobject.cpp:245
[...]
#13 0x08057c55 in TabBar::tabSelected (this=0x8921f08, _t1=12) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_tabbar.cpp:161
Mind attaching your yakuakerc? I can't reproduce. Created attachment 72004 [details]
yakuakerc
^ Thanks. I've been slacking on this because I don't have access to my regular dev environment at the moment, but I'll look into it soon. Basically what happens going by the backtrace is that closing a tab causes an adjacent tab to be raised and focus to be given to whatever its active terminal is, but for some reason the pointer to the latter is pointing at nothing in your case. That obviously isn't supposed to happen (and, given the absence of similar reports, normally doesn't). The quick workaround would be to add a null pointer check to at least avoid the crash, but the real fix is going to be to figure out why it's null in the first place. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |