[Libreoffice-bugs] [Bug 54275] New: Unable to "Save As" on Samba, "Windows Share", gvfs created from Nautilus

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=54275

             Bug #: 54275
           Summary: Unable to "Save As" on Samba,"Windows Share",gvfs
                    created from Nautilus
    Classification: Unclassified
           Product: LibreOffice
           Version: 3.6.1.2 release
          Platform: All
        OS/Version: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Libreoffice
        AssignedTo: libreoffice-bugs at lists.freedesktop.org
        ReportedBy: joehahn at gmail.com


Created attachment 66352
  --> https://bugs.freedesktop.org/attachment.cgi?id=66352
Screenshots of errors

Unable to "Save As" on Samba,"Windows Share",gvfs created from Nautilus 

When trying to "Save As" to a "Windows Share" (gvfs) mounted with Nautilus in
Ubuntu, three errors occur.

- The file is not created.

- Error messages appear. 
-- "Error saving the document" "Nonexistent file"
-- "Error saving the document" "General Error." "General input/output error."

- Libreoffice can no longer be closed from the menu and must be Force Quit.
Most menu features are now greyed out, including "About".

We are able to open and save existing files on the share with Libreoffice.
Other applications, such as Sublime Text, are able to create new files and Save
As.

It also appears that after we force quit, it leaves the lock files in place,
which LO does initially successfully create on the share when opening an
existing file. Does this mean that the file creation process for LO's lock/temp
files is entirely different from how it access the share when trying to create
or save normal files?

This appears to have been a problem for a long time, specific to shares mounted
with these methods.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.