Bug 108257
| Summary: | oo and loocking over nfs | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | ae |
| Component: | openoffice.org | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-02-27 16:45:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This happens because OOo is attempting to lock your ~/.recently-used file for reading/writing. When OOo freezes, can you check what programs have that file open using 'lsof' ? Please try current OOo 1.1.0, and reopen if problem still occurs |
Description of problem: ooffice fails to start for user whose home dir comes from solaris via nfs/nolock. (The nolock practice began as a workaround for a problem with wordperfect 8 multiuser.) OK for user whose home comes from ext3 file system. Version-Release number of selected component (if applicable): 1.1.0-2 How reproducible: always Steps to Reproduce: 1. xterm 2. $ ooffice 3. Actual results: endless (?) delay, no visible result Expected results: ooffice app opens Additional info: 1.1beta is OK. Dist is redhat 9 with patches to date, two processor.