I can also only spot in the terminal log that someone (I guess you)
already looked for processes to then kill the script. It seems that this
is only by accident/chance the samba package that was upgrading at the
time and could be anything else.
I see int he log that the upgrade was already in the removal stage after
the upgrades. Which is odd as you aborted a configure step which usually
doesn't happen in this stage.
I'm puzzled and unsure how to help with just the logs :-/
Was this resolved on a retry or was it reproducible and needed to be debugged
further?
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946402
Title:
package samba-common 2:4.11.6+dfsg-0ubuntu1.10 failed to
install/upgrade: installed samba-common package post-installation
script subprocess was killed by signal (Killed)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1946402/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
