RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

2.6.10: data loss/corruption on remote filesystems

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
2.6.10: data loss/corruption on remote filesystems Michael Hofer 22 Nov 09:56
  2.6.10: data loss/corruption on remote filesystems bimbi 11 Mar 15:00
Michael Hofer
2010-11-22 09:56:34 UTC (about 14 years ago)

2.6.10: data loss/corruption on remote filesystems

Hi,

i'm using Gimp 2.6.10 on Ubuntu 10.10. When I save a Gimp file on my network share (Samba via gnome-vfs) it works, but when I save it a second time and reopen the file again, everything is lost - i just see an empty (transparent) canvas. There is no error message. It looks like I can avoid that problem, if I would save every change with "Save as ..." as a new file - which is not a feasible way in practice.

I could not reproduce the problem by saving a Gimp file to my local harddisc. So I've tested to save a file to a SFTP/SSH-remote drive (also via gnome-vfs). In that case - when I reopen the file - Gimp gives an error message, that the file is damaged and cannot be opened.

Until now, there have been no problems with other applications saving data via gnome-vfs and the latest Ubuntu updates are also applied to my system.

Has someone recognized similar problems? What can I do to localize the problem further? Any hints?

Thanks, Michael...

bimbi
2011-03-11 15:00:57 UTC (almost 14 years ago)
postings
1

2.6.10: data loss/corruption on remote filesystems

Same problem, ubuntu 10.10, I can't save over samba, all layers get lost when I do it. Only "solution" I found was using "save as"