Bugzilla – Bug 132317
OOo can't open or save files after online update to final version
Last modified: 2005-11-21 19:30:33 UTC
Today I installed the final version of OpenOffice by Yast online update (build 2.0.0.1). After rebooting the machine, OOo cannot open or save files any more! The following error message appears: "Allgemeiner Ein-/Ausgabefehler beim Zugriff auf <Filename>" (sorry, I have only the german message). When I try to save a newly created document the same error message appears. The error does not depend on file type, it does not even open simple .txt files! I am in despair, I have a lot of work to do and can not open my documents! PLEASE provide a working version of the OOo update as soon as possible! What shall I do now? Is there a way to deinstall the update and come back to the version originally provided on the 10.0 CD? (I cannot find this option in YOU.)
Just discoverd some more info on this bug: My home directory is mounted via NFS. Saving a file to the local /tmp directory works! So the bug description should be correctly: "OOo 2.0 final can not open and save files on NFS"
Looks similar to one of the bug that was fixed, https://bugzilla.novell.com/show_bug.cgi?id=104655
I have found the SAL_ENABLE_FILE_LOCKING switch in /usr/lib/ooo-2.0/program/soffice. After commenting this out opening and saving documents now works. So, there remains one thing to complain about: The prerelease version of OOo that is on the 10.0 CDs works on NFS without changes in the soffice script. Installing online patches via YOU (that I run automatically every day) should not break a working system. An online update should not make changes that prevent essiantial programs from working, and if it does, there should be a warning when running YOU (as it is done when updating the kernel).
Petr, can you look into this and reassign to the right person. Thankyou
I am not able to reproduce the bug. The default behavior of OOo regarding the file locking was not changed in OOo-2.0.0, final version, so the update should not cause such problems. Yes, there could be a bug but... Another possibility is that the NFS locking support broke down after the YOU update. Christoph, did you do a kernel update before of after the YOU update? Could you please check the file /var/log/messages if there are any meesages from rcp.lockd? Olaf, you have more experiences with the NFS related bugs. Do you know what would have happened with the NFS locking?
NFS file locking was broken in 10.0. You need a fixed kernel to make it work (see bug #128784). There's no official update kernel yet, but for the time being please use the 10.0-* kernels from ftp://ftp.suse.com/pub/projects/kernel/kotd
OK, I will close this bug for now. Feel free to reopen it if it won't be fixed by the kernel update.