Created attachment 1261470 [details] Script to restart kwin without logging in and out Kwin makes the screen unresponsive after a while causing half of it to turn black. See this image for more information http://imgur.com/a/g6ZvN Version-Release number of selected component (if applicable): 5.8.6-1.fc25 How reproducible: This bug happens from time to time(for now it has happened 2 times in a row with an hour interval Steps to Reproduce: 1. Launch KDE 2. Screen freezes and becomes unresponsive Actual results: Screen freezes one half goes black. More info: http://imgur.com/a/g6ZvN Expected results: KDE behaving as usual without any glitches or inconveniences. Additional info: I've created the following script as a quick fix to restart kwin.
It seems that `GhostDeco 2.0` was the culprit. For now i will close this bug report.
I am reopening this bug because it happened again on default settings and default theme.
Recently discovvered some segfaults: ``` [Fri Mar 10 09:42:59 2017] QDBusConnection[6209]: segfault at 7f1cac98baa0 ip 00007f1cc8b23f8d sp 00007f1caebd99c0 error 4 in libQt5Core.so.5.7.1[7f1cc88b3000+478000] [Fri Mar 10 09:42:59 2017] QDBusConnection[6221]: segfault at 7f619dac6aa0 ip 00007f61be0fff8d sp 00007f619f304940 error 4 in libQt5Core.so.5.7.1[7f61bde8f000+478000] [Fri Mar 10 09:42:59 2017] QDBusConnection[6270]: segfault at 7f2e98478aa0 ip 00007f2ec297bf8d sp 00007f2e994b5940 error 4 in libQt5Core.so.5.7.1[7f2ec270b000+478000] [Fri Mar 10 09:42:59 2017] sddm-greeter[5615]: segfault at 30 ip 00007fef77b41e10 sp 00007ffd40a49ef8 error 4 in libKF5CoreAddons.so.5.31.0[7fef77b0d000+90000] [Fri Mar 10 09:42:59 2017] Qt bearer threa[6272]: segfault at 7fe4e0155b38 ip 00007fe4fb19d581 sp 00007fe4db7fd950 error 4 in libQt5Core.so.5.7.1[7fe4faf57000+478000] [Fri Mar 10 09:42:59 2017] Pid 6174(Qt bearer threa) over core_pipe_limit [Fri Mar 10 09:42:59 2017] Skipping core dump [Fri Mar 10 09:42:59 2017] wlp2s0: deauthenticating from f4:cf:e2:36:19:eb by local choice (Reason: 3=DEAUTH_LEAVING) [Fri Mar 10 09:42:59 2017] Pid 6178(QDBusConnection) over core_pipe_limit [Fri Mar 10 09:42:59 2017] Skipping core dump [Fri Mar 10 09:42:59 2017] QDBusConnection[6199]: segfault at 7f4cc86e7aa0 ip 00007f4ce407ef8d sp 00007f4cca1349c0 error 4 in libQt5Core.so.5.7.1[7f4ce3e0e000+478000] [Fri Mar 10 09:42:59 2017] Pid 6168(QDBusConnection) over core_pipe_limit [Fri Mar 10 09:42:59 2017] Skipping core dump [Fri Mar 10 09:42:59 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [Fri Mar 10 09:42:59 2017] QDBusConnection[6218]: segfault at 7f3bfd6d9aa0 ip 00007f3c1dd12f8d sp 00007f3bfef17940 error 4 in libQt5Core.so.5.7.1[7f3c1daa2000+478000] ```
Probably worth reporting upstream to bugs.kde.org at this point. While we're at it, the coredump/backtraces are missing debuginfo, which may help investigating too. Offhand, these lines look problematic: [Fri Mar 10 09:42:59 2017] Pid 6174(Qt bearer threa) over core_pipe_limit [Fri Mar 10 09:42:59 2017] Pid 6178(QDBusConnection) over core_pipe_limit [Fri Mar 10 09:42:59 2017] Pid 6168(QDBusConnection) over core_pipe_limit And the segfaults you reference include sddm too, so I suspect there's more going on here than anything just kwin-related.
googling suggests core_pipe_limit is a rate-limiting feature for catching multiple crash dumps. So yeah, when things go bad on your system, it appears there are lots of crashes, not just kwin.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.