package bluez 4.96-0ubuntu2 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 2 zurück
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
updated today.
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-8-generic i686
Architecture: i386
Date: Wed Aug 10 20:05:27 2011
Df:
Dateisystem 1K‐Blöcke Benutzt Verfügbar Ben% Eingehängt auf
/dev/sda1 124891036 36069696 82477152 31% /
sysfs 124891036 36069696 82477152 31% /sys
udev 124891036 36069696 82477152 31% /dev
devpts 124891036 36069696 82477152 31% /dev/pts
ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 2 zurück
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150/N210/N220
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
Title: package bluez 4.96-0ubuntu2 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 2 zurück
UpgradeStatus: Upgraded to oneiric on 2011-08-08 (3 days ago)
dmi.bios.date: 01/29/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 06JI.M053.
dmi.board.
dmi.board.name: N150/N210/N220
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: N150/N210/N220
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 2C:81:58:CB:75:A1 ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:2328 acl:0 sco:0 events:87 errors:0
TX bytes:1847 acl:0 sco:0 commands:87 errors:0
This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.