Since 2.1*, and still happens in 2.2.0, how to get a nice crash: New Presentation, F5(Slideshow), ESC(to close slideshow), ALT-F X (to close), and "boom", it crashes. I can reproduce it reliably under beryl, kexman got the same with metacity. I guess more fixes like the last one in the release notes of 2.2.0 are needed. Reproducible: Always Steps to Reproduce: 1.Open ooffice2 2.New Presentation, F5, ESC, ALT-F X 3. enjoy the crash Actual Results: crash, recovery dialog, etc. Expected Results: closing the window $ emerge --info Portage 2.1.2.2 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.5-r0, 2.6.20-gentoo-r6 x86_64) ================================================================= System uname: 2.6.20-gentoo-r6 x86_64 Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz Gentoo Base System release 1.12.9 Timestamp of tree: Thu, 19 Apr 2007 06:30:01 +0000 dev-java/java-config: 1.3.7, 2.0.31-r7 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.15-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.20-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe -ftree-vectorize -ftree-vectorizer-verbose=1" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/php/apache1-php5/ext-active/ /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=nocona -O2 -pipe -ftree-vectorize -ftree-vectorizer-verbose=1" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="es_ES.UTF-8" LINGUAS="es es_ES en" MAKEOPTS="" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/layman/voip" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aac acl acpi aiglx alsa amd64 apache2 arts avahi avi bash-completion berkdb bitmap-fonts bluetooth bonjour cairo cdr cli cracklib crypt cups curl dbus dlloader dri dvd dvdr dvdread eds emboss encode esd evdev evo fam firefox fortran galago gdbm gif gnome gpm gstreamer gtk gtk2 hal iconv icu iproute2 ipv6 isdnlog java jpeg kde kdehiddenvisibility kerberos lcms ldap libg++ logrotate lucene mad midi mikmod mmx mono mouse mp3 mpeg ncurses nls nptl nptlonly nsplugin obex ogg opengl oss pam pcre pdf pdflib perl png ppds pppd python qt3 qt3support qt4 quicktime readline reflection sdl session spell spl sse sse2 ssl svg tcpd theora threads tiff truetype truetype-fonts type1-fonts udev unicode v4l v4l2 vorbis xinerama xml xorg xrandr xv xvid zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" DVB_CARDS="usb-wt220u" ELIBC="glibc" INPUT_DEVICES="synaptics mouse evdev keyboard" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="es es_ES en" USERLAND="GNU" VIDEO_CARDS="vesa i810 intel" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
I meant Alt-F C, but X works for me too :)
I can reproduce that. Still: Could you file that upstream?
where is upstream? Novell? if so URL Sun? ditto I spend hours looking for the diverse and moving locations of openoffice.org bugzillas, just to be told that I used the wrong one after that. I read recently in some bug that we were not using "official" sources, but the old-ximian-now-i-don't-know-how-is-called build.
(In reply to comment #3) > where is upstream? > > Novell? if so URL https://bugzilla.novell.com/index.cgi > Sun? ditto http://qa.openoffice.org/ > I spend hours looking for the diverse and moving locations of openoffice.org > bugzillas, just to be told that I used the wrong one after that. It's actually not THAT complicated, if the bug is reproducable in openoffice-bin > OOo issuezilla, if not: Novell (and ours for both, so that we know). Normaly I point people directly to the right URL, in this case I just thought you would know, as I remembered you from earlier bug reports. > I read recently in some bug that we were not using "official" sources, but the > old-ximian-now-i-don't-know-how-is-called build. > That's not quite true. It's more like: We use the official source, plus a bunch of patches from ooo-build. But yes: It's not an unmodified OpenOffice.org, which complicates the bug reporting process a fair bit.
openoffice-bin is not amd64, but runs in 32-bits compat mode, so I dont think the crash will be there. I have not installed it so I can't test (openoffice and openoffice-bin block each other). Anybody can test with a binary build? or a native build on a 32 bit platform. I think there is no official amd64/x86_64 build at oo.o, so this leaves us with novell. Their bugzilla does not allow me to login with the password they gave me. See? it is not that simple :(
It is known to ooo-build devs, see thread: http://lists.ximian.com/pipermail/openoffice/2007-April/002252.html Though, there is no solution. Just known to be caused by system components. http://lists.ximian.com/pipermail/openoffice/2007-April/002257.html
Created attachment 116844 [details, diff] crashfix Well, no real fix. Rather a hack to hide the segfault. Upstream should decide what has to be done to fix this.
The 2.2.0-ebuild is now using a newer ooo-build snapshot, which incorporates the fix by Hanno (which also corrects the problem for me), great catch, thanks. Closing.