Issue 56222 - Post Installation
Summary: Post Installation
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: *Testproduct
Classification: Test
Component: code (show other issues)
Version: OOo 2.0
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: not determined
Assignee: issues@test
QA Contact: issues@test
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2005-10-18 16:19 UTC by marianoi
Modified: 2006-12-01 14:09 UTC (History)
2 users (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 marianoi 2005-10-18 16:19:01 UTC 
Hello,

I am not sure if this is an issue, but it is certanly not very nice.

After I installed the RC3, I double clicked on an OOo document I had on the
desktop and Win did not recognized the program that opens such extension. So, I
ran OOo from the strat menu and the Windows config started. After finished, I
double clicked again and the file opened OOo. 

I think that it could be a good idea if by double clicking a file after
installing, windows openes the windowds configuration process that happens in
the first time we run OOo.

Cheers !

Mariano
Comment 1 atdsm 2006-06-02 14:02:59 UTC 
I can't confirm. I just did a fresh installation of 2.0.3RC5 on my Windows XP
machine (uninstall and reinstall), following these steps:

1) Create a new OOo text document on the desktop
2) Uninstall OOo via "Add/Remove Programs"
3) Reboot
4) Reinstall OOo from setup files
5) BEFORE running OOo for the first time, double click on text document (.odt)
on desktop.

Following these steps, Windows recognizes the .odt as an OOo document and runs
OOo correctly (for me at least). However, I didn't get the usual "first run"
screens, leading me to believe that OOo was not actually completely uninstalled
(configuration files were still floating around).

In any case, would you please confirm that you still have this problem with
newer versions of the installer? If so, could you narrow down the circumstances
and post a step-by-step procedure for confirming the bug?

Thanks,

Steve
Comment 2 atdsm 2006-12-01 14:08:21 UTC 
No further information received in several months. Since we are two revisions
further on now, I'm closing this as WORKSFORME. Please reopen (or request
reopen) if you are still experiencing the problem.

Thanks,

Steve
Comment 3 atdsm 2006-12-01 14:09:07 UTC 
Closed.