• chuckleslord@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      11 months ago

      That’s so dumb, but okay.

      Edit: dumb that using the shortcut to open the task manager doesn’t interrupt the system. That’s what ctrl-alt-del did before windows 8 or whenever, open the task manager regardless of what was happening. Now I have to use that annoying lock-screen menu to open the task manager to kill processes if things are locked up. Didn’t know that, horribly unintuitive

        • chuckleslord@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          11 months ago

          If your computer is locked up, you have to use ctrl-alt-del, with its menu of options including the task manager, in order to interrupt the current processes locking up the system.

          Using ctrl-shift-esc launches the task manager program without a system interrupt, meaning it won’t unlock the computer. Which is dumb, because why else would I be opening the task manager other than to interrupt some out-of-control process? I guess you could be using it to monitor or something else, but that’s what I’m used to opening the task manager to be doing. I didn’t even realize this until this comment.

          • IronKrill@lemmy.ca
            link
            fedilink
            arrow-up
            3
            ·
            11 months ago

            I check ram and cpu usage and change startup apps or task priority just as much as I need to force quit.

          • force@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            11 months ago

            then just press ctrl alt del if you want a system interrupt??? there’s a reason they have bindings for both. it’s not much harder, the task manager doesn’t exist solely for killing some program that won’t respond.

    • jaybone@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      11 months ago

      I assume this terminology originally referred to an actual interrupt handled by a kernel interrupt handler, and half of the people in this thread have no idea what that means.