package openclipart-png 0.18+dfsg-8 failed to install/upgrade:
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openclipart (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: openclipart
maybe a dupe of #311656 but my issue happened on upgrading to karmic RC
I don't know what happened, but the whole upgrade process went wrong.
In the end I had lots of these messages:
This is normally a bug in some application using the D-Bus library.
process 30582: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 278.
This is normally a bug in some application using the D-Bus library.
then when I killed
3:2009/10/26 00-28-25:
3:2009/10/26 00-28-25:
the installer stoped and I was lost midst the installation.
So I guess the whole system is unclean upgraded
ProblemType: Package
Architecture: i386
Date: Sun Oct 25 23:30:05 2009
Dependencies:
DistroRelease: Ubuntu 9.10
ErrorMessage:
ErrorMessage: failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during `./usr/
Package: openclipart-png 0.18+dfsg-8
PackageArchitec
ProcVersionSign
SourcePackage: openclipart
Title: package openclipart-png 0.18+dfsg-8 failed to install/upgrade:
Uname: Linux 2.6.31-14-generic i686
Looking at the attached dpkg-log, the following line shows the following reason for this problem:
dpkg: error processing /var/cache/ apt/archives/ openclipart- png_0.18+ dfsg-8_ all.deb (--unpack): share/openclipa rt/png/ signs_and_ symbols/ flags/europe/ spain/spain_ basque. png': No space left on device
failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during `./usr/
"no space left on device" means that simply the disk ran out of space here, I don't think this is a problem of the package itself.
Therefore I am closing this as duplicate of bug 312491 where the error message is discussed, for now please try to make more space available on your harddrive and then try again.
If you think there is a problem with too much space usage somewhere, please create a separate bug report that provides the relevant information.
See also Bug #312491 which discusses improving the error message in this case.