Macro not showing up in Ubuntu 14.04 LO 4.2.3.3 Build ID: 420m0

Hi,

I have a calc file containing a Macro. In this file I have a button that trigger the PDF EXPORT macro. After upgrading to Ubuntu 14.04, have LO 4.2.3.3 installed, here is the error I have when cliking on the button (same under Lubuntu 14.04):

com.sun.star.uno.RuntimeExceptionUnable to obtain document content factory!
image description

If I create a new calc, draw a form button, link it to my pdf export macro : No problem !

So I tried adding a new button on my existing sheet, assign a macro and BAM ! : No macro are displayed as available to select. See below :

Whereas on my new created file, I can assign a macro to my button! So the error dialog must be related to this…

Note : On my laptop Ubuntu 14.04, the problem solved by itslef…I don’t know why. But on my desktop (Ubuntu 14.04) and netbook (Lubuntu 14.04) the problem remains.

Any chance of revealing your macro itself?

Sure! I added it in the question

UBUNTU 14.04 : I solved it by installing LO from the ubuntu software center. Even though LO was already installed, it appeared as NOT installed in the Ubuntu Software Center. After the installation completed, I couldn’t reproduce the error. That was for UBUNTU 14.04.

LUBUNTU 14.04 : it appears that I just didn’t installed the JAVA JRE which is needed to run the macro from the buttons : apt-get install openjdk-7-jre

Finally, I think that in both case, the problem was related to LO and the JRE that was not well configured. With such kind of error, you should have a look at tools > options > libreoffice / advanced > and be sure to have the right JRE detected and selected by openoffice. (LO needs to be restarted after any modifications.)

That error message appears to issue from /ucb/source/ucp/tdoc/tdoc_documentcontentfactory.cxx. There was one change (line #114) to that function between the two indicated releases (on 2014-02-25) - refer History of the file. Seems to be a basic error handling change so am unsure to what degree it may be the cause.

Hi. I have no idea why, but it’s working now. I will investigate more when I’ll have time (try on Lubuntu as well see if it’s still bugging) …very strange for me.

After investigating on my Desktop 14.04, I made some progress. So I updated my problem.