Session crash <3

  • superkret@feddit.org
    0·
    9 days ago

    If those steps (with no thinking or decision involved) fix the issue, then why the hell won’t the system execute those commands automatically?

    • qjkxbmwvz@startrek.website
      0·
      9 days ago

      IIRC chvt is a privileged command, which makes sense (if an unprivileged user could execute this command they could effectively brick the computer for a local user).

      That said, my understanding is that modern DE’s are given a lot of access, so presumably chvt is allowed (and in this case, is required because as others mentioned, password is required). So the only other option is to fail unlocked, which is all kinds of Bad.

    • sergiu@lemmy.world
      0·
      9 days ago

      I’ve had this happen to me a few times after waking up from sleep, I believe. Those steps did fix the issue for me.

  • penquin@lemm.ee
    0·
    9 days ago

    I hate this one. It’s so fucking random and I have never had a good answer as what causes it. I’ve found that a reboot fixes it. It usually happened after a big upgrade where you need to reboot. That’s the only solution I’ve had for it.

    • SqueakyBeaver@lemmy.blahaj.zone
      0·
      9 days ago

      I have never seen this error and don’t know the cause

      However, based on when it happens to you, it could be some weird caches or config files got overwritten and something did not like it. I know I’ve often had to delete plasma cache because something screwed up.

    • CanaryWhiskey@lemmy.worldOP
      0·
      9 days ago

      I’m hoping it’s fixed in later versions of Plasma. I’m on the LTS Debian release so bugs like these are to be expected :/ This aside Plasma is my favorite DE but I may switch to MATE due to nonsense like this.