Ubuntu
xulrunner-1.9 package

xul-runner crash on update

Bug #365409 reported by hama on 2009-04-23

This bug report is a duplicate of: Bug #312491: Out-of-disk-space is not reported to the user when installing/updating packages fails. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xulrunner-1.9 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: xulrunner-1.9

Ends up with this:

E: /var/cache/apt/archives/xulrunner-1.9_1.9.0.9+nobinonly-0ubuntu0.8.10.1_i386.deb: misslyckades i buffer_write(handtag) (10, ret=-1)

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/xulrunner-1.9.0.9/components/nsXmlRpcClient.js"
Package: xulrunner-1.9 1.9.0.8+nobinonly-0ubuntu0.8.10.1
SourcePackage: xulrunner-1.9
Title: package xulrunner-1.9 1.9.0.8+nobinonly-0ubuntu0.8.10.1 failed to install/upgrade: misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/xulrunner-1.9.0.9/components/nsXmlRpcClient.js"
Uname: Linux 2.6.27-8-eeepc i686

Tags:

Revision history for this message

hama (sy-marie-hss1910) wrote on 2009-04-23:

Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (47.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Dominik Stadler (dominik-stadler) wrote on 2009-11-22:

Looking at the attached dpkg-log, the following line shows the following reason for this problem:

dpkg: fel vid hantering av /var/cache/apt/archives/xulrunner-1.9_1.9.0.9+nobinonly-0ubuntu0.8.10.1_i386.deb (--unpack):
misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/xulrunner-1.9.0.9/components/nsXmlRpcClient.js": No space left on device

"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 but rather shortage of general disk space is the cause of this problem.

Therefore I am closing this as duplicate of bug 312491 where improving the error message display is discussed, for now please try to make more space available on your harddrive and then try again.