Bug 129484 - /usr/lib/openoffice has disappeared
Summary: /usr/lib/openoffice has disappeared
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-09 17:02 UTC by Tim Waugh
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 11:21:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Tim Waugh 2004-08-09 17:02:11 UTC
Description of problem:
Some documents that I have previously created using OpenOffice.org can
no longer be modified because of a BASIC path starting
"/usr/lib/openoffice".  An error dialog appeared, and clicking OK just
made the error dialog appear again.  This path no longer exists, but
creating a symlink to /usr/lib/ooo-1.1 works around the problem.

Version-Release number of selected component (if applicable):

How reproducible:
Don't know.

Comment 1 Dan Williams 2004-09-18 04:41:16 UTC
hmmm.  should have been fixed already.  Can you remove the symlink and
grep your ~/.rhopenoffice1.1 for "/usr/lib/openoffice" ?


Comment 2 Tim Waugh 2004-09-23 10:35:39 UTC
No output from 'find ~/.rhopenoffice1.1 -type f |xargs grep

I don't remember which document caused me to file this bug now. :-/  I
can't find one that causes the original problem anyway.

Comment 3 Dan Williams 2004-09-28 20:44:30 UTC
Hmm, in this case if we can't get the file causing the problem, we
can't really do anything about it...  The files we know about are
already modified to fix this in the startup script, but for any
additonal files we need the name.

If you grep your ~/.rhopenoffice directory for just "openoffice" what
do you get?

Comment 4 Tim Waugh 2004-09-30 11:21:41 UTC
Lots of things, but no suspicious pathnames.  I'm pretty sure this
problem is fixed, whatever it was.

Note You need to log in before you can comment on or make changes to this bug.