Kory@lemmy.ml to linuxmemes@lemmy.world · 3 months agoTerminating a processlemmy.mlimagemessage-square95fedilinkarrow-up1805arrow-down144file-text
arrow-up1761arrow-down1imageTerminating a processlemmy.mlKory@lemmy.ml to linuxmemes@lemmy.world · 3 months agomessage-square95fedilinkfile-text
minus-squareantifa@infosec.publinkfedilinkarrow-up3·3 months agoI dunno; I sadly can’t use Wayland yet bc I have Nvidia
minus-squareZozano@lemy.lollinkfedilinkEnglisharrow-up8·edit-23 months agoI 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.
minus-squareseadoo@lemmy.worldlinkfedilinkarrow-up1·3 months agoidk if this could be subjective, but what do you mean by upstream here? Does that mean it’s included in most distros?
minus-squareZozano@lemy.lollinkfedilinkEnglisharrow-up1·3 months agoYep. Most modern distros should be providing the 555 driver by now.
minus-squareFushuan [he/him]@lemm.eelinkfedilinkEnglisharrow-up1·edit-23 months agoOpen 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
minus-squareZozano@lemy.lollinkfedilinkEnglisharrow-up2·3 months agoI 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.
minus-squareFushuan [he/him]@lemm.eelinkfedilinkEnglisharrow-up4·3 months agoDunno, 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.
minus-squareZozano@lemy.lollinkfedilinkEnglisharrow-up2·3 months agoGreat idea, now I just need to know how to do that.
minus-squareHawk@lemmynsfw.comlinkfedilinkarrow-up2·3 months agoWhat’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.
minus-squareZozano@lemy.lollinkfedilinkEnglisharrow-up1·3 months agoxkill isn’t a function of Wayland.
Is there a Wayland equivalent?
I dunno; I sadly can’t use Wayland yet bc I have Nvidia
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.
Good to know; I’ll check it out!
idk if this could be subjective, but what do you mean by upstream here? Does that mean it’s included in most distros?
Yep. Most modern distros should be providing the 555 driver by now.
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 numberI 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.
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.
Great idea, now I just need to know how to do that.
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.
deleted by creator
xkill isn’t a function of Wayland.