package ubuntustudio-audio 0.52 failed to install/upgrade:

[badsc29]

package ubuntustudio-audio 0.52 failed to install/upgrade:

ProblemType: Package
Architecture: i386
Date: Fri Oct 23 09:21:22 2009
DistroRelease: Ubuntu 9.10
ErrorMessage:
 ErrorMessage: package ubuntustudio-audio is already installed and configured
LiveMediaBuild: Ubuntu-Studio 9.10 "Karmic Koala" - Release Candidate i386 (20091020.4)
NonfreeKernelModules: nvidia
Package: ubuntustudio-audio 0.52
ProcVersionSignature: Ubuntu 2.6.28-16.55-generic
SourcePackage: ubuntustudio-meta
Title: package ubuntustudio-audio 0.52 failed to install/upgrade:
Uname: Linux 2.6.28-16-generic i686

[James H Boyd (boydjhla)]

I am upgrading AMD64 version of Ububtu 9.04 to 9.10

[James H Boyd (boydjhla)]

Earlier in the processing of the upgrade the following two messages appeared:

Could not install '/var/cache/apt/archives/ubuntustudio-audio_0.64_amd64.deb'
package may not be in a working state
subprocess new pre-removal script returned error exit status 1

Could not install 'ubuntustudio-audio'
ubuntustudio-audio package may not be in a working state
package ubuntustudio-audio is already installed and configured

[Brian Murray (brian-murray)]

This was incorrectly marked as a duplicate of another bug. From VarLogDistupgradeApttermlog.gz we see:

Traceback (most recent call last):^M
  File "/usr/share/ubuntustudio-audio/rtprio.py", line 18, in <module>^M
    rtprio.rm_setting()^M
  File "/usr/lib/python2.6/dist-packages/changesettings.py", line 80, in rm_setting^M
    self.rm_list.remove(self.remove_string)^M
ValueError: list.remove(x): x not in list^M
dpkg: error processing /media/cdrom0//pool/universe/u/ubuntustudio-meta/ubuntustudio-audio_0.63_i386.deb (--unpack):^M
 subprocess new pre-removal script returned error exit status 1^M

[Launchpad Janitor (janitor)]

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

[Ross Gammon (rosco2)]

Ubuntu Studio 9.10 is no longer supported. I have tested upgrades for the last three releases, and could not reproduce this issue. Therefore I am setting the status to invalid.

If you can confirm that the bug still occurs for a current release, please reopen, or resubmit a new bug.