Bug#245861: openoffice.org: setup fails with "not enough space..." -- no largefile support
Package: openoffice.org
Version: 1.1.1-2
Severity: grave
Justification: renders package unusable
I wiped out my 1.0.3 files and .sversionrc. When I try to run openoffice I get:
bash$ openoffice
OpenOffice.org for Debian - see /usr/share/doc/openoffice.org/README.Debian.gz
running openoffice.org setup...
not enough space on the destination drive
ExitCode: 20
setup failed (code 0).. abort
---- Please read /usr/share/doc/openoffice.org/README.Debian.gz for known problems -----
I run it under strace and found:
2459 getuid32() = 1000
2459 access("/home/steve", F_OK) = 0
2459 statfs("/home/steve/.openoffice/1.1.1", 0xbfffed20) = -1 ENOENT (No such file or directory)
2459 statfs("/home/steve/.openoffice", 0xbfffed20) = -1 ENOENT (No such file or directory)
2459 statfs("/home/steve", 0xbfffed20) = -1 EOVERFLOW (Value too large for defined data type)
2459 statfs("/home", {f_type=0x187, f_bsize=4096, f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0,
f_fsid={0, 0}, f_namelen=255}) = 0
2459 write(2, "not enough space on the destinat"..., 55) = 55
So what's happening is that it's doing a statfs() on my home dir, failing with EOVERFLOW, and then doing a
statfs on /home, which is an automount filesystem (and hence has 0 bytes free).
The solution is probably to recompile at least the setup utility with -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE which will make it use statfs64()
-- System Information: Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8
Versions of packages openoffice.org depends on:
ii dictionaries-common [openoffi 0.22.9 Common utilities for spelling dict
ii openoffice.org-bin 1.1.1-2 OpenOffice.org office suite binary
ii openoffice.org-debian-files 1.1.1-2+1 Debian specific parts of OpenOffic
ii openoffice.org-l10n-en [openo 1.1.1-2 English (US) language package for
-- no debconf information
Reply to: