Just got these today, after upgrading to 2.2.1-8 % dpkg -s openoffice.org Package: openoffice.org Status: install ok installed Priority: optional Section: editors Installed-Size: 260 Maintainer: Debian OpenOffice Team <debian-openoffice@lists.debian.org> Architecture: i386 Version: 2.2.1-8 % openoffice /usr/lib/openoffice/program/soffice: line 360: 22522 Bus error "$sd_prog/$sd_binary" "$@" GLib: Cannot convert message: Could not open converter from 'UTF-8' to 'latin9' ** (process:22505): WARNING **: Unknown error forking main binary / abnormal early exit ... % oocalc /usr/lib/openoffice/program/soffice: line 361: 22547 Bus error "$sd_prog/$sd_binary" "$@" GLib: Cannot convert message: Could not open converter from 'UTF-8' to 'latin9' ** (process:22530): WARNING **: Unknown error forking main binary / abnormal early exit ... % oowriter /usr/lib/openoffice/program/soffice: line 361: 22568 Bus error "$sd_prog/$sd_binary" "$@" GLib: Cannot convert message: Could not open converter from 'UTF-8' to 'latin9' ** (process:22551): WARNING **: Unknown error forking main binary / abnormal early exit ... And so on. However, the really interesting part is this: odin:/usr/lib/openoffice/program% ldd soffice.bin /usr/bin/ldd: line 117: 22583 Bus error LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$@" odin:/usr/lib/openoffice/program% ldd unopkg.bin /usr/bin/ldd: line 117: 22595 Bus error LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$@" There is nothing in syslog or dmesg that would indicate hardware failure. All other programs I've tried so far work as one would expect. So it appears that something in the OO.o binaries themselves triggers this. System information: % uname -a Linux odin 2.6.22.1 #1 SMP Tue Jul 24 13:22:17 EEST 2007 i686 GNU/Linux odin:~% cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz stepping : 2 cpu MHz : 1798.271 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm bogomips : 3599.03 clflush size : 64 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz stepping : 2 cpu MHz : 1798.271 cache size : 2048 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm bogomips : 3596.42 clflush size : 64 At first I suspected a hardware failure, but that seems rather unlikely, since even ldd causes the same error and only with OO.o binaries. I also attached strace -f log of "openoffice" execution. Versions of basic libraries: libc6: 2.6.1-1+b1 libgcc1: 1:4.2.1-4 libstdc++6: 4.2.1-4 Any other information I can provide? -- Mika Boström +358-40-525-7347 -=- The flogging will continue Bostik@iki.fi www.iki.fi/bostik -=- until morale improves GPG: 0x039F188E; EC67 5B3A E6E3 6A84 9CB2 94D3 BFCD BD57 039F 188E
Attachment:
ootrace.log.gz
Description: Binary data
Attachment:
signature.asc
Description: Digital signature