Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 119978

Summary: ooo-1.1.1 requesting stuff from 1.1.0
Product: [Fedora] Fedora Reporter: Sammy <umar>
Component: openoffice.orgAssignee: Dan Williams <dcbw>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: santiago_erquicia
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-04-10 18:43:15 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:
Bug Depends On:    
Bug Blocks: 114961    

Description Sammy 2004-04-04 15:45:33 UTC
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux; X11; en_US, en) (KHTML, 
like Gecko) 
 
Description of problem: 
openoffice version 1.1.1-1 installs and works fine for viewing 
files BUT when I try to save a presentation that I opened I get error 
messages telling me that openoffice could  not find some files, where 
the path of the files point to /usr/lib/ooo-1.1.0 directory. The new 
ones seem to be in ooo-1.1 directory. If I make a logical link from 
1.1.0 to 1.1 then everything works fine. 
 
Version-Release number of selected component (if applicable): 
openoffice.org-1.1.1-1 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1.install openoffice.org-1.1.1-1 
2.open a presentation and make a small change 
3.try to save 
     
 
Additional info:

Comment 1 Sammy 2004-04-05 14:04:55 UTC
It looks like if one clears the ooo user directory before starting 
oo-1.1.1 than the problem does not exist. 

Comment 2 Dan Williams 2004-04-06 17:32:19 UTC
Fix will be in 1.1.1-2

Comment 3 Bill Nottingham 2004-04-06 20:11:32 UTC
*** Bug 120013 has been marked as a duplicate of this bug. ***

Comment 4 Dan Williams 2004-04-10 18:43:15 UTC
Fixed in 1.1.1-2