I had several windows open and decided to close them all. After closing several of them, I tried to close my Pidgin chat session using the X button in the top right (which I had attached Buddy List as a tab to), but the Pidgin window still stayed open even after 'ps aux | grep -i pidgin' showed that Pidgin exited. Even if I switch activities, the Pidgin window is still visible. However, clicks go straight through the window, triggering events on whatever is behind the ghostly Pidgin window even if I'm clicking on the window decorations, not the content of the window. The Alt+Tab window list doesn't show the window. As a sort-of workaround, turning off compositing with Alt+Shift+F12 makes the Pidgin window disappear and it stays gone if I turn compositing back on. Reproducible: Didn't try Steps to Reproduce: 1. Open Pidgin 2. Start a chat 3. Focus the Pidgin chat window 4. Window menu->Attach as tab to Buddy List 5. Window menu->Activities->All Activities 6. Close Pidgin by clicking the X on the top right Actual Results: Pidgin window cannot be closed or focused even though 'ps aux | grep -i pidgin' shows that Pidgin has already exited. Clicking on the Pidgin window will launch the desktop icon behind it. xwininfo reports the window id of the dead Pidgin window as "plasma-desktop" If I switch activities, the Pidgin window switches too, but still can't be clicked or interacted with in any way, though clicking in the Pidgin window will affect the window (or desktop icon) below Pidgin. Expected Results: Pidgin's window should have disappeared when Pidgin completely exited. I have compositing enabled with the following effects enabled from Configure Desktop->Desktop Effects in addition to the default enabled effects: Invert, Enabled Zoom, Translucency, Wobbly Windows, and Desktop Cube. Under General Translucency Settings, I've set all sliders to the third tick counting from the right. Under Window Behavior, Focus stealing prevention is set to High. Graphics information: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 220/PCIe/SSE2 OpenGL core profile version string: 3.3.0 NVIDIA 304.121 OpenGL core profile shading language version string: 3.30 NVIDIA via Cg compiler Versions: Qt: 4.8.6 KDE Development Platform: 4.13.3 KWin: 4.11.11 X.Org X Server 1.14.3.901 (1.14.4 RC 1) (Release Date: 2013-10-26) OS: Linux 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) x86_64 x86_64 x86_64 GNU/Linux Pidgin 2.10.9 (libpurple 2.10.9) KWin RPM: kwin-4.11.11-115.3.x86_64 Pidgin RPM: pidgin-2.10.9-4.18.1.x86_64 Xorg RPM: xorg-x11-server-7.6_1.14.3.901-8.1.x86_64 KWin gives me a warning about disabled triple buffering in ~/.xsession-errors-:0 > kwin(16595) KWin::GlxBackend::present: > It seems you are using the nvidia driver without triple buffering > You must export __GL_YIELD="USLEEP" to prevent large CPU overhead on synced swaps > Preferably, enable the TripleBuffer Option in the xorg.conf Device > For this reason, the tearing prevention has been disabled. > See https://bugs.kde.org/show_bug.cgi?id=322060 NVidia related RPMS: > rpm -qa | fgrep -i 304.121 nvidia-gfxG02-kmp-desktop-304.121_k3.11.6_4-36.1.x86_64 nvidia-gfxG02-kmp-desktop-304.121_k3.11.6_4-31.1.x86_64 nvidia-gfxG02-kmp-desktop-304.121_k3.11.6_4-37.1.x86_64 nvidia-computeG02-304.121-38.1.x86_64 x11-video-nvidiaG02-304.121-38.1.x86_64
> Reproducible: Didn't try Please do - if it's reproducible, we can check for some things that might trigger such. > I have compositing enabled with the following effects ... Many thanks for your efforts in collecting information, but please attach the output of qdbus org.kde.KWin /KWin supportInformation > KWin gives me a warning about disabled triple buffering This means v'sync is forcefully deactivated - if you want it, you've to opt into one of the proposed solutions, see bug #322060
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 is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
This issue report is quite old. Can you please confirm, that it still persists with Plasma 5.23?
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!
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!