Imagine you log on to the computer using the username "UserName". Now LibreOffice encounters an error and crashes. Then, on the next start, LO would run the document recovery (that would work in this case).
But if you logged off (before re-starting LO) and logged on again using another spelling of the username (e.g. "username") LO would also start the document recovery on launch. But now, an error message appears saying that another user had already opened the file. All attempts to recover the file will fail until you re-logged in using the same spelling of the username as you used when LO crashed.
Which Windows version?
We experienced this on Windows Server 2003 x64.
Set back to UNCONFIRMED because this bug report has not been confirmed independently.
Thank you for your understanding.
Best regards. JBF
Not a Bug. If you log with different names you are different users, the computer knows nothing about you, it know only the name of the session and the configuration attached to this session.
Best regards. JBF
No, JBF, you are wrong. The case is *NOT* that you have to login with different usernames, but with different *SPELLING* of the *SAME* username.
In Linux environments you are right, that usernames are case sensitive so that "UserName" and "username" are different users.
In Windows, usernames are case-in-sensitive and "UserName", "username" and "USERNAME" is always the same user with always the same configuration. And thats why LO correctly tries to recover files that crashed in a previous session - but always fails, if the name is spelled another way.
From what I can see this was never confirmed by QA team - moving to UNCONFIRMED to get their confirmation.
Clarify problem in Summary
Cannot reproduce as described.
(In reply to a07cd040897db54e103c from comment #0)
> Imagine you log on to the computer using the username "UserName". Now
> LibreOffice encounters an error and crashes. Then, on the next start, LO
> would run the document recovery (that would work in this case).
Full repro steps:
- Log on with your username as lower case (e.g. "tinnedbeef")
- (To simulate crashing) Open a file for editing, then kill the LibreOffice process.
- Log back on with CamelCase in your username (e.g. "TinnedBeef")
- Open LibreOffice.
RESULT: An error message appears saying that another user had already opened the file. All attempts to recover the file will fail.
EXPECTED: LO will start the document recovery on launch.
WORKAROUND: Log back in using the same character-case in the username as was used when LO crashed.
Robinson, are you confirming the bug yourself (in this case status should be NEW) of did you just write a better reproducibility steps list?
(In reply to tommy27 from comment #10)
> Robinson, are you confirming the bug yourself (in this case status should be
> NEW) of did you just write a better reproducibility steps list?
I don't have Win here to confirm. Just clarifying steps for repro.
No problem with Win 7 Pro 64-bit, LibO 4.4 RC2
I used this registry patch to be able to enter my username:
Windows server 2003 is going EOL in July 2015: http://www.microsoft.com/server-cloud/
To original reporter: is this still a problem for you and will it be a problem (have you already started moving away from Win server 2003)?
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:
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!
This NEEDINFO message was generated on: 2015-09-03
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
Message generated on: 2015-10-14
tested again in LO 188.8.131.52; bug is not reproducible anymore; WORKSFORME