this post was submitted on 29 Oct 2024
763 points (94.8% liked)

linuxmemes

21273 readers
1126 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     

    Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] Zozano@lemy.lol 2 points 2 weeks ago (2 children)

    Is there a Wayland equivalent?

    [–] antifa@infosec.pub 3 points 2 weeks ago (1 children)

    I dunno; I sadly can't use Wayland yet bc I have Nvidia

    [–] Zozano@lemy.lol 8 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    I don't know if you heard, but the Nvidia issues are solved (mostly).

    The issue most people had was with Explicit Sync, which was patched in the proprietary Nvidia driver 555 which is upstream on most distros.

    [–] antifa@infosec.pub 2 points 2 weeks ago

    Good to know; I'll check it out!

    [–] seadoo@lemmy.world 1 points 2 weeks ago (1 children)

    idk if this could be subjective, but what do you mean by upstream here? Does that mean it’s included in most distros?

    [–] Zozano@lemy.lol 1 points 2 weeks ago

    Yep. Most modern distros should be providing the 555 driver by now.

    [–] fushuan@lemm.ee 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

    Open the process list in your system monitor of choice, right click, signal, sigkill.

    You can also open a monitor and use top or any variant to detect the process number and manually kill -KILL number

    [–] Zozano@lemy.lol 2 points 2 weeks ago (2 children)

    I really want the convenience of binding xkill to a key, which I can use to double tap programs like the undead zombie they've become.

    [–] fushuan@lemm.ee 4 points 2 weeks ago (1 children)

    Dunno, create a script that uses a program to get the process number of the current active window or the window the mouse is hovering, and then kill that? Bind that script inor a key with whatever program and voilá.

    It's more involved sure but there's your option.

    [–] Zozano@lemy.lol 2 points 2 weeks ago (2 children)

    Great idea, now I just need to know how to do that.

    [–] Hawk@lemmynsfw.com 2 points 2 weeks ago

    What's your desktop environment? I'm pretty sure hyperland and sway will give a json output of open Windows.

    You could parse that with jq and pipe it into fzf or dmenu?

    Not quite the same as the clicking but probably just as quick.

    [–] fushuan@lemm.ee 1 points 2 weeks ago

    Get learning lol. I know that there's some command line program that gives process info on mouse hover and then that can be parsed with awk to get the pid, then pipe that again into kill -kill. Then use xbindkeys or whatever keybindings program to bind that script to a key.

    Tbh. For involved stuff like this chatgpt will help you more than stackoverflow.