[Bug 1780433] Re: Installing packages doesn't always remove obsolete configuration files

[Jarno Suni]

I have the same problem in Ubuntu 18.04. I installed pulseaudio 12.2
from PulseEffects PPA and later downgraded using apt. Then starting
pulseaudio daemon by command start-pulseaudio-x11 did not work. Removing
/etc/pulse/client.conf.d/00-disable-autospawn.conf helped.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dpkg in Ubuntu.
https://bugs.launchpad.net/bugs/1780433

Title:
  Installing packages doesn't always remove obsolete configuration files

Status in dpkg package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.10 dev with dpkg 1.19.0.5ubuntu3 and on
  upgrading/downgrading pulseaudio (mainly libpulse0) I noticed that
  configuration files were not always be removed correctly. For example
  the package libpulse0 1:11.1-1ubuntu8 doesn't contain the directory
  /etc/pulse/client.conf.d while the version 1:12.0-1ubuntu1 does
  contain it with the file 00-disable-autospawn.conf in it.

  On the first pulseaudio upgrade from version 11.1 to 12.0 by executing
  "apt-get download libpulse0:amd64 libpulse0:i386 libpulsedsp:amd64
  pulseaudio-utils:amd64 pulseaudio:amd64" and "dpkg -i *.deb" (both as
  root) all went fine and the directory /etc/pulse/client.conf.d with
  the file 00-disable-autospawn.conf was successfully created. However,
  on pinning those pulseaudio packages to version 11.1, deleting the old
  downloaded .deb packages and executing both commands above again I get
  the warning "dpkg: warning: unable to delete old directory
  '/etc/pulse/client.conf.d': Directory not empty" in the installation
  output and /etc/pulse/client.conf.d with 00-disable-autospawn.conf in
  it still exists.

  
  If I remember correctly at some point on upgrading pulseaudio to version 12.0 again I also noticed that the directory /etc/pulse/client.conf.d was existing but the file 00-disable-autospawn.conf in it was missing but I don't remember how I got into this state (maybe some sort of follow-up error or I messed just somehow something up on testing).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1780433/+subscriptions