Bug 301822 - Yakuake crashed when exiting from shell
Summary: Yakuake crashed when exiting from shell
Status: RESOLVED WORKSFORME
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 2.9.8
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-13 15:56 UTC by Dennis Schridde
Modified: 2018-11-29 09:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (7.01 KB, text/plain)
2012-06-15 07:26 UTC, Dennis Schridde
Details
New crash information added by DrKonqi (6.86 KB, text/plain)
2012-06-20 14:44 UTC, Dennis Schridde
Details
yakuakerc (141 bytes, application/octet-stream)
2012-06-20 23:12 UTC, Dennis Schridde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2012-06-13 15:56:28 UTC
Application: yakuake (2.9.8)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic-pae i686
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I switched windows away from Yakuake (which should minimise it). Then it crashed.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4df2a40 (LWP 1690))]

Thread 2 (Thread 0xb160ab40 (LWP 5475)):
#0  0xb7775424 in __kernel_vsyscall ()
#1  0xb5c40380 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb5428a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb541b06e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb541b1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb601e8e7 in QEventDispatcherGlib::processEvents (this=0xb0d00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb5fea50d in QEventLoop::processEvents (this=0xb160a240, flags=...) at kernel/qeventloop.cpp:149
#7  0xb5fea7a9 in QEventLoop::exec (this=0xb160a240, flags=...) at kernel/qeventloop.cpp:204
#8  0xb5ed394c in QThread::exec (this=0x8b401d0) at thread/qthread.cpp:501
#9  0xb5fc7b5d in QInotifyFileSystemWatcherEngine::run (this=0x8b401d0) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb5ed6de0 in QThreadPrivate::start (arg=0x8b401d0) at thread/qthread_unix.cpp:298
#11 0xb54ecd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb5c4eace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb4df2a40 (LWP 1690)):
[KCrash Handler]
#7  0xb659c474 in QWidget::focusWidget (this=0x0) at kernel/qwidget.cpp:6619
#8  0x0806d323 in SessionStack::raiseSession (this=0x89bcd58, sessionId=8) at /build/buildd/yakuake-2.9.8/app/sessionstack.cpp:104
#9  0x08057884 in SessionStack::qt_metacall (this=0x89bcd58, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0xbfef9238) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_sessionstack.cpp:183
#10 0xb5ff2c9d in metacall (argv=0xbfef9238, idx=47, cl=QMetaObject::InvokeMetaMethod, object=0x89bcd58) at kernel/qmetaobject.cpp:245
#11 QMetaObject::metacall (object=0x89bcd58, cl=QMetaObject::InvokeMetaMethod, idx=47, argv=0xbfef9238) at kernel/qmetaobject.cpp:240
#12 0xb60029bd in QMetaObject::activate (sender=0x89bd618, m=0x807f08c, local_signal_index=1, argv=0xbfef9238) at kernel/qobject.cpp:3566
#13 0x08057c55 in TabBar::tabSelected (this=0x89bd618, _t1=8) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_tabbar.cpp:161
#14 0x0806c886 in TabBar::removeTab (this=0x89bd618, sessionId=6) at /build/buildd/yakuake-2.9.8/app/tabbar.cpp:645
#15 0x08057eec in TabBar::qt_metacall (this=0x89bd618, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfef93b8) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_tabbar.cpp:125
#16 0xb5ff2c9d in metacall (argv=0xbfef93b8, idx=35, cl=QMetaObject::InvokeMetaMethod, object=0x89bd618) at kernel/qmetaobject.cpp:245
#17 QMetaObject::metacall (object=0x89bd618, cl=QMetaObject::InvokeMetaMethod, idx=35, argv=0xbfef93b8) at kernel/qmetaobject.cpp:240
#18 0xb60029bd in QMetaObject::activate (sender=0x89bcd58, m=0x807f07c, local_signal_index=3, argv=0xbfef93b8) at kernel/qobject.cpp:3566
#19 0x080574a5 in SessionStack::sessionRemoved (this=0x89bcd58, _t1=6) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_sessionstack.cpp:259
#20 0x0806e0ca in SessionStack::cleanup (this=0x89bcd58, sessionId=6) at /build/buildd/yakuake-2.9.8/app/sessionstack.cpp:167
#21 0x080576e4 in SessionStack::qt_metacall (this=0x89bcd58, _c=QMetaObject::InvokeMetaMethod, _id=48, _a=0xbfef9518) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_sessionstack.cpp:233
#22 0xb5ff2c9d in metacall (argv=0xbfef9518, idx=79, cl=QMetaObject::InvokeMetaMethod, object=0x89bcd58) at kernel/qmetaobject.cpp:245
#23 QMetaObject::metacall (object=0x89bcd58, cl=QMetaObject::InvokeMetaMethod, idx=79, argv=0xbfef9518) at kernel/qmetaobject.cpp:240
#24 0xb60029bd in QMetaObject::activate (sender=0x8b89540, m=0x807efec, local_signal_index=4, argv=0xbfef9518) at kernel/qobject.cpp:3566
#25 0x08056c85 in Session::destroyed (this=0x8b89540, _t1=6) at /build/buildd/yakuake-2.9.8/obj-i686-linux-gnu/app/moc_session.cpp:175
#26 0x0806f52e in Session::~Session (this=0x8b89540, __in_chrg=<optimized out>) at /build/buildd/yakuake-2.9.8/app/session.cpp:48
#27 0x0806f592 in Session::~Session (this=0x8b89540, __in_chrg=<optimized out>) at /build/buildd/yakuake-2.9.8/app/session.cpp:49
#28 0xb5fffd03 in qDeleteInEventHandler (o=0x8b89540) at kernel/qobject.cpp:4277
#29 0xb6006ca8 in QObject::event (this=0x8b89540, e=0x8b96b98) at kernel/qobject.cpp:1176
#30 0xb6553ed4 in notify_helper (e=0x8b96b98, receiver=0x8b89540, this=0x88c37e0) at kernel/qapplication.cpp:4559
#31 QApplicationPrivate::notify_helper (this=0x88c37e0, receiver=0x8b89540, e=0x8b96b98) at kernel/qapplication.cpp:4531
#32 0xb655930d in QApplication::notify (this=0x8b96b98, receiver=0x8b89540, e=0x8b96b98) at kernel/qapplication.cpp:4288
#33 0xb70d8b61 in KApplication::notify (this=0xbfef9d58, receiver=0x8b89540, event=0x8b96b98) at ../../kdeui/kernel/kapplication.cpp:311
#34 0xb5feb97e in QCoreApplication::notifyInternal (this=0xbfef9d58, receiver=0x8b89540, event=0x8b96b98) at kernel/qcoreapplication.cpp:876
#35 0xb5fefad8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8899370) at kernel/qcoreapplication.cpp:1500
#37 0xb5fefe0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393
#38 0xb601e494 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#39 postEventSourceDispatch (s=0x88c1368) at kernel/qeventdispatcher_glib.cpp:279
#40 0xb541acda in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#41 0xb541b0e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#42 0xb541b1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#43 0xb601e887 in QEventDispatcherGlib::processEvents (this=0x8899ef0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#44 0xb660caaa in QGuiEventDispatcherGlib::processEvents (this=0x8899ef0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#45 0xb5fea50d in QEventLoop::processEvents (this=0xbfef9cb4, flags=...) at kernel/qeventloop.cpp:149
#46 0xb5fea7a9 in QEventLoop::exec (this=0xbfef9cb4, flags=...) at kernel/qeventloop.cpp:204
#47 0xb5fefeba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#48 0xb6551a74 in QApplication::exec () at kernel/qapplication.cpp:3820
#49 0x08058920 in main (argc=0, argv=0x0) at /build/buildd/yakuake-2.9.8/app/main.cpp:73

Reported using DrKonqi
Comment 1 Dennis Schridde 2012-06-15 07:26:29 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
Comment 2 Dennis Schridde 2012-06-20 14:44:53 UTC
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
Comment 3 Eike Hein 2012-06-20 20:55:51 UTC
Mind attaching your yakuakerc? I can't reproduce.
Comment 4 Dennis Schridde 2012-06-20 23:12:06 UTC
Created attachment 72004 [details]
yakuakerc
Comment 5 Eike Hein 2012-06-20 23:25:45 UTC
^ 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.
Comment 6 Andrew Crouthamel 2018-10-29 22:22:17 UTC
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!
Comment 7 Bug Janitor Service 2018-11-13 14:38:32 UTC
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!
Comment 8 Bug Janitor Service 2018-11-29 09:40:16 UTC
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!