Main menu:

Sponsoring

Please consider a small donation:

 

 

Or you can donate bitcoin:

 

Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.

Search

My Favourites

Slackware

Calendar

September 2014
M T W T F S S
« Aug    
1234567
891011121314
15161718192021
22232425262728
2930  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

Meta

LibreOffice 4.1.3 for Slackware 14.0 and -current

There is a new source release of LibreOffice.- thanks Willy for notifying me this morning. The new 4.1.3 is another stability and bugfix release. Note that the developers are stating that LibreOffice 4.1.3 “is suitable for early adopters and private power users — for conservative requirements, we refer you to LibreOffice 4.0.6 from the previous series“. But, I think you can safely upgrade.

The fresh LibreOffice 4.1.3 packages for Slackware are available in my 14.0 package repository -  I just uploaded them. Remember, they will work on Slackware-current just as well. Note that I ship my LibreOffice 4.1 packages with additional “libreoffice-dict-<language>” packages, containing dictionary and spellchecker support!

If you are still running Slackware 13.37 you should stick with LibreOffice 3.6.7 for which I also have packages.

Please select one of the mirrors as your preferred download location, because they offer bigger bandwidth than the master site at slackware.com.

You can subscribe to the repository’s RSS feed if you want to be the first to know when new packages are uploaded.

Cheers, Eric

Comments

Pingback from So you want to be a Slacker! What do I do next? – Page 25
Posted: November 2, 2013 at 14:44

[…] […]

Comment from Eduardo
Posted: November 2, 2013 at 23:21

Thank you Eric! I found a bug where LO crashes in KDE. It happens upon invocation of the file dialog. When invoking this dialog for saving a file, just clicking something with the mouse crashes the program. If I need to save something, I am forced to navigate the dialog with the keyboard, using the Tab key and the Alt-shortcuts.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f386426ad00, pid=17969, tid=139880483456832
#
# JRE version: OpenJDK Runtime Environment (7.0_45-b31) (build 1.7.0_45-b31)
# Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libQtGui.so.4+0x39fd00] QTransform::type() const+0×0
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” before starting Java again
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
#

(I have the full log should you need it).

Comment from alienbob
Posted: November 3, 2013 at 15:40

Hi Eduardo

On Slackware64-current, with the same OpenJDK 7u45_b31 installed, and running KDE 4.11.2, I can not reproduce your issue. The “save” and “save as” dialogs work fine, and I can click the mouse anywhere without causing a crash.

I tried with and without Java support enabled in LibreOffice.

Eric

Comment from Eduardo
Posted: November 3, 2013 at 17:06

Eric: Thanks. I suspect that was the case, since I saw no one else complaining. Perhaps an extension is wreaking havoc. The problem is I cannot get rid of them; the extension dialog does not work. I’ll investigate further.

Thank you again Eric!

Comment from Eduardo
Posted: November 3, 2013 at 17:30

I think I found the reason of the crash, and I think it’s related to scim and anthy. using ‘export XMODIFIERS=’ before invoking libreoffice appears to solve the problem. Interesting to say the least.

Comment from Eduardo
Posted: November 3, 2013 at 17:30

More background: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620422

Comment from Hannibal
Posted: November 5, 2013 at 09:49

First of all, thanks Eric for all your work!

I’ve encounter different bug in file save dialog. This apply only to KDE like file save dialog LO one works OK. And the problem is that during saving “csv” file in calc I cannot check “edit filter settings” checkbox. It is always grayed. 4.1.2 have same problem but AFAIR in 4.0.X it works OK, and for sure it works in 3.X.Y.

Comment from alienbob
Posted: November 5, 2013 at 13:01

Hi Hannibal & Eduardo.

The bugs you describe are LibreOffice bugs, not Slackware bugs. The best you can do is to open a bug report in the LibreOffice bugtracker, https://www.libreoffice.org/get-help/bug/

Cheers, Eric

Comment from Eduardo
Posted: November 5, 2013 at 13:33

Hi Eric, you’re right. I think I’ll file a bug report upstream. Meanwhile, my info will serve as heads up for others who read the info here.

Cheers,

Eduardo

Comment from Michelino
Posted: November 12, 2013 at 12:50

Hi Eirc,
just to point you out that pdf import doesn’t work, probably due to the libpoppler upgrade in current.
I guess you built the package before Mon Oct 28, so now pdfimport miss libpoppler.so.26.
Do you agree or it’s my fault?

Comment from alienbob
Posted: November 14, 2013 at 13:27

Hi Michelino

It sounds like you are right.
You can try linking libpoppler.so.26 to libpoppler.so by executing “ln -sf libpoppler.so libpoppler.so.26″ in the lib directory and hope that this makes the PDF import work again… but it is a hack and success is not guaranteed.

I am not going to compile LibreOffice packages for Slackware 13.37 in future, so it may well be that I wll compile further LibreOffice 4.1.x for Slackware 14.1 and new 4.2.x releases only for Slackware-current.

Eric

Comment from Michelino
Posted: November 19, 2013 at 19:41

I’ve already tried linking libpoppler, in this way no error occurs, but I wasn’t able to import the pdf, so I gave up.
Maybe the specific file was protected, I think I’ll give it another try.
For the rest no matter, I’m always in -current mode
:-)
Thanks for the reply.

Write a comment