package udisks 1.0.1-1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Alejandro Beltrán]

Binary package hint: udisks

It was happen when I was upgraded the Ubuntu 10.04 Beta 2 system.
The upgrade is not finished, and I didn't fix this problem with 'apt-get -f install'.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: udisks 1.0.1-1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 10 10:21:07 2010
ErrorMessage: problemas de dependencias - se deja sin configurar
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
MachineType: BenQ Joybook R53
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
SourcePackage: udisks
Title: package udisks 1.0.1-1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
dmi.bios.date: 08/18/2005
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 3A06
dmi.board.name: Joybook R53
dmi.board.vendor: BenQ
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: BenQ
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr3A06:bd08/18/2005:svnBenQ:pnJoybookR53:pvrRevisionA0:rvnBenQ:rnJoybookR53:rvrRev1.0:cvnBenQ:ct10:cvrRev1.0:
dmi.product.name: Joybook R53
dmi.product.version: Revision A0
dmi.sys.vendor: BenQ

[Martin Pitt (pitti)]

lzma: Encoder error: -2147467259

This doesn't come from udisks, rather looks like dpkg itself or apt.

[Jean-Baptiste Lallement (jibel)]

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 562312, 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.