The problem still exists in Ubuntu 13.10 (Linux 3.11.0-20-generic
x86_64) with gedit 3.8.3-0ubuntu3

My fstab:
//ourserver.local/myshare   /mnt/mymount   cifs    
uid=1001,file_mode=0600,dir_mode=0700,credentials=/myhome/.smbcredentials,iocharset=utf8,sec=ntlm,nounix
   0 0

I found an interesting link which assumes that the reason is a time-
synchronization problem:
https://forums.gentoo.org/viewtopic-t-495454-start-0.html#3567475. This
makes sense since our NAS is a Netgear ReadyNAS with a time drift of
~20s per day and NTP doesn't seem to work on it. Latter means that I
cannot do any serious tests on it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/34813

Title:
  gedit fails to save files over smbfs/cifs

Status in Light-Weight Text Editor for Gnome:
  Confirmed
Status in SambaServer:
  Invalid
Status in SSHFS Mounter:
  Confirmed
Status in “gedit” package in Ubuntu:
  Triaged
Status in “gedit” package in CentOS:
  New

Bug description:
  Saving files over a cifs/smbfs server doesnt work.  You can open file,
  edit then save perfectly.  But repeated saves after give you this
  error:

  "The file /home/dhonn/website/arrays.php has been modified since
  reading it.  If you save it, all the external changes could be lost.
  Save it anyway?"

  The think is lying to me because I havent made any external changes.

  When I click "Save Anyway", i get this error:

  "Could not save the file /home/dhonn/website/arrays.php."

  But on the third try it works just fine.

  Here are the error messages, btw there are also GUI glitches too:
  http://dhonn.com/images/gedit-0.jpg
  http://dhonn.com/images/gedit-1.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/34813/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to