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: The crash happens when switching from external monitor to laptop screen or viceversa as described in bug 351025 comment 16. While performing the switch to/from external monitor/laptop screen I've also noticed a couple of weird Konsole behaviors: 1. If Konsole doesn't crash and there are several Konsole windows spread across multiple desktops *all* Konsole windows will get moved to the current desktop. I've tested with 3 Konsole windows opened on desktops 1 to 3. Changed to desktop 3 before undocking laptop followed by a Ctrl-Alt-F2 and Ctrl-Alt-F1 and all Konsole windows got moved to desktop 3. 2. A long 'ls' listing -- long enough to fill the screen top to bottom -- will result in only the few bottom lines actually srolling up with the rest of the screen remaining unchanged. A clear screen (Ctrl-L) will leave traces of output on the screen. Similar behavior if I scroll down in a 'vim' Konsole session or a 'man' page, or 'less' a file. None of the above behaviors happens with RoxTerm. -- 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 0x00007f789788e9aa in QXcbWindow::handleEnterNotifyEvent (this=0x560b971063b0, event=<optimized out>) at qxcbwindow.cpp:2327 #7 0x00007f7897877afd in QXcbConnection::handleXcbEvent (this=this@entry=0x560b96fb5a10, event=event@entry=0x7f78900c54d0) at qxcbconnection.cpp:1083 #8 0x00007f7897878433 in QXcbConnection::processXcbEvents (this=0x560b96fb5a10) at qxcbconnection.cpp:1527 #9 0x00007f78ade681b1 in QObject::event (this=0x560b96fb5a10, e=<optimized out>) at kernel/qobject.cpp:1239 #10 0x00007f78aeb1e41c in QApplicationPrivate::notify_helper (this=this@entry=0x560b96fc3560, receiver=receiver@entry=0x560b96fb5a10, e=e@entry=0x7f7890011870) at kernel/qapplication.cpp:3716 #11 0x00007f78aeb238e6 in QApplication::notify (this=0x7ffdfff31d30, receiver=0x560b96fb5a10, e=0x7f7890011870) at kernel/qapplication.cpp:3499 #12 0x00007f78ade3877b in QCoreApplication::notifyInternal (this=0x7ffdfff31d30, receiver=0x560b96fb5a10, event=event@entry=0x7f7890011870) at kernel/qcoreapplication.cpp:965 #13 0x00007f78ade3ab76 in QCoreApplication::sendEvent (event=0x7f7890011870, receiver=<optimized out>) at kernel/qcoreapplication.h:224 #14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x560b96f76600) at kernel/qcoreapplication.cpp:1593 #15 0x00007f78ade3b058 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #16 0x00007f78ade8eae3 in postEventSourceDispatch (s=0x560b96ffd070) at kernel/qeventdispatcher_glib.cpp:271 #17 0x00007f78a8801e3a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x00007f78a88021d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #19 0x00007f78a880227c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x00007f78ade8eeef in QEventDispatcherGlib::processEvents (this=0x560b970063c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #21 0x00007f78ade35f0a in QEventLoop::exec (this=this@entry=0x7ffdfff31be0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #22 0x00007f78ade3dfec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #23 0x00007f78ae36c60c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1527 #24 0x00007f78aeb1a855 in QApplication::exec () at kernel/qapplication.cpp:2976 #25 0x00007f78b4c00986 in kdemain (argc=<optimized out>, argv=<optimized out>) at ../../src/main.cpp:113 #26 0x00007f78acf78580 in __libc_start_main () from /lib64/libc.so.6 #27 0x0000560b9531aba9 in _start () Possible duplicates by query: bug 355585. Reported using DrKonqi
Distro : Korora release 23 (Coral) Konsole (Version 15.08.3) using : KDE Frameworks 5.17.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system Laptop : Dell Latitude E5530 While I did not experience a crash, I had display issues in Konsole after rebooting and connecting external monitor. Description of Issue : 1. While standalone, booted up laptop 2. Connected external monitor (correctly switches to Primary) 3. Started Konsole 4. Instead of displaying the terminal, the Konsole window instead contains the portion of the desktop and apps that it appeared over. 5. Moving does make it semi-transparent, but does not correct the display 6. I can go to Profile Settings and make changes, and they are saved, but the window is not updated What "resolved" the issue : 1. I rebooted the laptop with the external monitor connected 2. The Profile changes I'd made while "broken" were correctly displayed (change background image and adjust transparency) I will attempt to replicate the issue and provide more details.
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!
Hello, I won't be able to test as I am not using KDE anymore, sorry.
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!