• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle









  • Heh. “Guy” has some interesting history. It originally referred to Guy Fawkes, because that was his name. Then it came to mean any person, gender neutral, then it became any man, now gendered, but the neutral definition never went away, so we have both meanings floating around still, but the original meaning, an effigy of Guy Fawkes, died.

    (I skipped a few steps in there because they’re not relevant between guy Fawkes and any person)



  • I really wanted Wayland to work for me. I just bought a new ASUS laptop (and ASUS has a great Linux compatibility track record, mind you!), 7th Gen Ryzen+Radeon, all AMD. I figured, let’s use Wayland on this one.

    I installed KDE Neon, updated the kernel (some stuff is broken on the LTS kernel, no big deal, easy fix), switched to the Wayland session, everything was fine…until I opened any chromium-based app. Crashed kwin, killed the session completely, it recovered, but in a new session. Switched to X11, everything works. Maybe if I grabbed a newer mesa from a PPA it would work, but:

    1. Crashing the window manager killing the session is awful and doesn’t happen in X11
    2. Chromium shouldn’t crash the compositor at all
    3. Even if it’s AMD’s new graphics drivers being buggy, that still shouldn’t kill the session!

    And I know, technically KDE could (and afaik, is) implement session management so that doesn’t happen. But to my knowledge, literally 0 WMs/DEs can recover the session after a compositor crash currently, and that’s a big deal.