mickee@mickee-H61H2-TI:~$ dpkg -l | grep boinc
ii boinc 8.2.9+dfsg-1build1 all metapackage for the BOINC client and the manager
ii boinc-client 8.2.9+dfsg-1build1 amd64 core client for the BOINC distributed computing infrastructure
ii boinc-manager 8.2.9+dfsg-1build1 amd64 GUI to control and monitor the BOINC core client
ii libboinc7t64:amd64 8.2.9+dfsg-1build1 amd64 libraries of BOINC the client depends on
âboinctasks-jsâ is not a package, itâs a program thatâs part of a package. Use which boinctasks-js to find the fully qualified name of that file then use dpkg with the â-Sâ option and the full name you got from âwhichâ. (Alternatively use command line substitution to do both steps in one: dpkg -S $(which boinctasks-js)). That will give you the name of the package you need to remove to get rid of boinctasks-js. Be aware that this is likely to break boinc.
Before you start suspecting PAM, sudo, or cosmic rays for breaking âaptâ - donât worry, your pack mgr is completely innocent here!
The reason âdpkg -lâ and âaptâ canât find âboinctasks-jsâ is almost certainly because **it was installed as a Snap package**, not an APT/deb package.
If you run âdpkg -S $(which boinctasks-js)â, it will likely just return âno path found matching pattern /snap/bin/âŠâ, leading you further down the rabbit hole.
Try checking your Snaps instead:
1- Check if its managed by snap - âsnap list | grep boincâ
2- If it shows up there, remove it with - âsudo snap remove boinctasks-jsâ
And if âsnap listâ doesnât show it either, check âwhich boinctasks-jsâ or âreadlink /proc/$(pgrep -o boinctasks-js)/exeâ to see if itâs an appImage or manual install sitting in â/optâ or your home directoryâŠ
You want to use the âpurge option with that, snaps do automatically take a compressed backup of the user data when you remove them (in case you re-install the snap at a later point) purging prevents that.