Can't open files on WebDAV share

Bug #484855 reported by Bruno Girin
148
This bug affects 25 people
Affects Status Importance Assigned to Milestone
OpenOffice
New
Unknown
libreoffice (Ubuntu)
Fix Released
Undecided
Björn Michaelsen
openoffice.org (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

I have a home server running Ubuntu 8.04 (Hardy) that shares a folder using WebDAV. I can navigate the folder using Nautilus on a client laptop running 9.10 (Karmic) and open any file by double-clicking on them, except for OpenOffice files, in which case I get an error message (see attached screenshot). I also tried from the File -> Open menu item in OO.o with identical results: same error message.

Steps to reproduce #1 - via Nautilus
- Create a shared directory on a server, share it through WebDAV
- Connect to the shared directory using a client machine and add that share to the Nautilus bookmarks
- Open the shared drive through Nautilus
- Navigate to a directory
- Double-click on a non-OO.o file (e.g. a PDF or JPG file)
- The file opens normally
- Double click on an OO.o file (e.g. a .ods OpenOffice Calc or .odt OpenOffice Writer file)

Steps to reproduce #2 - via File -> Open
- Create a shared directory on a server, share it through WebDAV
- Connect to the shared directory using a client machine and add that share to the Nautilus bookmarks
- Start OpenOffice
- Select File -> Open
- Navigate to a directory
- Select an OO.o file to open (e.g. a .ods OpenOffice Calc or .odt OpenOffice Writer file)

Expected behaviour
- The selected OO.o file opens in the relevant OO.o application

Actual behaviour
- An error dialogue with the message: General input/output error while accessing /home/user/.gvfs/WebDAV on host/file.ods (see attached screenshot)

ProblemType: Bug
Architecture: i386
Date: Wed Nov 18 15:38:39 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: openoffice.org-core 1:3.1.1-5ubuntu1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: openoffice.org
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Bruno Girin (brunogirin) wrote :
Revision history for this message
Xabi Ezpeleta (xezpeleta) wrote :

I have the same problem in differerents computers with Ubuntu 9.10

Revision history for this message
pdf (pdffs) wrote :

Ditto

Revision history for this message
Bruno Girin (brunogirin) wrote :

@Xabi, @sPOiDar: can you confirm the OS versions you have both on the file server and client please? That should provide extra information that may be useful to developers.

I am confirming the bug report based on the independent confirmation in the comments.

Changed in openoffice.org (Ubuntu):
status: New → Confirmed
Revision history for this message
Bruno Girin (brunogirin) wrote :

Some additional information: the problem seems to be limited to WebDAV. Opening a file on the server via SFTP (SSH), works fine both via File -> Open in OO.o and by double-clicking on the file.

Revision history for this message
Xabi Ezpeleta (xezpeleta) wrote :

@Bruno

File server:
- OS: Debian GNU/Linux 5.0
- Kernel: 2.6.26-1-686
- Server software: Alfresco 3.1 Enterprise

Client:
- OS: Ubuntu 9.10
- Kernel: 2.6.31-17-generic #54-Ubuntu SMP

From Mac and Windows there's no problem, so the server is running fine...

Changed in openoffice:
status: Unknown → New
Revision history for this message
Greg Brown (paddler-poet) wrote :

I have this same problem with my work WebDAV. If I rename an ODT file to a DOC file, it opens fine, but if I try to open an ODT file as-is, it fails. It won't even let me download any ODT to my local client--the error message reports that the file was "not found." Again, renaming the file to DOC or PDF allows me to download it, though in the case of PDF I obviously have to change the extension back before the file opens properly.

This is a huge irritation and I hope we can find a solution. I don't know how to begin looking for a solution myself, being only a few months into Ubuntu. (Otherwise, it's been a great experience.)

Revision history for this message
Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote :

Does anyone know a workaround? Does it work if we mount the webdav in the fstab?

Revision history for this message
Chris Cheney (ccheney) wrote :

I think this is related to gvfs bug https://bugzilla.gnome.org/show_bug.cgi?id=522532

Chris Cheney (ccheney)
tags: added: karmic
Revision history for this message
rothchild (marc-rothera) wrote :

I'm having this issue with Lucid too.
Not sure what the server setup is (because it belongs to work). As noted it only seems to be files opening with OpenOffice, other files (such as .jpg) open fine.

As a workaround I can copy the files to my local machine, edit and copy back but it's not ideal.

Revision history for this message
rasos (rasos) wrote :

Problem confirmed on Ubuntu 10.04 Lucid with OpenOffice 3.2 client; server is Ubuntu Lucid with SabreDav (as part of GroupOffice).

