(error-ID 67040912) java related problem with the libreoffice integration on debian wheezy 64
On Debian Wheezy (stable, vanilla installation of libreoffice 3.5.2.4), there appears to be a problem with the LibreOffice-integration of zotero (both in its standalone or plugin version).
The error report says:
[JavaScript Error: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIServerSocket.init]" {file: "file:///local/zotero/extensions/zoteroOpenOfficeIntegration@zotero.org/components/zoteroOpenOfficeIntegration.js" line: 62}]
I tried all advice I could find in the forums, but the problem persists. Java runtime environment is Sun's 1.6.0_27.
Java is activated in LibreOffice via the options-menu.
Thanks in advance for any clues. So far, I stick with RTF-scan (great to have that option); unfortunately, its functionality is still somewhat limited.
The error report says:
[JavaScript Error: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIServerSocket.init]" {file: "file:///local/zotero/extensions/zoteroOpenOfficeIntegration@zotero.org/components/zoteroOpenOfficeIntegration.js" line: 62}]
I tried all advice I could find in the forums, but the problem persists. Java runtime environment is Sun's 1.6.0_27.
Java is activated in LibreOffice via the options-menu.
Thanks in advance for any clues. So far, I stick with RTF-scan (great to have that option); unfortunately, its functionality is still somewhat limited.
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
What error are you actually seeing on your screen?
Indeed, I have FF-plugin as well as the standalone version of zotero installed; however, the problem also arises if I start only one instance of zotero (regardless whether this is standalone or the ff-plugin).
/etc/network/interfaces
when I tried to make network-manager care for the connections.
Hence the problem did not really occur on a "vanilla" installation of Debian -- my apologies!