Hi, I recently rebuilt my Gentoo system using the new 1.4_rc2 PIII GRP LiveCD. When it came to installing OO I opted to use the GRP install. However, when running OO for the first time (either ooffice or oowriter) errors occured. Then a segfault was reported. I cleaned it up, did an emerge openoffice-bin instead and tried again with the graphical install (running /opt/OpenOffice.org1.0.1/setup). The same errors occured in this installer. Then I tried again using the oowriter wrapper script again. The errors occured again, but this time it did actually run OpenOffice. A text file is attached to this bug with the errors I got in the console. These errors seem to be related to the copying of icons from /opt/OpenOffice.org1.0.1/share/icons or /usr/share/icons. NOTE: I am using LVM with a traditional multi-partition layout (separate /usr /var and so on). Because my / volume is quite small I made /opt a symlink to /usr/opt. Maybe this confuses the installer?
Created attachment 7396 [details] Errors experienced upon running oowriter wrapper script
I had the same problem myself after installing the OOo-bin 2 evenings ago. My non-programmer analysis (ie - I don't know what to look for where in order to demonstrate the problem for actual fact) is as follows: 1) OOo-bin installed to a fluxbox only machine (more further down) 2) OOo setup script failed when choosing local install. 3) OOo setup script succeeded when choosing a network install. 4) When starting soffice or swriter for the first time, the user initialization script (or whatever it is that they call it) gave error messages, one each for each item which it complained about copying. Several points: A) This is a 48 meg machine and I did not expect the install to succeed at all. (which is why I did not originally report a problem.) B) While I have many components of KDE and Gnome installed, I have not actually installed either because I use fluxbox exclusively on this machine (for, I think obvious reasons). C) Looking at the error messages in detail revealed that _ALL_ the items were icons directed first to KDE share directories and then subsequently to Gnome directories. Since I don't have either KDE or Gnome 'officially' installed, these error messages made sense to me. However, I could see the directories were there and that icons were install. I suspect that the messege is slightly bogus in that the OOo script may have made the directories after complaining. Note, I was not about to rebuild a working K6 233, 48meg system to confirm this! Or start deleting directories in either KDE or Gnome (just in case soing so might break something else!). D) Running OOo (which takes some period of time slightly less than forever to load) is actually not bad and all the appropriate icons internal to OOo appear to be there. Based on the above, I considered the problem to be with the OOo folks. And that their expectations for what kind of environment people would run OOo in excludes lean, mean and fast WMs. ;) I hope this information helps. --------------------------------- Kerin, what window manager were you using when you invoked OOo for the first time?
Have a look at the ebuild, and comment the following lines in src_install(): --------------------------------------------------------------- # Unneeded, as they get installed into /usr/share... rm -rf ${D}${INSTDIR}/share/{cde,gnome,kde} --------------------------------------------------------------- Then remerge, and please let me know if this fixes it.
It mostly fixes it. ;-) I missed the messages where the OOo first time script wants to copy items (about 6) to ~.kde2/share ... But yes, it does fix all the icon related messages.
Yes, that fixed it. Not a single error occurred, and the icons and mime types were registered properly this time, at least in KDE - which was the window manager I was and am using. However, I am normally a Gnome user so I intend to test the procedure again once I have that re-merged. One other thing: I seem to recall that the "kde" and "gnome" flags are ignored by the script - that is, it runs both branches for KDE and Gnome regardless. This I will double-check too.
Seth fixed this in latest revisions.
