Bug 357108

Summary: konsole crash when switching from console (alt-f2,f3,etc.) to desktop (alt-f1)
Product: [Applications] konsole Reporter: smkr <steve.mckuhr>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version: 15.08.3   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description smkr 2015-12-23 21:37:38 UTC
Application: konsole (15.08.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.8-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

1.Docked the laptop.
2. Switched to console #2 (alt-f2).
3. Switched back to desktop (alt-f1).

I need to do this in order to get my external monitor activated after docking in. In docking mode only the monitor is being used.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  QXcbScreen::mapFromNative (this=0x0, pos=...) at qxcbscreen.cpp:249
#6  0x00007f4a7452e1b8 in QXcbWindow::handleLeaveNotifyEvent (this=0x560cd79091e0, event=<optimized out>) at qxcbwindow.cpp:2345
#7  0x00007f4a74517ab5 in QXcbConnection::handleXcbEvent (this=this@entry=0x560cd77b8a10, event=event@entry=0x7f4a6c015410) at qxcbconnection.cpp:1086
#8  0x00007f4a74518433 in QXcbConnection::processXcbEvents (this=0x560cd77b8a10) at qxcbconnection.cpp:1527
#9  0x00007f4a8ab061b1 in QObject::event (this=0x560cd77b8a10, e=<optimized out>) at kernel/qobject.cpp:1239
#10 0x00007f4a8b7bc41c in QApplicationPrivate::notify_helper (this=this@entry=0x560cd77caf00, receiver=receiver@entry=0x560cd77b8a10, e=e@entry=0x7f4a6c0155a0) at kernel/qapplication.cpp:3716
#11 0x00007f4a8b7c18e6 in QApplication::notify (this=0x7fffaf2aa320, receiver=0x560cd77b8a10, e=0x7f4a6c0155a0) at kernel/qapplication.cpp:3499
#12 0x00007f4a8aad677b in QCoreApplication::notifyInternal (this=0x7fffaf2aa320, receiver=0x560cd77b8a10, event=event@entry=0x7f4a6c0155a0) at kernel/qcoreapplication.cpp:965
#13 0x00007f4a8aad8b76 in QCoreApplication::sendEvent (event=0x7f4a6c0155a0, receiver=<optimized out>) at kernel/qcoreapplication.h:224
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x560cd7779600) at kernel/qcoreapplication.cpp:1593
#15 0x00007f4a8aad9058 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451
#16 0x00007f4a8ab2cae3 in postEventSourceDispatch (s=0x560cd7809f30) at kernel/qeventdispatcher_glib.cpp:271
#17 0x00007f4a8549fe3a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#18 0x00007f4a854a01d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#19 0x00007f4a854a027c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#20 0x00007f4a8ab2ceef in QEventDispatcherGlib::processEvents (this=0x560cd77fe240, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#21 0x00007f4a8aad3f0a in QEventLoop::exec (this=this@entry=0x7fffaf2aa1d0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#22 0x00007f4a8aadbfec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#23 0x00007f4a8b00a60c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1527
#24 0x00007f4a8b7b8855 in QApplication::exec () at kernel/qapplication.cpp:2976
#25 0x00007f4a9189e986 in kdemain (argc=<optimized out>, argv=<optimized out>) at ../../src/main.cpp:113
#26 0x00007f4a89c16580 in __libc_start_main () from /lib64/libc.so.6
#27 0x0000560cd6976ba9 in _start ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-11-01 13:53:13 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-16 11:37:05 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 smkr 2018-11-17 20:13:47 UTC
Hello, I won't be able to test as I am not using KDE anymore, sorry.
Comment 4 Bug Janitor Service 2018-12-02 03:44:33 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 5 Bug Janitor Service 2018-12-17 03:44:24 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!