Welcome to the new home of "This Week in Plasma"! No longer is it a private personal thing on my (Nate Graham's) blog, but now it's a weekly series hosted here on KDE's infrastructure, open to anyone's participation and contribution! I'll remain the editor-in-chief for now, and welcome contributions via direct push to the relevant merge request on invent.kde.org. And after a post is published, if you find a typo or broken link, feel free to just fix it.
  • Björn Tantau
    25•2 months ago

    But what if the OOM notification daemon gets killed by the OOM killer?

    • Czele
      4•2 months ago

      It doesnt. Instead daemon terminates whole Linux

    • @[email protected]English
      4•1 month ago

      The OOM killer always, invariably starts off with killing the display server. Any side effects such as “the notification daemon loses its connection and closes” or “every single thing that you were working on loses its connection and closes” is incidental.

      • @[email protected]
        1•1 month ago

        i will never stop wanting to commit severe crime every time i try to see what’s using the processor and every single fucking system monitor tool just says it’s xorg

        YES THANK YOU VERY USEFUL GOOD

        • @[email protected]English
          1•1 month ago

          At least Windows has more precise monitoring, it will tell you whether the process is “Windows Telemetry” or “SVCHOST.EXE”.