My thoughts on Slackware, life and everything

LibreOffice 3.4.2 packages for Slackware 13.37

Earlier today I uploaded new Slackware 13.37 packages for LibreOffice 3.4.2. The developers themselves say “Safe for production use by most users and enterprises“.

The Slackware server is the primary location for my packages: http://slackware.com/~alien/slackbuilds/libreoffice/ but please do not use this for downloads unless the URLs below do not work for you.

Because they have bigger download speeds to offer, please use one of the mirrors like:

and grab those packages (the mirrors may take a little while to get updated). Remember, those servers have rsync access as well if you like that better than http downloads (even though lftp does that very well).

The 3.4.2 release’s announcement page states that it is “… targeting both private individuals and enterprises. LibreOffice 3.4.2 fixes the majority of the most-important bugs identified by users in the previous version, and can be deployed for production needs by most enterprises“.

I will consider my options for Slackware 13.1. My current packages for that Slackware version are for libreoffice-3.3.3 which is stable and works well enough. I really would like to stop building packages for anything older than Slackware 13.37. Especially for such major pieces of software as LibreOffice, it keeps my build box busy for 2×7 hours, compiling packages for 32-bit & 64-bit…

Have fun!
Eric

31 Comments

  1. y0g1

    Thx again Eric

  2. David

    Mithic!
    And now, good holidays ๐Ÿ™‚

  3. MartinOwaR

    Thanks Eric for all your great work. Does anyone have such a problem: I can’t move the horizontal scrollbar and it is a half visible in Calc and Writer, probably also in the other office applications. This problem is only in LibreOffice 3.4.x, I didn’t have problems with 3.3.x.

    http://martinowar.com/pub/scrollbar.png

    Thanks again!

  4. alienbob

    @MartinOwaR –

    Actually, more distros report this bug with the non-functional horizontal scroll bar. It seems to be related to the KDE theme you use and the height of the scrollbar as defined by the theme.

    However the horizontal scrollbar is actually useable, you just have to be very careful!
    The very uppermost pixel-row of the horizontal scrollbar reacts to your mouse. If you click just right, you can grab that scrollbar and move it left and right without issues.

    Alternatively you can change the height of scrollbars of your theme (System Settings > Application Appearance > Style > Configure) and if you make the height > 16 your scrollbar will be moveable too. But then another bug becomes apparent: you will not be able to move the scrollbar to the left… and every time you click left of the scrollbar, it will actually move to the right! So it is not really an alternative.

    Eric

  5. MartinOwaR

    Yea, you’re right, the bug exists only if I use Oxygen theme. I tried the other themes – everything looks fine. With Oxygen – ‘the very uppermost pixel-row’ workaround works with everyone height value – from 10 to 30.

    Anyway, this is a minor bug, I just was curious if it is related to some my settings.

    Good night, Eric!

  6. Willy Sudiarto Raharjo

    I thought i was the only one with these bugs, but apparently, it affected most people as well..

  7. Willy Sudiarto Raharjo

    Actually the most annoying part is when it happened on Impress.

  8. ulij

    Grab the scrollbar with the mid-button of the mouse, works for me =)

  9. escaflown

    Thanks Eric!

  10. Willy Sudiarto Raharjo

    @Ulic
    Thanks for the tip. It worked!!

  11. Niki Kovacs

    That’s great news! Thanks for the packages! I’ve been eagerly looking forward to them. LibreOffice 3.3.3 mysteriously crashed on me on all the ODTs with macros my editor sends me, so I half-heartedly upgraded to 3.4.0 then 3.4.1. Reading the mention “safe for production” for 3.4.2 comes as a relief.

  12. steev

    I got this error the first time I started Libreoffice

    “The application cannot be started.
    LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice:

    /home/steven/.config/.libreoffice/3”

    Seems the folder is created as root when the doinst.sh runs.

    Anyway I just chown’d it and now libreoffice starts fine. Thanks for the package

  13. dolphin77

    on 64 bit oosplash.bin uses 100% CPU and then segfaults. Changing a line:
    Logo=1
    to:
    Logo=0
    in the file /usr/lib64/libreoffice/program/sofficerc, solves this. Hope this helps to someone.

  14. Brad

    Has anyone successfully run the SlackBuild? I have all the source, dependencies, etc. but it always fails early at:

    Starting libreoffice compilation (takes a long time)…
    ./bootstrap: line 2: /pracovni/prace/lo/build/libreoffice-3-4/build/bootstrap/LinuxX86-64Env.Set.sh: No such file or directory
    bash: ./*[Ee]nv.[Ss]et.sh: No such file or directory
    make: [dmake/dmake] Error 1 (ignored)
    bash: ./*[Ee]nv.[Ss]et.sh: No such file or directory
    make: [all] Error 1 (ignored)
    ./libreoffice.SlackBuild: line 747: cd: /tmp/build/tmp-libreoffice/build/libtextcat/unxl*.pro/misc/build/libtextcat-2.2/src: No such file or directory
    ./libreoffice.SlackBuild FAILED at line 750

    Any hints?

  15. alienbob

    I have built it successfully! Not once but many times.

    Those errors are never the real errors. The build will have failed long before that.

    You will have missed one of the required steps in the preparation. Removing seamonkey and seamonkey-solibs and installing xulrunner instead, AND logging out and back in is a main requirement. The logout/login part is also required if you had to install the JDK.
    Rebooting instead of logout/login is even better – sometimes the added path (for xulrunner) to /etc/ld.so.conf will not be picked up by the linker in time.

    Try catching the build log in a file (sa, “build.log”) and then examine the output of:

    grep -E “(ERROR|Error |error:)” build.log

    That is a bit easier than trying to read all of the build output.

    Eric

  16. Brad

    Hi Eric,

    I followed those steps. Seamonkey and seamonky-solibs removed. xulrunner-1.9.2.18 installed. apache-ant and perl-Archive-Zip installed. logged out and back in.

    You were right, there was an earlier error, but I ignored it as it seemed the buildscripts did as well:

    checking for MOZILLAXPCOM… yes
    checking for PK11_GetCertFromPrivateKey in -lnss3… no
    configure: error: PK11_GetCertFromPrivateKey missing but needed.
    See https://bugzilla.mozilla.org/show_bug.cgi?id=262274.
    Fixed since nss 3.9.3 (contained by e.g. mozilla >= 1.7.5)
    Starting libreoffice compilation (takes a long time)…
    ./bootstrap: line 2: /pracovni/prace/lo/build/libreoffice-3-4/build/bootstrap/LinuxX86-64Env.Set.sh: No such file or directory
    bash: ./*[Ee]nv.[Ss]et.sh: No such file or directory
    make: [dmake/dmake] Error 1 (ignored)
    bash: ./*[Ee]nv.[Ss]et.sh: No such file or directory
    make: [all] Error 1 (ignored)
    ./libreoffice.SlackBuild: line 747: cd: /tmp/build/tmp-libreoffice/build/libtextcat/unxl*.pro/misc/build/libtextcat-2.2/src: No such file or directory
    ./libreoffice.SlackBuild FAILED at line 750

    What is needed to fix the error: PK11_GetCertFromPrivateKey missing but needed.

    The other error seems legit too though. There really is no directory named unxl*.pro under /tmp/build/tmp-libreoffice/build/libtextcat/

  17. alienbob

    @Brad –

    Ah, let me guess… the xulrunner package was created from the script at SlackBuilds.org?

    Eric

  18. ricciare

    Hi guys, an info .. with the 64bit version someone else has 100% crashes using the spreadsheet and simply doing a copy of a cell or of a group of cells?

    Nicola

    That’s what gdb returns me:

    (gdb) run -scalc
    Starting program: /usr/lib64/libreoffice/program/soffice.bin -scalc
    [Thread debugging using libthread_db enabled]
    [New Thread 0x7fffeeb97700 (LWP 1765)]
    [New Thread 0x7fffda607700 (LWP 1766)]
    [New Thread 0x7fffd9e06700 (LWP 1767)]
    [New Thread 0x7fffd73ac700 (LWP 1768)]
    [New Thread 0x7fffd6433700 (LWP 1769)]
    [New Thread 0x7fffd51d6700 (LWP 1772)]
    [Thread 0x7fffd51d6700 (LWP 1772) exited]
    [Thread 0x7fffda607700 (LWP 1766) exited]
    LibreOffice(1764)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing “/usr/share/mime/magic”
    LibreOffice(1764)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing “/root/.local/share/mime/magic”
    [New Thread 0x7fffda607700 (LWP 1775)]
    [New Thread 0x7fffd51d6700 (LWP 1776)]
    [Thread 0x7fffda607700 (LWP 1775) exited]
    [Thread 0x7fffd51d6700 (LWP 1776) exited]
    [New Thread 0x7fffd51d6700 (LWP 1777)]
    [Thread 0x7fffd51d6700 (LWP 1777) exited]
    [New Thread 0x7fffd51d6700 (LWP 1778)]
    [New Thread 0x7fffda607700 (LWP 1779)]
    [Thread 0x7fffda607700 (LWP 1779) exited]
    [Thread 0x7fffd51d6700 (LWP 1778) exited]
    QPixmap: It is not safe to use pixmaps outside the GUI thread
    QPixmap: It is not safe to use pixmaps outside the GUI thread
    QPixmap: It is not safe to use pixmaps outside the GUI thread

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 0x7fffd73ac700 (LWP 1768)]
    0x00007fffea466292 in ?? () from /usr/lib64/libQtGui.so.4

  19. Brad

    Eric,

    I tried using theirs first, then I tried using yours, but with the version updated from 1.9.2.17 to 1.9.2.18. I’m getting the same error with both xulrunner builds.

    Brad

  20. Brad

    Removing xulrunner-1.9.2.18 and installing your build of 1.9.2.17 seems to have fixed my problem.

    Thanks Eric!

  21. ricciare

    I’ve noticed that problem happens just if I use scalc from the root account … from user everything seems to work good.

  22. John D. L. Platt

    Thank you for all your work. I’ve been trying to compile this on a 3.0 kernel and I keep running into problems. I took your advice and removed my seamonkey (a hardship I built 2.3 beta 2 using edited slackbuild scripts) and installed the xulrunner slackbuild from your directories. It consistently crashes with the following messages:

    checking for MOZ_NSS… no
    checking for MOZ_NSS… yes
    checking for MOZ_NSPR… yes
    checking for MOZILLAXPCOM… no
    checking for MOZILLAXPCOM… yes
    checking for PK11_GetCertFromPrivateKey in -lnss3… no
    configure: error: PK11_GetCertFromPrivateKey missing but needed.
    See https://bugzilla.mozilla.org/show_bug.cgi?id=262274.
    Fixed since nss 3.9.3 (contained by e.g. mozilla >= 1.7.5)
    Starting libreoffice compilation (takes a long time)…
    ./bootstrap: line 2: /pracovni/prace/lo/build/libreoffice-3-4/build/bootstrap/LinuxX86-64Env.Set.sh: No such file or directory
    bash: ./*[Ee]nv.[Ss]et.sh: No such file or directory
    make: [dmake/dmake] Error 1 (ignored)
    bash: ./*[Ee]nv.[Ss]et.sh: No such file or directory
    make: [all] Error 1 (ignored)
    libreoffice.SlackBuild: line 747: cd: /tmp/build/tmp-libreoffice/build/libtextcat/unxl*.pro/misc/build/libtextcat-2.2/src: No such file or directory
    libreoffice.SlackBuild FAILED at line 750

    Any suggestions?

    {Oh, I’ve reinstalled seamonkey since it’s my default web browser. I really uninstalled it ONLY to recompile libre office because that works so much better than other slackbuilds).

  23. alienbob

    @John

    This is exactly the same error message as posted earlier by Brad, and I would expect that this is cured by my xulrunner package. Why this does not work for your setup, I do not know. Try to retrace all your steps.

    Eric

  24. John D. L. Platt

    Redoing it and examining the log file I find:

    checking whether to turn warnings to errors… no
    configure: error: PK11_GetCertFromPrivateKey missing but needed.
    make: [dmake/dmake] Error 1 (ignored)

    As above.

    The xulrunner installed is:

    xulrunner-1.9.2.17-i486-1alien.txz:

    Which I believe is the one which you say should work. I tried using pastebin.com to put up part of my logfile but it didn’t work out. Suffice it to say that with xulrunner 1.9.2.17 installed and having rebooted I am still getting this error and was in fact before I asked.

  25. Oleg

    Thanks!

  26. kibe

    Thanks, just realized files with .docx extension open as blank pages any ideas?

  27. ozone89

    hi Eric,
    you’re surely gonna hate me… XD

    whenever i close Firefox, LibreOffice starts on his own O_o

    I’ve installed it via your prebuilt packages for x64.

    If you know more infos, let me know

  28. ozone89

    ooops, my bad, just realized my typo ๐Ÿ˜›

    s/know/want/ ๐Ÿ˜‰

  29. H.C

    I had the same problem as ozone89.

    Couldn’t figure out what the hell was going on, so I had to remove it and stick with kword.

  30. gegechris99

    Hope it’s not too late ๐Ÿ™‚

    Thank you for this update. It works fine for me (I’m using fluxbox, not KDE).

  31. Fred

    I get an error message when I try to launch LibreOffice. The error says (translated from French) “impossible to launch the oosplash binary file.

Leave a Reply to ricciare Cancel reply

Your email address will not be published. Required fields are marked *

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

© 2024 Alien Pastures

Theme by Anders NorenUp ↑