• gamermanh@lemmy.dbzer0.comEnglish
      0·
      2 days ago

      One time I was playing modded Skyrim when it froze/crashed at the loading screen

      So I summon task manager, it hides behind the frozen game. I alt+tab and start blind keying to Skyrim to end it, been here hundreds of times, but nothing happens and the Skyrim world music STARTS???!!!

      ALT+TAB to see TM and Skyrim both reporting non-responsive. Tab to Skyrim and press w, clearly hear character moving and reacting to my input

      Try again to end process via ALT+F4, No dice. Try via TM, still unresponsive

      I had to reboot my PC with a hard power button press that time and I still don’t fully understand what the FUCK happened

      • ArxCyberwolf@lemmy.ca
        0·
        2 days ago

        New Vegas does the same thing, hiding Task Manager behind itself when it crashes. I found a workaround by using Ctrl+Alt+Del, clicking to make the cursor appear, and then pressing the Windows key which makes the taskbar appear. Then the game window can be closed from the taskbar.

  • Demdaru@lemmy.world
    0·
    3 days ago

    As a windows user WIN+R -> CMD -> TASKKILL /F /T /IM “<appname>*”

    … I use it too much. Appa often block my screen :|

  • archonet@lemy.lolEnglish
    0·
    3 days ago

    SIGTERM: stop that.

    SIGKILL: That was not a request.

    Case power button: listen here you little shit

    • prole@lemmy.blahaj.zone
      0·
      3 days ago

      As someone who’s relatively new to Linux, anyone want to explain what these lines would do? I’m aware of KILL, but dunno what the ‘-9’ refers to. Not familiar with sysrq-trigger

      • BougieBirdie@lemmy.blahaj.zoneEnglish
        0·
        2 days ago

        The kill command allows you to specify which type of kill signal you want to send. -9 sends signal 9 or SIGKILL, and we’re sending it to pid 1.

        That would force kill systemd, which I just have to assume will send your computer to a crashing halt.

        The echo command is writing "c" to a file at /proc/sysrq-trigger which I don’t really know how it works but this suggests you’ll “crash the system without first unmounting file systems or syncing disks attached to the system.”

        I haven’t installed fuck so I’m not sure how that works

  • RegalPotoo@lemmy.worldEnglish
    0·
    3 days ago

    Meanwhile, a Linux user wipes blood off a sledgehammer with “SIGKILL” written on the handle

      • RegalPotoo@lemmy.worldEnglish
        0·
        3 days ago

        In the immortal words of Monzy:

        I pull out my keyboard / and I pull out my gloc / and I dismount your girl / and I mount slash proc / cos I’ve got your pid / and the bottom line / is you best not front / or its kill dash nine

      • finley@lemm.eeEnglish
        0·
        3 days ago

        Lol, tell that to Xorg.

        130% and it doesn’t care about your kills or killalls or pkills or SIGKILLs…. It’s just gonna go, no matter what, until you shut the fucker down by unplugging it.

        Sometimes you’ve just got a process that just won’t listen to commands.

        Thants when you have to KILL the process.

        • PlexSheep@infosec.pub
          0·
          3 days ago

          Ig you sigkill a process, that process will no longer get CPU time, as far as I know. So if it didn’t work, you shot the wrong thing.