-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error starting extension #20
Comments
This is really strange. Do you have similar problems with other LibreOffice extensions written in Basic? Did you try to install OOoLilyPond in previous LibreOffice versions? |
Just another idea: Cheers, |
I have the very same problem. I've tried:
I don't use LibreOffice very often, so I can't tell if this happens to other extensions aswell. I've also tried commenting that line. It produces the same error message, but in "Editor" line 19, but it may be due to the commented line. No more ideias. |
Hi Yves-Antoine, thanks for testing. Now I know that your "ElementNames" list is completely empty. Unfortunatly I really don't know what to do now. That's the only place I know where I could ask for help. Hopefully there is someone with a deeper knowledge than me. Cheers, |
Hello Klaus, Thanks for your time! Cheers.Yves-Antoine. |
To everyone who is concerned by this issue: 1.) Uninstall OOoLilyPond via the Extension Manager. 2.) Rename the LO profile folder as desribed here: 3.) Reinstall OOoLilyPond |
Hello Klaus, Thanks for your support. |
A user who had the same problem has reported that deleting the subfolder "extensions" inside the user folder did the trick. |
Installed the extension in LibreOffice Version: 6.0.4.2 on Linux (Build ID: 1:6.0.4~rc2-0ubuntu0.14.04.2
CPU threads: 4; OS: Linux 3.13; UI render: default; VCL: gtk2;).
When I click the OLy button on the toolbar or select Tools -> Addons -> oooLilyPond from the menus, I get the following error message:
The Syntax editor goes to line 67,
DialogLibraries.LoadLibrary (constOLyLibraryName)
.The text was updated successfully, but these errors were encountered: