Description of problem: I copied a file name to clipboard via mouse highlight then right-click copy. Version-Release number of selected component: konsole5-15.08.3-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/konsole -session 1015bcdd3dd000144970482500000070600021_1450480442_889697 crash_function: poll_for_reply executable: /usr/bin/konsole global_pid: 2330 kernel: 4.2.7-300.fc23.x86_64 runlevel: 3 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 poll_for_reply at xcb_in.c:428 #1 wait_for_reply at xcb_in.c:515 #2 xcb_wait_for_reply at xcb_in.c:546 #4 XIQueryDevice at XIQueryDevice.c:60 #5 QXcbConnection::handleEnterEvent at qxcbconnection_xi2.cpp:830 #6 QXcbWindow::handleEnterNotifyEvent at qxcbwindow.cpp:2319 #7 QXcbConnection::handleXcbEvent at qxcbconnection.cpp:1083 #8 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1527 #9 QObject::event at kernel/qobject.cpp:1239 #10 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3716
Created attachment 1107804 [details] File: backtrace
Created attachment 1107805 [details] File: cgroup
Created attachment 1107806 [details] File: core_backtrace
Created attachment 1107807 [details] File: dso_list
Created attachment 1107808 [details] File: environ
Created attachment 1107809 [details] File: exploitable
Created attachment 1107810 [details] File: limits
Created attachment 1107811 [details] File: maps
Created attachment 1107812 [details] File: mountinfo
Created attachment 1107813 [details] File: namespaces
Created attachment 1107814 [details] File: open_fds
Created attachment 1107815 [details] File: proc_pid_status
Created attachment 1107816 [details] File: var_log_messages
I've run into konsole failing to completely open several times now (the new konsole was on a different virtual desktop than the original running konsole...whether or not related I don't know). Here is an update to behavior I've noticed when konsole fails. The graphics of the konsole does not refresh, and is a copy of whatever was under the konsole at the moment of creation. Just as an experiment, I clicked where I knew the "new tab" button should be, and I see the title change to reflect a new konsole tab (but graphics remains locked at the original background at moment of create). If I mouse click in the middle and blindly type "exit", I see the title bar reflect this as succeeding...the konsole is apparently working so far as text entry goes, but graphics fails to show this (refresh stopped at the moment of creating the window frame). When I finally exit konsole completely, either by blindly typing "exit" or by clicking on window manager "x" to close, konsole eventually goes from no CPU usage to maxed out on one core at 100%. I have to kill this undisplayed konsole manually by pid (e.g., under top). I believe there is a threading issue here. Something fails to run and blocks before graphics refresh, with no significant CPU use; upon close the CPU goes up to 100% and the PID remains active. Myself and other people have noticed that upon shutdown or reboot of the system there is sometimes an excessive delay as init waits for a user session to close. I feel very strongly that these shutdown delays are likely related to some wider threading issue, such as going to 100% CPU upon close of a konsole (if closing konsole results in a PID which does not go away then this may be what the session close is hung up on). Some bug report tool issues do not allow reporting this, as they say the backtrace is too large and cannot be used (the abrt tool just stops reporting and throws away the report when the backtrace is too large).
There's one known 'konsole using 100% cpu' issue, that has something to do with nvidia-libs (as part of nvidia's binary video driver). Do you happen to use that driver?
(In reply to Rex Dieter from comment #15) > There's one known 'konsole using 100% cpu' issue, that has something to do > with nvidia-libs (as part of nvidia's binary video driver). Do you happen > to use that driver? Yes, I do currently use nVidia drivers. The nouveau driver does not refresh correctly, and is completely unusable...stability actually increased by using the nVidia driver. I would be interested in any reference to the konsole 100% CPU bug which may be related to this.
https://bugs.kde.org/show_bug.cgi?id=343803 and https://devtalk.nvidia.com/default/topic/879586/kf5-konsole-15-04-and-15-08-consumes-100-cpu-on-close-only-with-proprietary-nvidia-driver/
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.