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

Bug #1712735 reported by Jean-Baptiste Lallement
6
This bug affects 1 person
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-tools-desktop
2. Uninstall open-vm-tools-desktop

(Lecture de la base de données... 311688 fichiers et répertoires déjà installés.)
Suppression de open-vm-tools-desktop (2:10.1.10-1) ...
Failed to stop run-vmblockx2dfuse.mount: Unit run-vmblockx2dfuse.mount not loaded.
dpkg: erreur de traitement du paquet open-vm-tools-desktop (--remove) :
 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-tools-desktop (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
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
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5~beta1
SourcePackage: open-vm-tools
Title: 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
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Fail is from ./open-vm-tools-desktop.prerm
+ ./open-vm-tools-desktop.prerm remove
+ pkill -USR1 -f (vmtoolsd.*vmusr|vmware-user)
+ true
+ [ -d /run/systemd/system ]
+ deb-systemd-invoke stop run-vmblock\x2dfuse.mount
+ [ -d /run/systemd/system ]
+ [ remove = remove ]
+ deb-systemd-invoke stop run-vmblockx2dfuse.mount
Failed to stop run-vmblockx2dfuse.mount: Unit run-vmblockx2dfuse.mount not loaded.

That is actually by:
# Automatically added by dh_systemd_start/10.7.2ubuntu2
if [ -d /run/systemd/system ] && [ "$1" = remove ]; then
        deb-systemd-invoke stop run-vmblock\x2dfuse.mount >/dev/null
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
# Automatically added by dh_systemd_start/10.7.2ubuntu2
if [ -d /run/systemd/system ]; then
        systemctl --system daemon-reload >/dev/null || true
        deb-systemd-invoke start run-vmblock\x2dfuse.mount >/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

Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

In a bionic LXC container, I get an error message on install but it seems to complete, and uninstallation works without issue:

triage-bionic+18.04:~$ sudo apt-get install open-vm-tools-desktop
...
Setting up libgtkmm-3.0-1v5:amd64 (3.22.2-2) ...
Setting up open-vm-tools-desktop (2:11.0.5-4ubuntu0.18.04.1) ...
modprobe: FATAL: Module fuse not found in directory /lib/modules/5.4.0-100-generic
Created symlink /etc/systemd/system/multi-user.target.wants/run-vmblock\x2dfuse.mount → /lib/systemd/system/run-vmblock\x2dfuse.mount.
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
triage-bionic+18.04:~$ sudo apt-get remove open-vm-tools-desktop
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libatkmm-1.6-1v5 libcairomm-1.0-1v5 libegl-mesa0 libegl1 libegl1-mesa libgbm1 libglibmm-2.4-1v5
  libgtkmm-3.0-1v5 libpangomm-1.4-1v5 libsasl2-modules libsigc++-2.0-0v5 libwayland-server0 libxatracker2
  libxcb-xfixes0 python3-debconf xserver-xorg-core xserver-xorg-video-vmware
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  open-vm-tools-desktop
0 upgraded, 0 newly installed, 1 to remove and 118 not upgraded.
After this operation, 509 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 98729 files and directories currently installed.)
Removing open-vm-tools-desktop (2:11.0.5-4ubuntu0.18.04.1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
triage-bionic+18.04:~$

I notice there are older bug reports about installation failures caught by apport, but none affecting bionic or newer. Since this is filed against a version of Ubuntu no longer actively supported, I'm going to close this report out. If the issue still presents itself on newer Ubuntu's please file a new bug report with the corresponding log and config files.

Bryce Harrington (bryce)
Changed in open-vm-tools (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.