Ubuntu
bluez package

package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Bug #399543 reported by Paul Hummer on 2009-07-15

This bug report is a duplicate of: Bug #399482: Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later fails. Edit Remove

62

This bug affects 13 people

Affects		Status	Importance	Assigned to	Milestone
	bluez (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: bluez

On an `apt-get update; apt-get upgrade` this happened. I haven't made any customizations, etc. so I have no idea where this came from.

Description: Ubuntu karmic (development branch)
Release: 9.10

bluez:
  Installed: 4.45-0ubuntu2
  Candidate: 4.45-0ubuntu3
  Version table:
     4.45-0ubuntu3 0
        500 http://us.archive.ubuntu.com karmic/main Packages
*** 4.45-0ubuntu2 0
        100 /var/lib/dpkg/status

ProblemType: Package
Architecture: amd64
Date: Tue Jul 14 18:43:08 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess new pre-removal script returned error exit status 1
Package: bluez 4.45-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
SourcePackage: bluez
Title: package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Uname: Linux 2.6.31-2-generic x86_64

Tags:

Revision history for this message

Paul Hummer (rockstar) wrote on 2009-07-15:

#1

AptOrdering.txt Edit (609 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (70.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (38.3 KiB, application/x-gzip)

Revision history for this message

3vi1 (launchpad-net-eternaldusk) wrote on 2009-07-15:

#2

I see exactly the same thing trying to upgrade to bluez_4.45-0ubuntu3_amd64.deb

Revision history for this message

Don Forigua (ingforigua) wrote on 2009-07-15:

#3

I have this problem when i trying to upgrade to bluez_4.45-0ubuntu1 on karmic koala i386

Revision history for this message

bobya (bobya) wrote on 2009-07-15:

#4

I also had this problem , what i did to solve it is that I edited the /etc/init.d/bluetooth startup script and just commented the stop line and added "exit 0".
After this change the installation process had passed.
I checked the new startup script and there was another solution made by the package team "pkill -TERM bluetoothd || true" this should always return true :)

Revision history for this message

Manuel Muradás (dieresys) wrote on 2009-07-15:

#5

I think this was fixed in #399482.

Revision history for this message

Max Bowsher (maxb) wrote on 2009-07-15:

#6

Bug 399482 has fixed it for the future. Affected people with the bad 4.45-0ubuntu1 or -0ubuntu2 packages install are going to have to manually work around this by editing the initscript, unless a prerm failed-upgrade handler is added to the package to catch this and work around it automatically.

Niall Creech (sevenmachines-deactivatedaccount) on 2009-07-15

Changed in bluez (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #399482 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.