Bug 63215

File opened correctly under Win8 Std en_UK x64 using LO 4.0.2.2

Got a warning message when opening the file:

"Document file 'XYZ%20QUALIFICATION%20SUPPLEMENT%20with%20corrections%20(1).docx' is locked for editing by:
Unknown User
Open document read-only or open a copy of the document for editing."

Choosing either option opened the file without any problems.

Can you provide more details? Is the LO interface set to any particular language other than English?

Using Linux Mint 13 and LO 4.0.2.1 from the LO Ubuntu repository I found the document opened correctly repeatedly. I did not get any warnings.

The document also opened correct using Calligra Words, version from the standard repository.

I do not see the crash with 4.0.2.2 on Windows 7 Professional. I also do not see there any warning. It opens just fine.

Could you please provide more information?

1. What localizations you have installed and what localization is use?
2. Do you have any 3rd party extension? Which one?
3. Does it help you to reset user configuration? [1]

[1] See https://wiki.documentfoundation.org/UserProfile#Resetting_the_user_profile

1. None
2. None
3. No, already tried. Document did open in Apache OO.

http://www.linkedin.com/in/parjlarsson                                              

On Apr 8, 2013, at 6:21, bugzilla-daemon@freedesktop.org wrote:

> Comment # 3 on bug 63215 from Petr Mladek
> I do not see the crash with 4.0.2.2 on Windows 7 Professional. I also do not
> see there any warning. It opens just fine.
> 
> Could you please provide more information?
> 
> 1. What localizations you have installed and what localization is use?
> 2. Do you have any 3rd party extension? Which one?
> 3. Does it help you to reset user configuration? [1]
> 
> [1] See
> https://wiki.documentfoundation.org/UserProfile#Resetting_the_user_profile
> You are receiving this mail because:
> You reported the bug.

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

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

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