Created attachment 365225 [details] OpenOffice Crash Log Description of problem: ======================= Openoffice (any program) crashes when saving a document. (on SMB shares) **** The crash happens if you're saving on an SMB share (a samba server in my case). **** The crash happens only if you're saving an already existing document. The initial save works. In the same situation previous versions of Oo would issue a waring about not being able to save a backup and then the file would get saved the next time you hit the "save" button. This was a known problem. With 3.1.1 you simply get a crash instead. Versions: ========= openoffice.org-base-3.1.1-19.2.fc11.i586 Crashlog from openoffice: ========================= See the Attached File How reproducible: ================= Always Steps to Reproduce: =================== 1. Create a document. Or open an existing one. 2. If you Save it on an SMB share for the first time (and the file does not yet exist on the SMB share) it should work 3. If the file already exists when you hit "Save", then Openoffice should crash Actual results: =============== Crash with pop-up "OOo has crashed! Paste this text into your bugreport" Expected results: ================= If not a flawless save, one would expect at least the old behaviour (with warnings etc). Additional info: ================ I mount my samba shares through fstab: ====================================== //smb/work /net/work cifs user=testuser,pass=testpass,domain=WORKGROUP,uid=testuser,gid=users 0 Excerpt from my samba config: ============================= [global] time server = Yes unix extensions = No ^^^^^^^^^^^^^^^^^^^^ domain logons = Yes preferred master = Yes domain master = Yes create mask = 0770 directory mask = 0770 delete readonly = Yes dos filemode = Yes [work] path = /work admin users = testuser read only = No force create mode = 0770 force directory mode = 0770
dtardon->red: could you give us result of stat -Z /work/whatever/the/file/name.is and stat -Z `dirname /work/whatever/the/file/name.is` ? (subsitute the made up path for a real path)
> dtardon->red: could you give us result of ReD -> dtardon: I guess not. Selinux is disabled.
dtardon->red: remove the '-Z' option, then (though i always thought that worked without selinux too)
This is from my machine and the file is the latest I worked on. == $ stat '/net/programmi/Documenti/Lettere/Palenzona/Riscaldamento 2009.odt' File: `/net/programmi/Documenti/Lettere/Palenzona/Riscaldamento 2009.odt' Size: 35876 Blocks: 72 IO Block: 16384 regular file Device: 18h/24d Inode: 6801138 Links: 1 Access: (2767/-rwxrwSrwx) Uid: ( 500/ davide) Gid: ( 100/ users) Access: 2009-10-19 10:58:45.052294000 +0200 Modify: 2009-10-19 11:20:49.435843000 +0200 Change: 2009-10-19 11:20:49.435843000 +0200 == $ stat /net/programmi/Documenti/Lettere/Palenzona File: `/net/programmi/Documenti/Lettere/Palenzona' Size: 0 Blocks: 0 IO Block: 16384 directory Device: 18h/24d Inode: 6800243 Links: 1 Access: (0777/drwxrwxrwx) Uid: ( 500/ davide) Gid: ( 100/ users) Access: 2009-09-11 12:29:11.296133000 +0200 Modify: 2009-10-19 11:35:16.672051600 +0200 Change: 2009-10-19 11:35:16.672051600 +0200 ADDITIONAL NOTE: I noticed that the first "save" after recovering the documents from the crash works.
For you reference: Above I mistakenly documented the configuration of the SMB share [work] instead of [programmi]. Anyway they are identical. =========== [programmi] path = /programmi admin users = davide read only = No force create mode = 0770 force directory mode = 0770 ===========
And this one is mounted as: //smb/work /net/work cifs user=davide,pass=*******,domain=WORKGROUP,uid=davide,gid=users 0
ok, reproduced
Thanks! BTW, has anyone got any thoughts for a temporary workaround?
*** Bug 529915 has been marked as a duplicate of this bug. ***
No such reports ever until recently and then a few come along together ?, hmm did something get updated recently which has trigged this
Yes, this bug is still replicating.
Is this dying *inside* a syscall, or is there a previous syscall which is returning an error that we're ignoring or something. i.e. is this our fault or can a small standalone demo be created that demonstrates samba client/server bustage ?
dtardon->caolanm: As I said in the upstream bug, I think the problem is in mmap. I've been able to get a crash on SIGBUS by truncating the source file, but AFAIK that's documented behaviour... I.e. compile the following attachment and run it as ./save -t /source/file /destination/file (it crashes on copying from anywhere, not just from samba share, of course...)
Created attachment 369037 [details] standalone testcase
Well, lets try the current upstream idea on this one, minus the hackery to detect a bad mmap and just use read/write. Will try that for >= 3.1.1-19.11.f11
openoffice.org-3.1.1-19.11.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/openoffice.org-3.1.1-19.11.fc11
openoffice.org-3.1.1-19.11.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update openoffice.org'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-13396
The same problem happens with openoffice.org-base-3.1.1-19.14.fc12.i686. What is strange is that abrt doesn't catch it.
(In reply to comment #18) > The same problem happens with openoffice.org-base-3.1.1-19.14.fc12.i686. > What is strange is that abrt doesn't catch it. Same for me on FC12 x86_64. And OOo doesn't show me the crash dialog, it just "disappears"
openoffice.org-3.1.1-19.12.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/openoffice.org-3.1.1-19.12.fc11
openoffice.org-3.1.1-19.12.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
Created attachment 397120 [details] Error Dialog OK. I'm testing the latest OpenOffice on Fedora 12 and the behaviour has changed. Now every time I try to save a modified document on an SMB share, this message pops up and nothing get saved. Versions: openoffice.org-base-3.1.1-19.26.fc12.i686 openoffice.org-calc-3.1.1-19.26.fc12.i686