https://bugs.kde.org/show_bug.cgi?id=515550
--- Comment #6 from Zamundaaa <[email protected]> --- Okay, so one suspicious thing is this: > [ 115.096076] i915 0000:00:02.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe201, auth=1, DRM_IOCTL_DROP_MASTER > [ 115.096115] nvidia 0000:01:00.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe200, auth=1, DRM_IOCTL_DROP_MASTER right before KWin would normally turn off the screens before suspend. After wakeup, it does > [ 145.491052] i915 0000:00:02.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe201, auth=1, DRM_IOCTL_SET_MASTER > [ 145.491068] nvidia 0000:01:00.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe200, auth=1, DRM_IOCTL_SET_MASTER but only after KWin attempts to turn the display on again. I don't quite understand why systemd would do that, and it certainly doesn't do that on my PC. My first suspicion would be that lact is doing something weird, another possibility is that you have a service or something that causes this. The screens turning on when you press something on the keyboard is most likely because that just triggers a repaint, and makes KWin try again to turn the display(s) on. Can you try removing lact and check if it still happens then? -- You are receiving this mail because: You are watching all bug changes.
