Bug 74675

Summary: "Open File" does not work
Product: LibreOffice Reporter: Pepino <Pepino.Escaso>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: major CC: barta
Priority: medium    
Version: 4.2.0.4 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Pepino 2014-02-07 14:12:29 UTC
After installing the new release (4.2.0.4), I cannot open existing files in LibO on my Windows 7 pro machine. Instead, I have do do a workaround:
- new text document
- then use the menu command "open file", which then opens a new window.
On an XP computer, everything works fine.
Comment 1 tommy27 2014-02-15 16:08:31 UTC
was a clean new install or did you overinstall the 4.2.0 on top of a previous LibO release?
Comment 2 Pepino 2014-02-15 16:26:15 UTC
(In reply to comment #1)
> was a clean new install or did you overinstall the 4.2.0 on top of a
> previous LibO release?

I installed over a previous LibO, 4.1.4. Should I de- and re-install?
Comment 3 tommy27 2014-02-15 16:31:20 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > was a clean new install or did you overinstall the 4.2.0 on top of a
> > previous LibO release?
> 
> I installed over a previous LibO, 4.1.4. Should I de- and re-install?

you could try and see if it solves the issue.

basically you are saying that double clicking on an .odt file doesn't open it in LibO? what exactly happens when you do so?
Comment 4 Pepino 2014-02-16 11:42:12 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > was a clean new install or did you overinstall the 4.2.0 on top of a
> > > previous LibO release?
> > 
> > I installed over a previous LibO, 4.1.4. Should I de- and re-install?
> 
> you could try and see if it solves the issue.
> 
> basically you are saying that double clicking on an .odt file doesn't open
> it in LibO? what exactly happens when you do so?

Now I de-installed LibO 4.2.0 and tried to re-Install. I tried 3 times: The installation stopped without success an without changing the system.
After that, I installed the 4.1.4 version and everything is o.k.
Then I installed the new 4.1.5 version over the 4.1.4, and it is still o.k.
So, I think I will keep that version.
Comment 5 tommy27 2014-02-16 12:49:30 UTC
Ok. stick with 4.1.5 and wait when 4.2.1 comes out if you still experience the same issue.

let's set status to NEEDINFO, revert it to UNCONFIRMED if 4.1.2 still gives you troubles once is out.
Comment 6 QA Administrators 2014-09-03 21:32:47 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 7 QA Administrators 2014-10-05 22:59:54 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO