Libre Office 3.3.0-rc3

Here they are: packages for the third release candidate of the upcoming LibreOffice 3.3.0.

They have been compiled from source, as opposed to repackaging RPM files. These packages are native Slackware stuff. If you are running Slackware with a non-english localization, you can additionally install an appropriate language pack. No dictionaries are included, get a dictionary for your language at http://extensions.services.openoffice.org/en/dictionaries .

You can find the Slackware LibreOffice package and language packs – and associated build scripts – at the usual locations:

The package has no further dependencies – a full Slackware 13.1 install (or -current) is all.

Search for the previous posts that I wrote on this blog about LibreOffice if you are interested in building these from the sources yourself… it is not a trivial task.

Eric

Update 15-jan-2011:

  • If your extension manager refuses to start, or the list of installed extensions is empty, and you are unable to install any new extensions, then try removing the (likely corrupted) extensions database – they will be re-created when you start a Libreoffice application the next time:

$ rm -r ~/.libreoffice/3/user/extensions

  • If you notice that your LibreOffice menu entries no longer work and you are even missing the LibreOffice Writer menu entry, then you should upgrade to my re-built packages for version 3.3.0.3 (they have “2alien” as the build number). The menu entries in the first build were broken because the LibreOffice program names have changed between RC2 and RC3 (“oowriter” has been renamed to “lowriter” and so on).

13 thoughts on “Libre Office 3.3.0-rc3

  1. Pingback: Tweets that mention Alien Pastures » Libre Office 3.3.0-rc3 -- Topsy.com

  2. Hi Eric,

    thanks again for providing these packages. Generally they work well and are a great relief!

    I found only two little snags.
    (1) I can’t install any of the dictionary files. Either I get “doesn’t exist” or “tag < missing" or so.
    (2) With this version as well as with RC2 I got an error on the very first attempt to start the application: "tag < missing" or so. I started from LbiO from the KDE menu. The application was finished immediately. Then I clicked a second time on the icon and all was fine. No trace of the initial error, again.
    As I said, this was the case with RC2, already, too.
    BTW, I am using LibO with the German language pack, and I tried to add German (frami) and Canadian English dictionaries, but got the errors mentioned above (1).
    Not sure, if this are errors of the LibO RC3 in general or if they just occur on Slackware64 13.1 (because I don't have anything else, anymore… ;))

    But again: Thanks for your excellent work!

    gargamel



  3. Ah, ok, now I see: I got an error message complaining about a wrong security code, but the post was submitted anyway!
    Sending the post with the correct code created the duplicate post.
    There seems to be a problem with security code processing?

    gargamel

    gargamel


  4. This package did not properly update the K-Menu shortcuts. The new binaries have been changed from oowriter, oocalc, etc. to lowriter, localc, etc. It also removed the writer shortcut all together.


  5. @em21701 –

    Well, the .desktop files for the menus are still installed, but since the name of the program starters have changed (oowriter -> lowriter, oocalc -> localc etcetera) the menu entries no longer work.

    The fact is, that all menu entries have been updated partly… but only the “Writer” menu entry had the other part updated. There is a “TryExec” line in every .desktop file to let the desktop manager find out if the program has actually been installed, so that it can make a decision to not show the menu entry. And that is why the Writer menu entry is invisible now.

    I will have to update the packages in a rebuild. In the meantime, it’s easily fixed with the following two commands:

    # sed -i -e “s/Exec=oo/Exec=lo/g” /usr/share/applications/*.desktop

    # update-desktop-database /usr/share/applications

    Eric


  6. @gargamel –

    The WordPress blog software seems to have an issue with the > ‘ < character. Everybody who posts a comment containing that character gets the error message while the post has actually been accepted and published... I have no idea why Libreoffice aborts the very first time you run it. That was something I experienced with all the previous versions. I tried installing LibreOffice 3.3.0.3 on a fresh computer and was able to install some dictionaries without issues. I have seen that tag error in the past and I think it points at a corrupted extensions cache in your ~/.openoffice somewhere. Unfortunately I can not remember if Libreoffice started the very first time now... I think it did... Eric


  7. Thanks these valuable hints!
    I renamed ~/.libreoffice to ~/.libreoffice.sav, started LibO and was able to install the dicitonary extension without problems. However, trying to install it from the internet with the extension manager from the URL above resulted in a “does not exist” error message, again. Which is weird, because the file *IS* there, I could download it and install it from my local harddisk.

    gargamel


  8. BTW, my last post didn’t contain an opening XML tag, but I didn’t enter a security code, at all. So it was correct, that I got an error message, that the security code was invalid. But shouldn’t the system reject the submission of the post, when no security code is given, at all?
    What is the code good for, if it is possible to submit posts even without specifying a security code?
    The Wiki software seems to have a bigger issue, here…

    gargamel


  9. Hi and many thanks for this great build!

    Now, since oowriter has been changed to lowriter (and so on) — any idea if LibreOffice could to be used with Bibus?

    regards

    -lunar


  10. Thanks for the new package. I had to delete ~/…/extensions and restart to add the dictionary, so thanks for that tip. I also got the above tag error, but I tried again and it started fine. I also no longer see the Captcha, so I’m gonna submit anyway and see what happens. If you read this, know that I did not enter a captcha.


  11. Pingback: So you want to be a Slacker! What do I do next? - Page 12


Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.