Neo/J-1.1 (BUG) configuration of datasources can hang up

[Max_Barel]

This is not very easy to reproduce:
- "connect" to the last datasource. Here, last means in the datasource configuration dialog listing, not in the usage pane where listing is alphabetical. This test datatasource can be of any kind, even simple txt.
- then disconnect (ctrl-click) on the datasource name in the usage pane.
- then try to "manage datasource" on this very same one datasource.
- soffice.bin is now hung. The Java part of the app do respond to event, but the underlying code do not.
Killing soffice.bin is the only way out.
Other sequence of operation on the last datasource can lead to the same deadlock.

Please (Ed?): Give me back my login to bugzilla. As I reported in the relevant forum, it's now more than one month that I'm unable to login nor to register anew.

[pluby]

Max,

The bad news is that this bug also exists in OOo 1.1.2. But, after debugging this for a few hours this afternoon, I found the source of the problem and I have checked in a fix. I'll put the fix in the first patch.

It seems that every time you click on one of the data sources, the underlying OOo code tries to execute some program that it not shipped with OOo or Neo/J. That's not a big deal, but it seems that if a program tries to execute more than 5 or 10 non-existent executables, the next try will hang the program instead of just failing.

Fortunately, the solution is a simple one: don't try executing programs that don't exist.

Patrick

[Terry Teague]