On 19/12/2024 08:47, Ralph Corderoy wrote:
I've been killing bitwarden via htop.
Or not!
It used to work.
Try ‘ps xf’ to see a forest (f) of trees of processes across (x) your
various terminals, etc. That should might show there's a hierarchy of
bitwardens where you're only killing the lower ones.
Actually, htop gives me much the same info, although it can be annoying
owing to the updates that move things around (yes I know that I can slow
that down).
If they all have the same process name then ‘killall bitwarden’ might
kill them all in one go. Another ‘ps xf’ would check.
There were around a dozen left and they all had different process names.
I laboriously killed all the bitwarden trees, and was duly informed that
bitwarden had updated, via the desktop. However, after a reboot,
bitwarden relaunched and I can see one tree in ps -xf:
2627 ? S 0:00 \_ /bin/sh /snap/bitwarden/128/bitwarden
--no-sandbox
2796 ? Sl 0:06 | \_ /snap/bitwarden/128/bitwarden-app
--no-sandbox
3105 ? S 0:00 | \_
/snap/bitwarden/128/bitwarden-app --type=zygote --no-zygote-sandbox
--no-sandbox
3428 ? Sl 0:00 | | \_
/snap/bitwarden/128/bitwarden-app --type=gpu-process --no-sandbox
--enable-crash-reporter=5e53878b-ebff-4d80-82b9-9ac33
3106 ? S 0:00 | \_
/snap/bitwarden/128/bitwarden-app --type=zygote --no-sandbox
3403 ? Sl 0:00 | \_
/snap/bitwarden/128/bitwarden-app --type=utility
--utility-sub-type=network.mojom.NetworkService --lang=en-GB --service-san
However, I still cannot launch the GUI from the desktop and I get the
same error as before in the console. After I killed the above tree I
tried to launch it again, so the problem is not so much about quitting
bitwarden, but actually being able to launch it correctly.
BTW. I cannot see how bitwarden is launched after rebooting, since it
is not in the Autostart area and I can find nothing in
/home/terry/.bashrc or /root/profile*. Are there any other mechanisms
to launch software on startup? If not, I assume that there is something
in the App that does it, but I can't see how.
--
Terry Coles
--
Next meeting: Online, Jitsi, Tuesday, 2025-01-07 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... https://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
