Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: gvfs (Ubuntu Hardy)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
The NAS shares are mounted using fstab. Here's the relevant line from
fstab for one of the NAS shares:
//nest/home /media/Home cifs
uid=1000,rw,iocharset=utf8,username=**,password=*** 0 0
My OO version is the same.
One difference is that I used an .ods file
--
[gvfs] [smb]
Can you try a test with my Polly2.odg? Copy it onto your NAS share,
open it in OOo, delete two frames, save it. Close OOo. Open the saved
file from Nautilus by double clicking it. Is it OK?
Do you know what OS your NAS box uses?
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
Yikes. I believe that as of the recent fuse/samba update (this AM),
this bug is back in Karmic with OO 3.1.
Open a spreadsheet from an NAS in OO
Save the spreadsheet back to the NAS, (there seems to be a short freeze after
what looks in OO like a normal save) quit OO
Re-Open the spreadsheet in
I have tested using Karmic and OpenOffice.org-core 1:3.1.1-5ubuntu1
(taken from the Help About box). My standard test using the file
Polly2.odg (see #14 above) opened from a Windows XP SP3 network share,
deleted 2 frames and saved back to the network share. I did not find a
problem.
I did the
After a month testing with more than 30 PCs :
The following constellation has solved my problem:
- Use samba share for windows client
- Use NFS 4 for ubuntu (mine are hardy), don't use NFS under v.4 file locking
seems to be a problem otherwise
- Use OO 3.1.x to allow correct file locking
This bug was about having problems with smb when using gvfs. You can
always use real samba mounts using mount and/or /etc/fstab instead of
the Places-Connect to Server.
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
You received this bug
No, OO win pcs using samba to a FC server works perfectly
OO under Ubuntu using NFS works perfectly
That is how we are mixing machines here in Mercury
Regards MOB
Gundalf wrote:
Thanks Mark (MOB),
But by letting the Win-PCs accessing OO files through Samba - then the same
corrupted file
You could do what I have done and that was install a server as a central
sharing point. The linux pcs access the server using NFS and the XP
machines via samba. Perhaps I shouldnt say it b(here!) - but I used FC
for the server! All has been well ever since.
MOB
On Tue, 2009-06-23 at 05:34 +,
Thanks Mark (MOB),
But by letting the Win-PCs accessing OO files through Samba - then the same
corrupted file problem stays?
Sorry for my bad english.
Gundalf
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
You received this bug notification
Ooops, I've just understood your point.
Of course win + OO + Samba - won't cause file corruption right? Got to test it.
Thanks Mark,
Gundalf
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
You received this bug notification because you are a
Oh no,
We've moved more than 30 PCs to Hardy in our offices in Indonesia because of
the LTS term for more than a year. Recently the problem with corrupted OO
files starts to haunts our system. Due to the necessity to use autocad, visio
and other tax programs we must keep 8 PCs running on XP.
Is there any chance of a backport to Intrepid?
IMHO a backport to Hardy should also be considered
because this bug is problematic in networking environments.
Lets say in environments where LTS versions are preferred.
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
Its already in the ppa for Intrepid but gvfs fuse is broken in Intrepid
so it doesn't actually work. For Hardy there is no GIO support as far as
I can tell so I had to disable the patch for it, even if it did work
gvfs fuse fixes would have to be backported to Hardy as well. The gvfs
maintainer
I confirm that this bug is fixed for me after upgrading to Jaunty.
Now OpenOffice files open correctly on a samba share.
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
You received this bug notification because you are a member of Ubuntu
Desktop
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: gvfs (Ubuntu)
As far as I can tell, the original bug reported by Sophie is fixed in
Jaunty with OOo 3.0.1. I have conducted my standard test saving a large
odg file to a an XP share and re-opening it.
Thanks to all
Tony
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
As far as I can tell, the original bug reported by Sophie is fixed in
Jaunty with OOo 3.0.1. I have conducted my standard test saving a large
odg file to a an XP share and re-opening it.
Thanks to all
Tony
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
could you try on current jaunty and describe what gvfs issue you still
get there exactly?
** Changed in: gvfs (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
[gvfs] [smb] Damaged OpenOffice files
could you try on current jaunty and describe what gvfs issue you still
get there exactly?
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
the hardy openoffice version doesn't use gvfs does it?
** Changed in: gvfs (Ubuntu Hardy)
Importance: Undecided = Low
** Changed in: gvfs (Ubuntu Hardy)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
** Changed in: openoffice.org (Ubuntu)
Status: Incomplete = Fix Released
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
I believe that this bug is essentially fixed in openoffice.org
1:3.0.1-5ubuntu1 in Jaunty as I have now turned off both gnome-vfs and
gio in OOo. OOo is now patched to use gvfs fuse which should work. There
are a few remaining bugs in gvfs fuse that cause saving not to work for
ftp/webdav but
Sorry , forgot to mention that my OOo version is:
OpenOffice.org-core 1:2.4.1-1ubuntu2.1
Installing smbfs 3.0.28a and mounting via CLI, is working.
(i.e. im unable to corrupt files during my tests)
However i'll have a hard time relying on the GUI/gvfs for attaching to any
SMB-share anymore..
I'm running HH 64bit ws _and_ HH 8.04.2 64bit as samba server.
I _am_ experiencing the problem.
As much as the problem is reckognized , all i can see is that i'll have
to use a kernel not for 8.04
This isn't the sort of thing You'd expect when upgrading from Fedora WS and
CentOS server to
I am seeing file corruption when copying from a Windows NT4 server to an
up-to-date version of Jaunty with a 2.6.29-rc2 kernel (but also using
the stock Jaunty kernel) using gvfs. The files in question have NOTHING
to do with OOo, they are JPEG's from a digital camera. Files are
reliably corrupted
** Summary changed:
- Damaged OpenOffice files from samba shares
+ [gvfs] [smb] Damaged OpenOffice files from samba shares
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
You received this bug notification because you are a member of Ubuntu
** Changed in: openoffice.org (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Chris Cheney (ccheney)
Status: Confirmed = Triaged
Target: None = ubuntu-9.04-beta
--
[gvfs] [smb] Damaged OpenOffice files from samba shares
https://bugs.launchpad.net/bugs/267371
28 matches
Mail list logo
