Bug 895690 - Libreoffice causing errors when SAVING files by gvfs-mount (Samba)
Summary: Libreoffice causing errors when SAVING files by gvfs-mount (Samba)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 18
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Stephan Bergmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 926001 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-15 19:18 UTC by Grosswiler Roger
Modified: 2013-08-21 06:24 UTC (History)
8 users (show)

Fixed In Version: libreoffice-3.6.5.2-7.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-24 22:49:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Grosswiler Roger 2013-01-15 19:18:25 UTC
Description of problem:

When saving a file in libreoffice, using the mounted gvfs-path, the following error occurs. Libreoffice cannot get closed then and needs to be killed in the shell.

Errors:
"Error saving this document: the file doesn't exist" and then after OK, this
"Error saving this document: general error. general i/o-error"

-> Saving to /run/user/[userno.]/gvfs/ works!!

Version-Release number of selected component (if applicable):
Version 3.6.3.2 (Build ID: 3.6.3.2-8.fc1


How reproducible:
Always

Steps to Reproduce:
1. Open Libreoffice, create any new file
2. save file to a share using gvfs (preferable on a samba-share)
3. Get the error
  
Actual results:
Cannot save file to this path.


Expected results:
Saving File to the Path indicated in the save-as-path-dialogue to the left.


Additional info:

Comment 1 Caolan McNamara 2013-02-28 15:32:35 UTC
caolanm->sberg: is the a dup of the X-GIO-NoFuse=true issue or something else ?

Comment 2 Stephan Bergmann 2013-02-28 15:54:23 UTC
Does the problem go away when you select "Tools - Options... - LibreOffice - General - Open/Save dialogs - Use LibreOffice dialogs" first?

Comment 3 Grosswiler Roger 2013-02-28 17:10:07 UTC
i have changed this in libreoffice, now 2 situations occure:

Prerequisite: i saved the samba-share as a favourite within libreoffice in the open/save-dialogue

i always open a file within nautilus and want to save it.

1) i save clicking on the favourite folder and type a filename: The error comes up as described above

2) i use the path, which libreoffice seems to have and points to the local resource /run/user/100n/gvfs/[share] - this works

and if i open the file within libreoffice without nautilus, both described situations

1) the same, it won't save

2) the same, it saves.

it works always using the path from /run...

Comment 4 Grosswiler Roger 2013-02-28 17:11:06 UTC
and no, it doesn't go away.

Comment 5 Stephan Bergmann 2013-03-13 11:08:02 UTC
(upstream fix is <http://cgit.freedesktop.org/libreoffice/core/commit/?id=8722f0e7ef690205d042c8a6b1fdf342a34ecbe1> "rhbz#895690: Make GIO UCP less brittle, so saving docs works again")

Comment 6 Fedora Update System 2013-03-14 10:39:16 UTC
libreoffice-3.6.5.2-7.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/libreoffice-3.6.5.2-7.fc18

Comment 7 Fedora Update System 2013-03-15 00:08:46 UTC
Package libreoffice-3.6.5.2-7.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreoffice-3.6.5.2-7.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3868/libreoffice-3.6.5.2-7.fc18
then log in and leave karma (feedback).

Comment 8 Grosswiler Roger 2013-03-15 13:40:10 UTC
Installed, tested and left posivite karma.

Thx!

Comment 9 Fedora Update System 2013-03-15 20:07:45 UTC
libreoffice-3.6.5.2-8.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/libreoffice-3.6.5.2-8.fc18

Comment 10 Fedora Update System 2013-03-24 22:49:44 UTC
libreoffice-3.6.5.2-8.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Stephan Bergmann 2013-03-25 13:26:20 UTC
*** Bug 926001 has been marked as a duplicate of this bug. ***

Comment 12 Trever Adams 2013-03-26 10:37:20 UTC
On problem with this fix, in the past I could use the recent list to load files on a gvfs mount and it would automount it (ask for a password if needed). With this fix, that doesn't work.

I do not know if you can cause the mount from file/open or not. I have had to just use nautilus to go to the mount and get it mounted, then the recent list works.

Comment 13 Stephan Bergmann 2013-03-26 14:38:03 UTC
(In reply to comment #12)
> On problem with this fix, in the past I could use the recent list to load
> files on a gvfs mount and it would automount it (ask for a password if
> needed). With this fix, that doesn't work.

Are you sure that this got broken with this fix (i.e., did it still work with libreoffice-3.6.5.2-6.fc18)?

Comment 14 Trever Adams 2013-03-30 11:44:55 UTC
I am not sure what version it worked with. It was working with several versions post Fedora 18 release. It doesn't work now. It would be helpful if it did, but if it can't be fixed, I can understand that.

Comment 15 Stephan Bergmann 2013-08-21 06:24:55 UTC
(In reply to Trever Adams from comment #12)
> On problem with this fix, in the past I could use the recent list to load
> files on a gvfs mount and it would automount it (ask for a password if
> needed). With this fix, that doesn't work.
> 
> I do not know if you can cause the mount from file/open or not. I have had
> to just use nautilus to go to the mount and get it mounted, then the recent
> list works.

Turns out I forgot about this but later re-discovered the problem and fixed it on upstream master towards LibreOffice 4.2 as <http://cgit.freedesktop.org/libreoffice/core/commit/?id=4d8bf09305fc4e4bd652187aac0a02398413ba65> "Always try to mount in gio::Content::getGFileInfo" (no idea when exactly it got broken, though).  Anyway, will be fixed in the next libreoffice-4.1.1.1-3.fc19.


Note You need to log in before you can comment on or make changes to this bug.