obsolete conffiles not cleaned up on upgrade

[Michael Biebl]

Impact:

When upgrading to xenial from earlier releases, some files are left on the user's system. They are not used, but may otherwise be mistaken for being used by the user if they are attempting to fix a problem.

Regression potential:

Low to none, as the relevant files are not used, and are being removed when the updated version of Pulseaudio is installed. These files are already removed in yakkety and later.

Test case:

When updating from trusty to xenial, one will note the presence of the below listed files on the system. Updating from pulseaudio in xenial or pulseaudio in trusty to what is in xenial-proposed shoudl delete the listed files. The /etc/init.d/pulseaudio script should also be unregistered.

Original bug report:

The following files are marked obsolete after the upgrade to 16.04:

 /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
 /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
 /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
 /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

Those files should be cleaned up and the sysv init script properly deregistered.

[Luke Yelavich (themuso)]

Some of these files should be getting removed, as there are appropriate rm_conffile calls in pulseaudio.maintscript, which subsequently end up in the postinst script of the pulseaudio package. There are however some that are not being removed that should.

I'll look into why the files that should be removed are not being removed...

[Brian Murray (brian-murray)]

Hello Michael, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Luke Yelavich (themuso)]

I can verify that after upgrading from trusty with pulseaudio pre-installed, that the indicated files are still present. Once upgrading to pulseaudio in xenial-proposed, the indicated files are removed and the init script unregistered.

[Martin Pitt (pitti)]

The verification of the Stable Release Update for pulseaudio has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.1

---------------
pulseaudio (1:8.0-0ubuntu3.1) xenial; urgency=medium

  * debian/pulseaudio.maintscript: Bump versions for files that need to be
    removed as they are obsolete (LP: #1573296)
  * 0502-bluetooth-bluez5-bring-back-SCO-over-PCM-support.patch:
    - Remove patch hunk that set u->transport to NULL. At the time this
      code was written for 15.10, it was to prevent an assertion. Now with
      newer versions of pulse, the opposite is happening in some circumstances
      (LP: #1574324)

 -- Luke Yelavich <email address hidden> Thu, 03 Nov 2016 16:58:35 +1100

[Aaron Peromsik (aperomsik)]

pulseaudio was working fine for me in system mode until this update hit my machine today. Now I have no sound.