package usb-creator-kde 0.2.12 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zur?ck
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
usb-creator (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: usb-creator-kde
Release: Ubuntu 9.10 - Karmic Koala
Version: 0.2.12
Expecting: Clean install/
Happening:
> apt-get install -f
3 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0B Plattenplatz zusätzlich benutzt.
Richte usb-creator-kde ein (0.2.12) ...
dpkg (Unterprozess): kann installiertes post-installati
dpkg: Fehler beim Bearbeiten von usb-creator-kde (--configure):
Unterprozess installiertes post-installati
Fehler traten auf beim Bearbeiten von:
usb-creator-kde
E: Sub-process /usr/bin/dpkg returned an error code (1)
Additional comments:
Setting up kubuntu-desktop in a environment that was set up and updated from 9.04 to 9.10 in the past 24 hours did not want to set up correctly. This could be due to a freeze that occured during the setup process. I don't know which packets were affected at that time. However, even after using dpkg to configure the missing packages, this one remains broken. Deinstallation is also impossible due to broken deinstall scripts too.
Note that this computer has problems with its built in SATA/NIC/
ProblemType: Package
AptOrdering:
usb-creator-kde: Configure
okular-
userconfig: Configure
Architecture: i386
Date: Tue Feb 23 10:36:58 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: Unterprozess installiertes post-installati
NonfreeKernelMo
Package: usb-creator-kde 0.2.12
PackageArchitec
ProcVersionSign
SourcePackage: usb-creator
Title: package usb-creator-kde 0.2.12 failed to install/upgrade: Unterprozess installiertes post-installati
Uname: Linux 2.6.31-19-generic i686
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 512096, 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.