Bugzilla – Bug 588480
Can't open remote files in Openoffice
Last modified: 2010-09-20 15:58:04 UTC
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Have openoffice 3.1.1 and samba shares set up between my Opensuse 11.2 desktop and wife and daughters widows7 notebooks. Can access everything perfectly over the shares except anything in Openoffice. When I try to open a file located on one of the two notebooks Openoffice gives the message "you can only select local files" Reproducible: Always
Sigh, bugzilla did not send mails around last weeks and we somehow missed this new bug. Mark, could you please provide more information? 1. What window manager do you use? (KDE4 or GNOME or ???) 2. Do you have the related OOo integration installed? (OpenOffice_org-kde4 for KDE4; OpenOffice_org-gnome for GNOME) 3. How do you exactly access the file? Do you mount the samba share to your linux system? Or do you try to unset the smb:// protocol Hmm, I am afraid that the smb:// protocol does not work in KDE4 because the support for KIO is missing there :-(
Using KDE 4.3.5 with the OOo kde4 integration installed. Usually access the fille simply by choosing "file open" and using the file manager to browse to the network / samba shares / documents folder on remote computer and opening the file. Id I brose to the remote folder using Dolphin and double click on the document file it opens a blank page in writer.
Roman, could you please look at it?
This is a known limitation. I have been thinking about how to allow remote files (i.e. what the kio slaves support) but have not come to a good solution as of yet. The problem is that the file doesn't exist locally, and thus the software must support some sort of protocols (whether that be cache or whatnot) to deal with moving the files back and forth.
You might take some inspiration in the GNOME integration. It somehow works there with the gnome-vfs and it might solve similar problems. Kendy might know some more details.
. *** This bug has been marked as a duplicate of bug 575182 ***