The problem I have here, is that it is unclear to me _why_ the connect failed, and I prefer to find that out rather than work around any LibreOffice issues.
Because there are two cases to consider: - LibreOffice is not already running - LibreOffice is already running In the first case it's easy, we start our own listener. In the second, we have to instruct the existing LibreOffice to start listening. It would be interesting to know whether you already have LibreOffice running, or not. Then see what exactly happens and how we can improve this. It's possible that the initial attempt to start a listener did work,but the listener is not completely ready, yet accepting connections. Whatever is the case, I prefer not to work around it like e.g. cloudooo is doing. They actively monitor the process and kill it if it is a runaway or memory-leaking process. They also kill the process when it does not finish within a certain timeframe and then try again. This all looks very useful, but it's working around the problem, while my aim is to get LibreOffice fixed so we can depend on it better. If we mask the problem like cloudooo is doing, we are making the situation worse IMO. (Not that I understand why cloudooo is doing it and why it makes perfect sense to them !) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/759184 Title: unoconv 0.3 doesn't know how to work with libreoffice ("Unable to start listener") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unoconv/+bug/759184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
