Plainly short story: this file crashes OpenOffice 2.0 on SuSE 10.0 and OpenOffice 2.0.1 on Gentoo Linux but works fine on OOO 2.0 on Windows XP. Detail story: I have an buggy OOO draw file. This file is originally worked out on a Gentoo Linux running binary OpenOffice 2.0, and modified on my SuSE 10.0 Linux with OOO 1.9 (should be beta2). Also my colleague modified it on Windows XP/OpenOffice 2.0. Recently I upgraded my SuSE 10.0 from OOO 1.9 to OOO 2.0 and upgraded my Gentoo Linux from binary OOO 2.0 to self-compiled OOO 2.0.1. And this file crashes both OOO upon opening the file. Both OOO seems to be crashing right after most of the file loaded. Meanwhile, the file is fine on Windows as I mensioned. The people on OpenOffice project said this file works for them. So this could be a distribution-related bug. But this is not the first time OOO 2.0.1 on gentoo behave differently then on other systems. E.g. for several times the objects copied from Draw to Writer have different shape, an object is drawn and filled with certain color but simply appear transparent... Extra info: Please notice this file has only used one font, the HKSCS government stantand font can be downloaded for free from http://sc.info.gov.hk/gb/www.info.gov.hk/digital21/chi/hkscs/reference_iso10646.html
The URI of this bug is the sample document. See if it crashes your OOO. zhangweiwu@Joe /var/spool/.bp $ emerge info Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-r1, 2.6.11-gentoo-r6 i686) ================================================================= System uname: 2.6.11-gentoo-r6 i686 Intel(R) Celeron(R) CPU 2.40GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig digest distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.sjtu.edu.cn/gentoo ftp://ftp.tsinghua.edu.cn/mirror/gentoo http://ftp.gentoo.or.kr" LANG="zh_CN.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X a52 acl alsa apache2 apm audiofile avi bzip2 cdr cjk crypt cups curl dba doc dvd eds emboss encode esd exif expat fam ffmpeg flac foomaticdb fortran gd gdbm gif gimp gimpprint glut gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml iconv idn imagemagick imap imlib ipv6 jabber java jpeg jpeg2k lcms ldap libg++ libwww mad mailwrapper mhash mikmod mmx mng mozdevelop mozilla mozsvg mozxmlterm mp3 mpeg msn mysql ncurses net nls nsplugin ogg oggvorbis opengl pam pcre pdflib perl png ppds python quicktime readline recode samba sdl session smtp speex spell sse ssl svg svga tcpd theora tiff truetype truetype-fonts type1-fonts udev unicode usb vorbis win32codecs wmf xine xinerama xml2 xmms xprint xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Crashes my OOo here too. Still: Did you try with openoffice-bin? Does it crash, too?
As far as I can remember, openoffice-bin 2.0.0 (not 2.0.1) open this file okay but crash when scrolling thumbnails (to avoid crashing: close thumbnail). openoffice on windows never crash (2.0.0) openoffice 2.0 beta2 on SuSE 10.0 never crash with this file. I didn't test openoffice-bin 2.0.1 yet.
This bug was: http://www.openoffice.org/issues/show_bug.cgi?id=60725
I more and more belive this is a distribution-related bug because this file opens fine on Ubuntu on openoffice 1.9 and 2.0 (a special version of 2.0 for Chinese enhancement, not standard Ubuntu OOO 2.0).
Could it be a font issue? There are many broken fonts around. Especially with asian characters. It shouldn't crash of course, but at least older versions of freetype did crash on some classes of broken fonts.
Could be font's problem. The bad thing about non-opensource font is that, even if it is provided for free, as the hkscs font, once you find a bug in it, you cannot correct it (just try to talk with a HK officer talks a lot of time). I just tested this document on openoffice-bin 2.0.1 and it did NOT crash. (=works fine)
If it does work on the bin and you have the same problem on SUSE, please report it uptream for ooo-build, the correct place is her: https://bugzilla.novell.com/index.cgi
I don't understand, the file fail with openoffice that is compiled from source by an emerge, is there anything to do with SuSE in the concept of "upstream"? What if SuSE people say you are the 'upstream'? I never have the oppotunity to try this file on SuSE openoffice 2.0.1 (I only tried on SuSE openoffice 2.0.0 because I don't think SuSE officially distrubuting OOO 2.0.1 yet in their auto-package update). Besides, this file works with Ubuntu. just in case I am not clear: Ubunto OpenOffice 2.0 (non-standard-package) --- works Ubunto OpenOffice 1.9 --- works Windows XP/2000 with openoffice 2.0 --- works Gentoo openoffice-bin 2.0 --- works Gentoo openoffice-bin 2.0.1 --- works Gentoo openoffice 2.0.1 (emerged) --- FAILS SuSE 10.0 + openoffice 1.9 (official package)--- works SuSE 10.0 + openoffice 2.0 (official package)--- FAILS
In my above comment, SuSE 10.0 + openoffice 1.9 means the openoffice 1.9 pre-installed on SuSE 10.0 distribution, which gets rebanded as openoffice 2.0 (SuSE 10.0 is released ahead of openoffice 2.0, so it is not possible to deliver OOO 2.0 on it. It should be simply 1.9 renamed.)
The problem seems to have only been introduced recently, so no wonder that you get mixed results. Anyway: this looks to be a duplicate of bug #116473 *** This bug has been marked as a duplicate of 116473 ***
