package dma 0.11-2 failed to install/upgrade: installed dma package post-installation script subprocess returned error exit status 128

[Markus Birth]

During upgrade on a Raspberry Pi 3 (armhf) from disco to eoan, the upgrade of dma failed.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: dma 0.11-2
ProcVersionSignature: Ubuntu 5.0.0-1025.26-raspi2 5.0.21
Uname: Linux 5.0.0-1025-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: armhf
Date: Tue Mar 3 01:44:46 2020
DuplicateSignature:
 package:dma:0.11-2
 Setting up dma (0.11-2) ...
 dpkg: error processing package dma (--configure):
  installed dma package post-installation script subprocess returned error exit status 128
ErrorMessage: installed dma package post-installation script subprocess returned error exit status 128
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt 1.9.4
SourcePackage: dma
Title: package dma 0.11-2 failed to install/upgrade: installed dma package post-installation script subprocess returned error exit status 128
UpgradeStatus: Upgraded to eoan on 2020-03-03 (0 days ago)
modified.conffile..etc.dma.auth.conf: [modified]
mtime.conffile..etc.dma.auth.conf: 2019-10-29T11:14:01.611576

[Launchpad Janitor (janitor)]

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

[intherye (intherye)]

Also happened for me when updating from 18.04 to 20.04 on a x64-VM (qemu/kvm).

I worked around by "apt remove dma", "apt install dma"

[Steve Dodd (anarchetic)]

I'm dealing with a very similar bug building containers with jammy beta. If there's an existing /etc/dma/dma.conf, I get the above error message. Oddly, attempting to strace or add too much debug to the .postinst or .config scripts makes the problem go away, which makes it seem like some sort of weird debconf bug/race?

[Steve Dodd (anarchetic)]

Ah, looks like upstream bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940219 is the answer to my problem..