Bug 71229 - CLI bridge - bootstrap not working
Summary: CLI bridge - bootstrap not working
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: sdk (show other bugs)
(earliest affected) Master
Hardware: x86 (IA32) Windows (All)
: high critical
Assignee: Not Assigned
Depends on:
Reported: 2013-11-04 18:14 UTC by serg
Modified: 2014-01-06 09:25 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description serg 2013-11-04 18:14:20 UTC
Build: libo-master~2013-11-01_23.37.14_LibreOfficeDev_4.2.0.0.alpha0_Win_x86.msi and libreoffice-4-1~2013-10-31_04.48.54_LibreOfficeDev_4.
OS: Windows 7 32bit
Program: "WriterDemo" from sdk (vb.net)
IDE: Visual Studio Express 2012
.NET: 4.0

The program builds successfully but does not run.

Unhandled Exception: System.Runtime.InteropServices.SEHException: External component has thrown an Exception.
   at cppu.bootstrap(Reference<com::sun::star::uno::XComponentContext>* )
   at uno.util.Bootstrap.bootstrap()
   at ConsoleApplication1.Module1.Main(String[] args)
Comment 1 Lafriks 2013-11-04 19:27:06 UTC
This bug has been there as long as libreoffice sdk introduced .net 4.0 dll's
Comment 2 serg 2013-11-04 20:49:47 UTC
This bug, or similar, was introduced with lbo 4.0.0. It was reported here:

It was reported as fixed in the list of fixed bugs to 4.1.0 beta1, but it was of little consequence because another quite nasty bug was simultaneously, or close to that time, introduced, this one:

And 61503 WAS actually fixed, because I did manage to run programs with 4.1.0, even though it took some work around 67725.

Now that 67725 seems to be fixed, 61503 reappears.
Comment 3 serg 2013-11-30 09:30:21 UTC Beta1 - the bug is still there.
Comment 4 serg 2013-12-07 11:58:48 UTC Beta2 - the bug is there.
Comment 5 jvanderduim 2013-12-09 08:49:00 UTC
Having te same issue. As for now our program can't upgrade to 4.X and is still using 3.6. Any indication when this bug will be picked up?
Comment 6 serg 2013-12-20 22:33:50 UTC (4.2.0 RC1)

The bug is gone!

Comment 7 Stephan Bergmann 2014-01-06 09:25:32 UTC
(In reply to comment #6)
> (4.2.0 RC1)
> The bug is gone!

...so marking this issue as FIXED then.