Skip to content
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

uno.RuntimeException: URP-Bridge: disposed(tid=3) Unexpected connection closure #22

Closed
ehynds opened this issue Jan 11, 2012 · 5 comments
Assignees
Labels
Milestone

Comments

@ehynds
Copy link

ehynds commented Jan 11, 2012

I'm getting this error from a master branch install, Libreoffice 3.3.2. Any help is appreciated...

ehynds@ehynds ~/exports: unoconv -f doc 793.html

Traceback (most recent call last):
  File "/usr/bin/unoconv", line 947, in <module>
    main()
  File "/usr/bin/unoconv", line 879, in main
    convertor = Convertor()
  File "/usr/bin/unoconv", line 583, in __init__
    unocontext = resolver.resolve("uno:%s" % op.connection)
uno.RuntimeException: URP-Bridge: disposed(tid=3) Unexpected connection closure
@dagwieers
Copy link
Member

This is caused by OpenOffice/LibreOffice crashing. If you can reproduce this, please report this upstream !

You may want to test using LibreOffice 3.4.5 or 3.5rc1 to make sure this is not already fixed. And you may want to test also using the latest unoconv from Github, we have intelligence added to make unoconv match the UNO python binary/libraries with the LibreOffice/OpenOffice instance used.

@dagwieers
Copy link
Member

Can you reproduce this ? Is there a way for me to reproduce this ? It works for me on various local HTML files, so it must be something specific to your installation or to this file.

@dagwieers
Copy link
Member

I am closing this issue due to lack of feedback. If this is still an issue, feel free to reopen and provide more information.

@dagwieers
Copy link
Member

@ehynds We are close to releasing v0.6 and we would like to know whether the current master branch fixes the issue you reported. The latest release has a few stability and reliability fixes that may make a difference for your issue.

@ehynds
Copy link
Author

ehynds commented Sep 7, 2012

I'm no longer able to reproduce this issue. Thanks!

@ghost ghost assigned dagwieers Sep 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants