package open-vm-tools-desktop (not installed) failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debhelper (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
open-vm-tools (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Test Case:
1. Install open-vm-
2. Uninstall open-vm-
(Lecture de la base de données... 311688 fichiers et répertoires déjà installés.)
Suppression de open-vm-
Failed to stop run-vmblockx2df
[1mdpkg:[0m erreur de traitement du paquet open-vm-
le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 5
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: open-vm-
ProcVersionSign
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
Date: Wed Aug 23 09:58:14 2017
ErrorMessage: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 5
InstallationDate: Installed on 2013-09-03 (1450 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3
PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
RelatedPackageV
dpkg 1.18.24ubuntu1
apt 1.5~beta1
SourcePackage: open-vm-tools
Title: package open-vm-
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Changed in open-vm-tools (Ubuntu): | |
status: | New → Won't Fix |
Fail is from ./open- vm-tools- desktop. prerm vm-tools- desktop. prerm remove *vmusr| vmware- user) x2dfuse. mount use.mount use.mount: Unit run-vmblockx2df use.mount not loaded.
+ ./open-
+ pkill -USR1 -f (vmtoolsd.
+ true
+ [ -d /run/systemd/system ]
+ deb-systemd-invoke stop run-vmblock\
+ [ -d /run/systemd/system ]
+ [ remove = remove ]
+ deb-systemd-invoke stop run-vmblockx2df
Failed to stop run-vmblockx2df
That is actually by: start/10. 7.2ubuntu2
deb-systemd- invoke stop run-vmblock\ x2dfuse. mount >/dev/null
# Automatically added by dh_systemd_
if [ -d /run/systemd/system ] && [ "$1" = remove ]; then
fi
# End automatically added section
If e.g. installe din a container the modprobe fails anyway and it can't fuse.
There might be other reasons for the service to fail that are "ok" just like this.
Further more it seems "ok" to not start, see the || true start/10. 7.2ubuntu2
deb-systemd- invoke start run-vmblock\ x2dfuse. mount >/dev/null || true
# Automatically added by dh_systemd_
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
fi
# End automatically added section
I wonder if it would be right to generate also the stop with a || true.
Maybe not as simple as that, but kind of a
1. stop it (ignore errors)
2. if not running, then all ok
3. only if after stop it is still running it is an error (e.g. can't remove while running)
But that is a generic thing so it should be filed to debhelper as well