Issue 70310 - Paths go wrong in update
Summary: Paths go wrong in update
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-11 14:54 UTC by magi
Modified: 2006-12-19 15:18 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description magi 2006-10-11 14:54:07 UTC 
My paths were as follows in OOo 2.0.3:

  Home dir: /home/magi/texts
  Templates: /home/magi/texts/templates

After updating to 2.0.4rc3, they suddenly changed as follows:

  Home dir: /home/magi/texts/texts/
  Templates: /home/magi/texts/texts/templates

The same occurred on two different machines. Also, opening a new Writer document
displayed an error box, because it could not find the custom default template. 

On the other machine, I could not get the templates directory to work in
creating a new document from template, even after correcting the path. This is
strange, because it worked just fine on the other machine.

OOo was installed from OOo_OOD680_m5_LinuxIntel_install_fi_deb.tar.gz (Finnish
version) to Kubuntu. Did not test with English version.
Comment 1 magi 2006-11-25 10:41:42 UTC 
This occurred again when updating to OOE680_m4 from 2.0.4 release build.

This possibly also caused corruption of all links to external images in Writer
to go wrong. It occurred once, but now it again works just fine. Possibly it was
the first document I opened, corrected the default path settings, and then the
image links broke. Not sure.

I'm using Finnish version from Pavel's builds under Ubuntu Linux. Don't know if
that matters.
Comment 2 thorsten.martens 2006-12-19 15:17:30 UTC 
Problem was reproducible and has already been fixed in a more recent build
Comment 3 thorsten.martens 2006-12-19 15:18:16 UTC 
closed