*** This bug is a duplicate of bug 486443 ***
https://bugs.launchpad.net/bugs/486443
** Changed in: openoffice.org (Ubuntu)
Status: Incomplete => Triaged
** This bug has been marked a duplicate of bug 486443
[upstream] OOo can not save files to NAS cifs - needs nobrl or disable
loc
I can confirm, the "nobrl" option at mounttime is a workaround. With
this option i have no problems opening older office files on a CIFS
share.
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of U
If this does solve the problem its most likely a duplicate of the other
bug, but I will keep them separate for now. If it can't be fixed in OOo
upstream I will ping the samba maintainer.
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug
First tests look promising. I've informed my co-workers of this fix.
I'll keep you updated on issues found.
BTW: The man-page of mount.cifs says:
Do not send byte range lock requests to the server. This is
necessary for certain applications that break with cifs style
mandatory byte ran
Hi Chris,
I have to make further tests to confirm that all files work, but presently it
seems so.
Hilaire
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
hilaire,
So nobrl fixes the problem for you? If so does it also help you Mark
Schouten?
Chris
** Changed in: openoffice.org (Ubuntu)
Status: Fix Released => Incomplete
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notifica
Hi again,
Great news: I solved my problem! The nomand option is not valid for
cifs, you have to use nobrl
in fstab
//machine/partition/media/Sauvegardecifs
nobrl,credentials=/root/.smbcredentials,uid=1000,gid=100,rw,iocharset=utf80
0
with sudo mount
hila...@hilaire-desktop:
Sorry for the confusion.
I meant that I could open the file now, but couldn't before. Which
doesn't mean the problem is gone, it's just even more weird.
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a m
Hi,
I can confirm that the workaround proposed by Brian (i.e.mounting the share via
'Nautilus->places->network') works for me. I am still not able to make it work
when mounting using fstab nor sudo mount -t: it seems that options nomand and
nounix are not taken into account:
if I mount a partiti
Perhaps you confused me? You said this bug was different because it was
causing OOo to crash and then went on to say:
"BTW: I don't have a crashing Ooo now.."
So what exactly are you meaning?
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received t
Huh? Where's the fix than?
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
** This bug is no longer a duplicate of bug 486443
[upstream] OOo can not save files to NAS cifs
** Changed in: openoffice.org (Ubuntu)
Status: Incomplete => Fix Released
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug noti
*** This bug is a duplicate of bug 486443 ***
https://bugs.launchpad.net/bugs/486443
Sorry. But this bug can hardly be a duplicate of 486443. That bug is
about unable to save files to a nas. This bug is about Ooo *crashing*
while opening a file from a Samba share.
BTW: I don't have a crashing
*** This bug is a duplicate of bug 486443 ***
https://bugs.launchpad.net/bugs/486443
** This bug has been marked a duplicate of bug 486443
[upstream] OOo can not save files to NAS cifs
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received th
Right. Some more testing:
Test 1: Open an existing .odt from a CIFS share [1]
Result: OpenOffice crashes
Test 2: Open the same file from local disk
Result: OpenOffice works
Test 3: Create, Edit and Save a new file on a Samba-share
Result: OpenOffice works
Test 4: Open a file created with OO 3.1
I'm currently testing/debugging this.
I can write, edit and open small files, it seems. I'm testing with:
Client:
Ubuntu 10.04 AMD64, Desktop
Server:
Debian Sarge (yes, I know :)), Samba 3.0.14a-3sarge
I'll report later with more testing/debugging.
--
crashes opening network file, leaves lo
That bug was with 9.10 and 3.1.1, which worked OK here on the LAN. It
does have some similar characteristics, though. Interesting that it
showed with KDE but not Gnome. Maybe my using Gnome was why I didn't see
it. (potential experiment suggested in that, I wonder what the
difference is).
I see al
This bug looks like it might be a duplicate of bug 486443 which has an
upstream bug attached to it already. Does it seem related to you?
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
B
When I did my testing I did an open->edit->save trip with the two
methods I tried which worked.
I wrote the support to have OOo use gvfs-fuse instead of regular gvfs
and during that time noticed a lot of bugs in gvfs-fuse, most of which
related to OOo calling ftruncate (non 0) from what I recall.
It appears that this is a well known interaction between OOo 3.0 and
Samba related to file locking. There appears to be a bug here for an
earlier distribution and OOo 3.1 and also issues listed in the OOo
forums and buglists. It can cause a crash on load or it can cause
unspecific 'general IO error
I can't manage to reproduce this problem with samba 2:3.4.7~dfsg-
1ubuntu3 in Lucid for the server and client. I tried using nautilus
(gvfs-fuse) for the client connection and also did a client test using
mount.cifs and both worked fine for me. My test was saving to both an
ods and odt file on the
Same problem here, changed from autofs to manual mounting did not solve
the problem
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Given that Lucid is an LTS release, also targeted at 'the enterprises' I
think this bug should be marked 'important'.
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Several people in our office report similar problems.
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
** Changed in: openoffice.org (Ubuntu)
Status: New => Confirmed
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had exactly the same issue. 10.04LTS. One is a fresh install, second
is an upgrade from 8.04LTS.
Mount says //ks-eisfair/mew on /home/piotr/mew type cifs (rw,mand)
File permissions are 100755. Copy the to Desktop and back to NAS solves the
issue.
--
crashes opening network file, leaves lock f
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48225326/Dependencies.txt
--
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
27 matches
Mail list logo