This was also present on previous OOo versions in portage. However, this is how I am ALWAYS able to reproduce this 1. run OpenOffice 2. open the "open" dialog, shows the KDE dialog 3. press cancel and a warning dialog (see attached screenshot) 4. press the OK button or close the dialog, kde crash handler dialog follows 5. close the kde crash handler dialog 6. close openoffice and watch CPU usage jump to 100% as some soffice.bin process fails to shut down 7. try to open any openoffice program while the previous CPU-hogging process runs... nothing happens... ever. No error message, nothing. Only killing the soffice.bin processes makes it possible to run openoffice again. app-office/openoffice-3.0.0 USE="cups dbus gstreamer gtk kde nsplugin opengl pam -binfilter -debug -eds -gnome -java -ldap -mono -odk -templates" LINGUAS="de en en_GB en_US et -af -ar -as_IN -be_BY -bg -bn -br -bs -ca -cs -cy -da -dz -el -en_ZA -eo -es -fa -fi -fr -ga -gl -gu_IN -he -hi_IN -hr -hu -it -ja -km -ko -ku -lt -lv -mk -ml_IN -mr_IN -nb -ne -nl -nn -nr -ns -or_IN -pa_IN -pl -pt -pt_BR -ru -rw -sh -sk -sl -sr -ss -st -sv -sw_TZ -ta_IN -te_IN -tg -th -ti_ER -tn -tr -ts -uk -ur_IN -ve -vi -xh -zh_CN -zh_TW -zu" kde-base/kdelibs-3.5.10-r2 USE="acl alsa arts bindist cups doc jpeg2k lua spell tiff utempter -avahi -branding -debug -fam -kdehiddenvisibility -kerberos -legacyssl -openexr" Lines from emerge --info, which might be helpful: Portage 2.1.6.4 (default/linux/amd64/2008.0/developer, gcc-4.1.2, glibc-2.6.1-r0, 2.6.28-gentoo-worship x86_64) ================================================================= System uname: Linux-2.6.28-gentoo-worship-x86_64-AMD_Athlon-tm-_64_Processor_3200+-with-glibc2.2.5 Timestamp of tree: Mon, 05 Jan 2009 03:00:01 +0000 app-shells/bash: 3.2_p39 dev-lang/python: 2.5.2-r7 dev-util/cmake: 2.4.6-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.4_p6, 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.28-r1 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -march=athlon64 -ggdb" 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/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -pipe -march=athlon64 -ggdb" FEATURES="collision-protect cvs digest distlocks fixpackages multilib-strict parallel-fetch protect-owned sandbox sfperms sign splitdebug strict unmerge-orphans userfetch usersandbox" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="en et en_GB en_US de" MAKEOPTS="-j2" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 177488 [details] Backtrace from the KCrash handler
Created attachment 177489 [details] Screenshot of the *informative* warning dialog. The title reads "Error(kdefilepicker)".
Well I guess that would be better handled upstream, could you please file a bug at http://qa.openoffice.org/issue_handling/pre_submission.html ?
(In reply to comment #3) > Well I guess that would be better handled upstream, could you please file a bug > at http://qa.openoffice.org/issue_handling/pre_submission.html ? > I wouldn't want to waste my time based on guesses. Are you sure it's not a gentoo-specific issue? Have you been able or have you been unable to reproduce this crash?
(In reply to comment #4) > (In reply to comment #3) > > Well I guess that would be better handled upstream, could you please file a bug > > at http://qa.openoffice.org/issue_handling/pre_submission.html ? > > > > I wouldn't want to waste my time based on guesses. Are you sure it's not a > gentoo-specific issue? Have you been able or have you been unable to reproduce > this crash? > No I'm not, because I don't use KDE. Still another thing: Do you have KDE4 also installed?
(In reply to comment #5) > No I'm not, because I don't use KDE. Still another thing: Do you have KDE4 also > installed? No I don't have it installed.
(In reply to comment #6) > (In reply to comment #5) > > No I'm not, because I don't use KDE. Still another thing: Do you have KDE4 also > > installed? > > No I don't have it installed. > Ok, so the fix for these sorts of problems won't help you ;)
The problem comes from kdefilepicker, which is go-oo extension, therefore reporting bug to qa.openoffice.org is a waste of time. I'm going to look at it. I don't promise any results, though :(
Created attachment 178016 [details, diff] openoffice-3.0.0.ebuild.diff fix crash for kdefilepicker on close
http://lists.go-oo.org/pipermail/dev-go-oo.org/2008-September/000791.html Workaround for this bug investigated at september,
Jaak, could you check that workaround fixes the problem?
(In reply to comment #11) > Jaak, could you check that workaround fixes the problem? You mean the patch for the ebuild? Ohwell, I'll leave it compiling then. Be patient.
(In reply to comment #9) > Created an attachment (id=178016) [edit] > openoffice-3.0.0.ebuild.diff > > fix crash for kdefilepicker on close > This won't help as we are already using system alloc (it is default with Go-OO), check your build log for prove. Also the patch would be for the wrong configure.
(In reply to comment #8) > The problem comes from kdefilepicker, which is go-oo extension, therefore > reporting bug to qa.openoffice.org is a waste of time. I'm going to look at it. > I don't promise any results, though :( > Well in this case https://bugzilla.novell.com/index.cgi is the right place to file the bug, as weird as that may sound, but for historic reasons this is the place where Go-OO specific bugs are dealt with.
(In reply to comment #13) > This won't help as we are already using system alloc (it is default with > Go-OO), check your build log for prove. Also the patch would be for the wrong > configure. YAY! All these hours of compiling... wasted resources... system unresponsiveness... at least I could now abort the emerge before it did any more damage! :P It's just that I can't currently afford to sacrifice my box for compiling dinosaurs like OOo this often. It aint all fun either.
(In reply to comment #15) > (In reply to comment #13) > > This won't help as we are already using system alloc (it is default with > > Go-OO), check your build log for prove. Also the patch would be for the wrong > > configure. > > YAY! All these hours of compiling... wasted resources... system > unresponsiveness... at least I could now abort the emerge before it did any > more damage! :P It's just that I can't currently afford to sacrifice my box for > compiling dinosaurs like OOo this often. It aint all fun either. > > Sorry for uneeded patch, i forgot that's portage build of OO has distro-configs with config_office option. But, i build portage oo on both my boxes ~amd64/~x86 and can't reproduce filepicker crash on kde3. Fixes for similar bug is already on go-oo patchset/distroconfigs. Very, very strange.
Only OpenOffice 3.1.1 is in tree, and only KDE4 support is left. Closing.
