Bug 350035 - KDE crashed on a CTRL-D
Summary: KDE crashed on a CTRL-D
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.14.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-07-08 22:02 UTC by Anmol P. Paralkar
Modified: 2018-11-15 22:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anmol P. Paralkar 2015-07-08 22:02:47 UTC
Application: konsole (2.14.2)
KDE Platform Version: 4.14.7 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 3.19.8-100.fc20.i686+PAE i686
Distribution: "Fedora release 20 (Heisenbug)"

-- Information about the crash:
- What I was doing when the application crashed:

I hit CTRL-D and prior to that I had pressed ALT + TAB to switch from Mozilla Firefox (foreground) to KDE (background).

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

Thread 2 (Thread 0xb43c5b40 (LWP 2484)):
#0  0x4ac4f031 in g_mutex_unlock (mutex=mutex@entry=0xb3a004e0) at gthread-posix.c:232
#1  0x4ac08daa in g_main_context_prepare (context=<optimized out>, context@entry=0xb3a004e0, priority=priority@entry=0xb43c5094) at gmain.c:3338
#2  0x4ac09787 in g_main_context_iterate (context=context@entry=0xb3a004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3693
#3  0x4ac099e9 in g_main_context_iteration (context=0xb3a004e0, may_block=1) at gmain.c:3774
#4  0x4f991e2f in QEventDispatcherGlib::processEvents (this=0xb3a00468, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x4f95eb20 in QEventLoop::processEvents (this=this@entry=0xb43c51a4, flags=...) at kernel/qeventloop.cpp:149
#6  0x4f95eeb1 in QEventLoop::exec (this=this@entry=0xb43c51a4, flags=...) at kernel/qeventloop.cpp:204
#7  0x4f840105 in QThread::exec (this=this@entry=0x8dc3ce8) at thread/qthread.cpp:538
#8  0x4f93d9c1 in QInotifyFileSystemWatcherEngine::run (this=0x8dc3ce8) at io/qfilesystemwatcher_inotify.cpp:265
#9  0x4f842c0b in QThreadPrivate::start (arg=0x8dc3ce8) at thread/qthread_unix.cpp:349
#10 0x4aa5dd4c in start_thread (arg=0xb43c5b40) at pthread_create.c:309
#11 0x4a98d74e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 1 (Thread 0xb7785800 (LWP 2482)):
[KCrash Handler]
#7  0x0959bc78 in ?? ()
#8  0x417ee14b in x11EventSourceDispatch (s=s@entry=0x8bfb700, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#9  0x4ac09556 in g_main_dispatch (context=0x8bfa448) at gmain.c:3066
#10 g_main_context_dispatch (context=context@entry=0x8bfa448) at gmain.c:3642
#11 0x4ac09920 in g_main_context_iterate (context=context@entry=0x8bfa448, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3713
#12 0x4ac099e9 in g_main_context_iteration (context=0x8bfa448, may_block=1) at gmain.c:3774
#13 0x4f991e04 in QEventDispatcherGlib::processEvents (this=this@entry=0x8bb8030, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#14 0x417ee30c in QGuiEventDispatcherGlib::processEvents (this=0x8bb8030, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#15 0x4f95eb20 in QEventLoop::processEvents (this=this@entry=0xbfc65b24, flags=...) at kernel/qeventloop.cpp:149
#16 0x4f95eeb1 in QEventLoop::exec (this=this@entry=0xbfc65b24, flags=...) at kernel/qeventloop.cpp:204
#17 0x4f964cdb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#18 0x41735ea5 in QApplication::exec () at kernel/qapplication.cpp:3823
#19 0x4f3d7ac3 in kdemain (argc=1, argv=0xbfc65cd4) at /usr/src/debug/konsole-4.14.3/src/main.cpp:86
#20 0x080486cc in main (argc=1, argv=0xbfc65cd4) at /usr/src/debug/konsole-4.14.3/i686-redhat-linux-gnu/src/konsole_dummy.cpp:3

Possible duplicates by query: bug 349722, bug 346123, bug 343138, bug 341830, bug 341641.

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-31 04:01:53 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 2 Bug Janitor Service 2018-11-15 10:54: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 3 Anmol P. Paralkar 2018-11-15 15:51:17 UTC
Hi,

 Sorry for the delay in responding. I am on Ubuntu 18.04.1 LTS and I just retried this a few times - I do not see this issue anymore. Please do close the case. Thank you for your support!

Thanks,
Anmol P. Paralkar
Comment 4 Andrew Crouthamel 2018-11-15 22:53:26 UTC
Thanks for the update!