Bug 132317

Summary:	OOo can't open or save files after online update to final version
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Christoph Singer <cs>
Component:	OpenOffice.org	Assignee:	Petr Mladek <pmladek>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Blocker
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Christoph Singer 2005-11-04 14:50:22 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.)

Comment 1 Christoph Singer 2005-11-04 14:59:26 UTC

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"

Comment 2 M Nagashree 2005-11-07 06:00:54 UTC

Looks similar to one of the bug that was fixed,
https://bugzilla.novell.com/show_bug.cgi?id=104655

Comment 3 Christoph Singer 2005-11-07 09:20:49 UTC

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).

Comment 4 M Nagashree 2005-11-11 04:52:41 UTC

Petr, can you look into this and reassign to the right person.
Thankyou

Comment 5 Petr Mladek 2005-11-11 17:50:59 UTC

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?

Comment 6 Olaf Kirch 2005-11-14 12:08:29 UTC

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

Comment 7 Petr Mladek 2005-11-21 19:30:33 UTC

OK, I will close this bug for now. Feel free to reopen it if it won't be fixed by the kernel update.