package bluez 4.91-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bluez
I am not a computer professional, I am just a user - installed 11-04 yesterday, something didn't install correctly.
All I can hope to help with is send you what information the computer can gather itself =)
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: bluez 4.91-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelMo
Architecture: i386
Date: Fri Apr 22 10:56:32 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterestingModules: sco bnep l2cap btusb bluetooth
MachineType: ASUSTeK Computer INC. 1015PE
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
Title: package bluez 4.91-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to natty on 2011-04-22 (0 days ago)
dmi.bios.date: 07/01/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 1015PE
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:34 acl:0 sco:0 events:3 errors:0
TX bytes:12 acl:0 sco:0 commands:4 errors:0
Changed in bluez (Ubuntu): | |
status: | New → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 523896, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.