package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1

[Daniel Axtens]

Hi,

I installed trousers on my Dell XPS 13, and the following error occurred:

Aug 06 12:03:45 linkitivity trousers[11173]: * Starting Trusted Computing daemon tcsd
Aug 06 12:03:45 linkitivity trousers[11173]: /etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator
Aug 06 12:03:45 linkitivity trousers[11173]: * TPM device owner for /dev/tpmrm0 is not 'tss', this can cause problems.
Aug 06 12:03:45 linkitivity tcsd[11196]: TCSD TDDL[11196]: TrouSerS ioctl: (25) Inappropriate ioctl for device
Aug 06 12:03:45 linkitivity tcsd[11196]: TCSD TDDL[11196]: TrouSerS Falling back to Read/Write device support.
Aug 06 12:03:45 linkitivity tcsd[11196]: TCSD TCS[11196]: TrouSerS ERROR: TCS GetCapability failed with result = 0x1e
Aug 06 12:03:45 linkitivity trousers[11173]: ...fail!
Aug 06 12:03:45 linkitivity systemd[1]: trousers.service: Control process exited, code=exited status=30
Aug 06 12:03:45 linkitivity systemd[1]: trousers.service: Failed with result 'exit-code'.
Aug 06 12:03:45 linkitivity systemd[1]: Failed to start LSB: starts tcsd.

The first problem in /etc/init.d/trousers is:

                if [ ! -e /dev/tpm* ]
                then
                        log_warning_msg "device driver not loaded, skipping."
                        exit 0
                fi

I have two devices that match /dev/tpm*: /dev/tpm0 and /dev/tpmrm0, and [ -e only works with one input. This doesn't cause the warning to fire, so it's purely a cosmetic warning.

The second warning seems to related to the ownership of /dev/tpmrm0:

# ls -l /dev/tpm*
crw------- 1 tss tss 10, 224 Aug 6 12:03 /dev/tpm0
crw------- 1 root root 253, 65536 Jul 27 19:50 /dev/tpmrm0

So it looks like /dev/tpm0 is set correctly but not /dev/tpmrm0.

Looking at the source, it seems that debian/trousers.udev contains only the following:

KERNEL=="tpm[0-9]*", MODE="0600", OWNER="tss", GROUP="tss"

I think per some reading online it needs to read something like this:

KERNEL=="tpmrm[0-9]*|tpm[0-9]*", MODE="0660", OWNER="tss", GROUP="tss"

Editing /lib/udev/rules.d/45-trousers.rules to include this line and running `udevadm trigger` makes the warning go away.

Finally, the whole thing fails with "ERROR: TCS GetCapability failed with result = 0x1e". This is apparently due to the presence of a TPM2 chip rather than the 1.2 chip that trousers understands.

I think trousers should print a loud warning in this case (and preferably a much more informative one!) but that it should not fail to configure the package.

This is Ubuntu 18.04, with:
trousers:
  Installed: 0.3.14+fixed1-1build1
  Candidate: 0.3.14+fixed1-1build1
  Version table:
 *** 0.3.14+fixed1-1build1 500
        500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: trousers 0.3.14+fixed1-1build1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libtspi1:amd64: Install
 libtpm-unseal1:amd64: Install
 trousers:amd64: Install
 tpm-tools:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Aug 6 12:03:45 2018
ErrorMessage: installed trousers package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2017-04-05 (487 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.2
SourcePackage: trousers
Title: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-04-30 (97 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.