Can't get a "com.sun.star.frame.Desktop" instance from Libreoffice UNO using Mono
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I have used Mono with LibreOffice in Ubuntu 11.04, and it worked quite well. In Ubuntu 11.10, the bootstrapping works, but I can't get an instance of the "com.sun.
The code in the attached file runs, and tells me that the requested loader is null.
Trying out the code:
1. Start Monodevelop
2. Create a new Command-Line project
3. Delete Main.cs from the project
4. Add the attached file called TestLibreOffice
5. Right-click on "References" in the project tree, select "Edit References"
6. Choose the ".Net Assembly" tab
7. Navigate to the path /usr/lib/
8. Add all cli_*.dll to the project
9. Select the new references in the project tree, right-click on them and disable "Local copy"
10. Run the project (by pressing F5).
On Ubuntu 11.04, the output is "Loader is not null", on Ubuntu 11.10, the output is "Loader is null". So the CIL Bindings for Libreoffice on 11.10 is completely useless for me right now.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libreoffice 1:3.4.3-3ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Thu Oct 6 15:58:26 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
ProcEnviron:
PATH=(custom, user)
LANG=de_AT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to oneiric on 2011-09-15 (21 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 869722 and any other logs that are relevant for this particular issue.