Bug 343138 - Crashes after "exit" after running ./update.sh for widelands update builds.
Summary: Crashes after "exit" after running ./update.sh for widelands update builds.
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-22 02:37 UTC by Joseph O Morrow
Modified: 2018-10-31 04:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.74 KB, text/plain)
2015-05-29 13:42 UTC, Joseph O Morrow
Details
New crash information added by DrKonqi (3.35 KB, text/plain)
2015-06-07 17:26 UTC, Joseph O Morrow
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph O Morrow 2015-01-22 02:37:05 UTC
1) Start konsole
2) Run ./update.sh from bazaar/widelands
3) "exit"
4) Window closes after more time than usual
5) After 20-30 seconds, crash box appears (kde bugs)

Reproducible: Always

Steps to Reproduce:
1. (see details above)
2.
3.

Actual Results:  
(see details above)

Expected Results:  
konsole should exit normally. Always does under other circumstances.

Application: konsole (2.14.2)
KDE Platform Version: 4.14.3
Qt Version: 4.8.6
Operating System: Linux 3.17.8-200.fc20.i686+PAE i686
Distribution: "Fedora release 20 (Heisenbug)"

-- Information about the crash:
After I typed "exit" after the widelands update build (./update.sh) the window took extra time to close. Then a few seconds later, this crash system appeared for reporting the bug.

The crash can be reproduced every time.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb404e800 (LWP 14826))]

Thread 2 (Thread 0xb1174b40 (LWP 14833)):
#0  0xb77adcbc in __kernel_vsyscall ()
#1  0xb57adc82 in __GI___clock_gettime (clock_id=1, tp=0xb1173f44) at ../sysdeps/unix/clock_gettime.c:115
#2  0xb682b34d in do_gettime (frac=0xb1173f38, sec=0xb1173f30) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0xb691d313 in updateCurrentTime (this=0xb0802074) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0xb0802074, tm=...) at kernel/qeventdispatcher_unix.cpp:460
#6  0xb691b6db in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb1174038) at kernel/qeventdispatcher_glib.cpp:143
#7  0xb691b78d in timerSourcePrepare (source=0xb0802040, timeout=timeout@entry=0xb1174038) at kernel/qeventdispatcher_glib.cpp:176
#8  0xb4c24dbf in g_main_context_prepare (context=<optimized out>, context@entry=0xb08004e0, priority=priority@entry=0xb1174094) at gmain.c:3340
#9  0xb4c25787 in g_main_context_iterate (context=context@entry=0xb08004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3693
#10 0xb4c259e9 in g_main_context_iteration (context=0xb08004e0, may_block=1) at gmain.c:3774
#11 0xb691b83f in QEventDispatcherGlib::processEvents (this=0xb0800468, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#12 0xb68e8530 in QEventLoop::processEvents (this=this@entry=0xb11741a4, flags=...) at kernel/qeventloop.cpp:149
#13 0xb68e88c1 in QEventLoop::exec (this=this@entry=0xb11741a4, flags=...) at kernel/qeventloop.cpp:204
#14 0xb67c9b75 in QThread::exec (this=this@entry=0x98702c8) at thread/qthread.cpp:538
#15 0xb68c73d1 in QInotifyFileSystemWatcherEngine::run (this=0x98702c8) at io/qfilesystemwatcher_inotify.cpp:265
#16 0xb67cc67b in QThreadPrivate::start (arg=0x98702c8) at thread/qthread_unix.cpp:349
#17 0xb674ed4c in start_thread (arg=0xb1174b40) at pthread_create.c:309
#18 0xb579f82e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 1 (Thread 0xb404e800 (LWP 14826)):
[KCrash Handler]
#7  0x00000000 in ?? ()
#8  0xb5d93825 in QApplication::x11ProcessEvent (this=0xbfa52628, event=event@entry=0xbfa5229c) at kernel/qapplication_x11.cpp:3443
#9  0xb5dbf93b in x11EventSourceDispatch (s=s@entry=0x9708928, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#10 0xb4c25556 in g_main_dispatch (context=0x9708278) at gmain.c:3066
#11 g_main_context_dispatch (context=context@entry=0x9708278) at gmain.c:3642
#12 0xb4c25920 in g_main_context_iterate (context=context@entry=0x9708278, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3713
#13 0xb4c259e9 in g_main_context_iteration (context=0x9708278, may_block=1) at gmain.c:3774
#14 0xb691b83f in QEventDispatcherGlib::processEvents (this=this@entry=0x967e000, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#15 0xb5dbfafc in QGuiEventDispatcherGlib::processEvents (this=0x967e000, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#16 0xb68e8530 in QEventLoop::processEvents (this=this@entry=0xbfa52564, flags=...) at kernel/qeventloop.cpp:149
#17 0xb68e88c1 in QEventLoop::exec (this=this@entry=0xbfa52564, flags=...) at kernel/qeventloop.cpp:204
#18 0xb68ee6eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#19 0xb5d07745 in QApplication::exec () at kernel/qapplication.cpp:3823
#20 0xb7705403 in kdemain (argc=1, argv=0xbfa52714) at /usr/src/debug/konsole-4.14.3/src/main.cpp:86
#21 0x080486cc in main (argc=1, argv=0xbfa52714) at /usr/src/debug/konsole-4.14.3/i686-redhat-linux-gnu/src/konsole_dummy.cpp:3

Possible duplicates by query: bug 343103, bug 342248, bug 342216, bug 341830, bug 341641.

Report to https://bugs.kde.org/
Comment 1 Joseph O Morrow 2015-05-29 13:42:36 UTC
Created attachment 92906 [details]
New crash information added by DrKonqi

konsole (2.14.2) on KDE Platform 4.14.7 using Qt 4.8.6

- What I was doing when the application crashed:

Closed using the "exit" command (crash notification takes a few seconds to appear).

-- Backtrace (Reduced):
#8  0xb5d998d5 in QApplication::x11ProcessEvent (this=0xbff1ab08, event=event@entry=0xbff1a77c) at kernel/qapplication_x11.cpp:3443
#9  0xb5dc59eb in x11EventSourceDispatch (s=s@entry=0x83a6000, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#10 0xb4c29556 in g_main_dispatch (context=0x83a4750) at gmain.c:3066
#11 g_main_context_dispatch (context=context@entry=0x83a4750) at gmain.c:3642
#12 0xb4c29920 in g_main_context_iterate (context=context@entry=0x83a4750, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3713
Comment 2 Joseph O Morrow 2015-05-29 14:18:18 UTC
If multiply konsole windows are running at time of crash, they all close.
Comment 3 Joseph O Morrow 2015-06-07 17:26:22 UTC
Created attachment 93062 [details]
New crash information added by DrKonqi

konsole (2.14.2) on KDE Platform 4.14.7 using Qt 4.8.6

- What I was doing when the application crashed:

I had run yum update on another linux machine on home network, followed by a yum update on local machine.

Crash widget appears 5-10 seconds after "exit" command given to konsole (konsole window disappears immediately after "exit" command).

-- Backtrace (Reduced):
#8  0xb5cef8d5 in QApplication::x11ProcessEvent (this=0xbfd37ee8, event=event@entry=0xbfd37b5c) at kernel/qapplication_x11.cpp:3443
#9  0xb5d1b9eb in x11EventSourceDispatch (s=s@entry=0x97f2000, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#10 0xb4b7f556 in g_main_dispatch (context=0x97f0750) at gmain.c:3066
#11 g_main_context_dispatch (context=context@entry=0x97f0750) at gmain.c:3642
#12 0xb4b7f920 in g_main_context_iterate (context=context@entry=0x97f0750, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3713
Comment 4 Joseph O Morrow 2015-06-07 17:31:17 UTC
There were a few times recently when konsole did not crash under similar circumstances. However, there were also a few cases where my machine unexpectedly rebooted while running either "yum update" (locally) or "scp" in konsole.
Comment 5 Andrew Crouthamel 2018-10-31 03:58:12 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 6 Joseph O Morrow 2018-10-31 04:09:59 UTC
I'm not aware of when this bug was fixed, but it has not been a problem for some time.
Comment 7 Joseph O Morrow 2018-10-31 04:16:06 UTC
I kept getting an "error" when attempting to change NEEDSINFO to REPORTED.