Changed in openoffice.org (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote : migrating packaging from OpenOffice.org to Libreoffice

[This is an automated message.]
There are no new official OpenOffice.org releases in Ubuntu packaging anymore => Won't Fix

If the problem persists, please mark this bug as "also affects project Libreoffice" or "also affects distribution Libreoffice (Ubuntu)" if that has not happened already.

Please leave references to upstream OpenOffice.org bugs in place to allow cross pollination.

penalvch (penalvch)
summary: - OpenOffice can't open files on WebDAV share
+ Can't open files on WebDAV share
Revision history for this message
penalvch (penalvch) wrote :

Bruno Girin, Ubuntu 9.10 reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with a Xubuntu client 11.10 and was unable to, given the information you've provided. Please upgrade and test.

CLIENT:
lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10

apt-cache policy thunar
thunar:
  Installed: 1.2.3-0ubuntu1
  Candidate: 1.2.3-0ubuntu1
  Version table:
 *** 1.2.3-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages
        100 /var/lib/dpkg/status

apt-cache policy davfs2
davfs2:
  Installed: 1.4.6-1ubuntu3
  Candidate: 1.4.6-1ubuntu3
  Version table:
 *** 1.4.6-1ubuntu3 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages
        100 /var/lib/dpkg/status

apt-cache policy libreoffice-calc
libreoffice-calc:
  Installed: 1:3.4.3-3ubuntu2
  Candidate: 1:3.4.3-3ubuntu2
  Version table:
 *** 1:3.4.3-3ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
        100 /var/lib/dpkg/status

SERVER:
lsb_release -rd
Description: Ubuntu 8.04.4 LTS
Release: 8.04

apt-cache policy apache2
apache2:
  Installed: 2.2.8-1ubuntu0.21
  Candidate: 2.2.8-1ubuntu0.21
  Version table:
 *** 2.2.8-1ubuntu0.21 0
 500 http://us.archive.ubuntu.com hardy-updates/main Packages
 500 http://security.ubuntu.com hardy-security/main Packages
 100 /var/lib/dpkg/status
     2.2.8-1 0
 500 http://us.archive.ubuntu.com hardy/main Packages

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Revision history for this message
Mario Moder (oddfellow) wrote :

This bug still exists in Ubuntu 11.10 (LibreOffice 3.4.4) and I can reproduce it reliably with the authors original description.

My guess: It is a LibreOffice <-> GVFS/GIO integration bug but where should it be reported? Gnome? Ubuntu? LibreOffice? OpenOffice??

Revision history for this message
penalvch (penalvch) wrote :

Marking New based on comment #14.

Changed in libreoffice (Ubuntu):
status: Incomplete → New
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

This should be fixed in LibreOffice 3.5.0 (even the beta) that is now in precise by changing to GIO.

Changed in libreoffice (Ubuntu):
milestone: none → ubuntu-12.04
assignee: nobody → Björn Michaelsen (bjoern-michaelsen)
Changed in libreoffice (Ubuntu):
status: New → Fix Released
Revision history for this message
rothchild (marc-rothera) wrote :

Just upgraded to Precise and this now works as expected when you use 'file / open' from within Libre Office, but I get a 'general I/O error' when just double clicking the remote file in the file browser. (Libre office starts to fire up but then closes with the error message.

Revision history for this message
ZenGuy (bstone) wrote :

Confirming rothchild's comment that double clicking in file browser still errors, but documents can be opened from within LibreOffice. I'm running 12.04 desktop and server with Owncloud 4.1 installation.

Revision history for this message
Simplehuman (simplehuman) wrote :

Libreoffice 3.5.4 - problem is still actual . Ubuntu 12.04 x64

Revision history for this message
Philipp Gassmann (phiphi.g) wrote :

Probably Related: Similar Bug with smb/Cifs and GVFS with i/o error, where a fix is released and working.

https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/792622

Revision history for this message
Thomas Kregelin (tkr) wrote :

The error still persists with respect to nautilus.

Trying to open a libreoffice file on a webdav directory using nautilus results in:

General input/output error while accessing ...

Revision history for this message
beccon (beccon) wrote :

It might have to do with the password vault LibreOffice implements.

When I open a file on a Webdav share - Libreoffice asks for a password for a keyring (which is not the one of Gnome it runs on). An attempt to open the file from outside e.g. from Nautilus results in an error with no password dialog.

The question remains why LibreOffice does not use the gvfs / Kioslaves when on Gnome/KDE but instead reinvents the wheel?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.