[Solved by going to X11]

I am working with my Debian 12 system and suddenly the whole screen goes blank and comes right back. I am not sure what triggers it, it seems to happen when I am exiting a program, I think when It comes back any program I had running is gone now. This is very intermittent and does not happen very often.

Here as a start have a neofetch:

OS: Debian GNU/Linux 12 (bookworm) x86_64

Host: VivoBook_ASUSLaptop S5402ZA_S5402ZA 1.0

Kernel: 6.1.0-11-amd64

Uptime: 12 hours, 2 mins

Packages: 2361 (dpkg)

Shell: bash 5.2.15

Resolution: 2880x1800

DE: Plasma 5.27.5

WM: kwin

WM Theme: plastik

Theme: [Plasma], Breeze [GTK2/3]

Icons: [Plasma], breeze-dark [GTK2/3]

Terminal: konsole

Terminal Font: Hack 19

CPU: 12th Gen Intel i7-12700H (20) @ 4.600GHz

GPU: Intel Alder Lake-P Memory: 3406MiB / 11577MiB

I did journalctl -b - there is a crazy amount of detail in there.

If there is anything specific I can do, please let me know - I am more than a noob, but a lot of the time I only know just enough to be dangerous.

Thanks!

  • WasPentaliveOP
    2·
    1 year ago

    Here is a clue perhaps from Journalctl:

    Aug 11 17:25:17 adam plasmashell[14949]: This plugin supports grabbing the mouse only for popup windows
Aug 11 17:25:18 adam plasmashell[14949]: This plugin supports grabbing the mouse only for popup windows
Aug 11 17:25:18 adam plasmashell[14949]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 11 17:25:18 adam plasmashell[14949]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 11 17:25:19 adam plasmashell[14949]: QWaylandShmBuffer: mmap failed (Invalid argument)
Aug 11 17:25:23 adam kwin_wayland_wrapper[2483]: error in client communication (pid 12396)
Aug 11 17:25:23 adam plasmashell[12396]: wl_display@1: error 0: invalid object 213
Aug 11 17:25:23 adam plasmashell[12396]: The Wayland connection experienced a fatal error: Invalid argum>
Aug 11 17:25:23 adam plasmashell[12396]: The Wayland connection experienced a fatal error: Invalid argum>
Aug 11 17:25:23 adam systemd[2384]: plasma-plasmashell.service: Main process exited, code=exited, status>
Aug 11 17:25:23 adam systemd[2384]: plasma-plasmashell.service: Failed with result 'exit-code'.
Aug 11 17:25:23 adam systemd[2384]: plasma-plasmashell.service: Consumed 1min 59.306s CPU time.
Aug 11 17:25:24 adam systemd[2384]: plasma-plasmashell.service: Scheduled restart job, restart counter i>
Aug 11 17:25:24 adam systemd[2384]: Stopped plasma-plasmashell.service - KDE Plasma Workspace.
Aug 11 17:25:24 adam systemd[2384]: plasma-plasmashell.service: Consumed 1min 59.306s CPU time.
Aug 11 17:25:24 adam systemd[2384]: Starting plasma-plasmashell.service - KDE Plasma Workspace...
lines 907-931/975 94%
    • kopper [they/them]@lemmy.blahaj.zoneEnglish
      1·
      1 year ago
      > Aug 11 17:25:23 adam kwin_wayland_wrapper[2483]: error in client communication (pid 12396)
> Aug 11 17:25:23 adam plasmashell[12396]: wl_display@1: error 0: invalid object 213
> Aug 11 17:25:23 adam plasmashell[12396]: The Wayland connection experienced a fatal error: Invalid argum>
> Aug 11 17:25:23 adam plasmashell[12396]: The Wayland connection experienced a fatal error: Invalid argum>
> Aug 11 17:25:23 adam systemd[2384]: plasma-plasmashell.service: Main process exited, code=exited, status>
> Aug 11 17:25:23 adam systemd[2384]: plasma-plasmashell.service: Failed with result 'exit-code'.

      KDE’s crashing and getting started back up. Due to how Wayland works this will also take down most programs you were running.

      Why is KDE crashing? No idea. You may have better luck with Xorg if you aren’t reliant on any Wayland niceties (proper multiple monitor support, for example)

      edit: https://bugs.kde.org/show_bug.cgi?id=447717 looks like a candidate, but there isn’t enough detail to make sure

      • WasPentaliveOP
        1·
        1 year ago

        I have rebooted into X11, we will see if there are any more instances.