Same problem for me with OO.org 2.0.4-ubuntu4.
I noticed a small difference in the error message for these two cases:
1. Start OO.org and open a file from passw-protected ftp
--> dlg with "general input/output error"
2. Run from cmdline: openoffice ftp://user:passw@host/file
This opens the file, it works.
Then open a file from the same ftp location using File->Open.
--> dlg with "Access to ftp://user@host/file was denied"
Notice that, again, the password is missing here.
I got these error message on the console/xsession-errors:
(nautilus:4202): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is probably a race-condition.
(soffice.bin:6857): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is probably a race-condition.
The former occurs a couple of time in ~/.xsession-errors. I haven't been able to reproduce them though.
Same problem for me with OO.org 2.0.4-ubuntu4.
I noticed a small difference in the error message for these two cases:
1. Start OO.org and open a file from passw-protected ftp
--> dlg with "general input/output error"
2. Run from cmdline: openoffice ftp://user: passw@host/ file host/file was denied"
This opens the file, it works.
Then open a file from the same ftp location using File->Open.
--> dlg with "Access to ftp://user@
Notice that, again, the password is missing here.
I got these error message on the console/ xsession- errors:
(nautilus:4202): libgnomevfs-WARNING **: gnome-vfs- monitor. c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is probably a race-condition.
(soffice.bin:6857): libgnomevfs-WARNING **: gnome-vfs- monitor. c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is probably a race-condition.
The former occurs a couple of time in ~/.xsession-errors. I haven't been able to reproduce them though.