Bug 75835 - Changing the case of chars in username affects document recovery
Summary: Changing the case of chars in username affects document recovery
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.2.1.1 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: needsWindows
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-06 12:17 UTC by a07cd040897db54e103c
Modified: 2016-08-10 11:47 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description a07cd040897db54e103c 2014-03-06 12:17:14 UTC
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.
Comment 1 Urmas 2014-03-06 17:55:52 UTC
Which Windows version?
Comment 2 a07cd040897db54e103c 2014-03-07 06:59:29 UTC
We experienced this on Windows Server 2003 x64.
Comment 3 Jean-Baptiste Faure 2014-03-08 09:57:07 UTC
Set back to UNCONFIRMED because this bug report has not been confirmed independently.

Thank you for your understanding.
Best regards. JBF
Comment 4 Jean-Baptiste Faure 2014-03-08 22:04:43 UTC
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
Comment 5 a07cd040897db54e103c 2014-03-10 09:05:58 UTC
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.
Comment 6 Joel Madero 2014-11-06 00:29:13 UTC
From what I can see this was never confirmed by QA team - moving to UNCONFIRMED to get their confirmation.
Comment 7 Robinson Tryon (qubit) 2015-01-03 20:45:27 UTC
Clarify problem in Summary
Comment 8 Urmas 2015-01-03 21:04:27 UTC
Cannot reproduce as described.
Comment 9 Robinson Tryon (qubit) 2015-01-11 01:06:38 UTC
(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-off
- 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.
Comment 10 tommy27 2015-01-11 17:33:14 UTC
Robinson, are you confirming the bug yourself (in this case status should be NEW) of did you just write a better reproducibility steps list?
Comment 11 Robinson Tryon (qubit) 2015-01-11 20:13:22 UTC
(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.
Comment 12 Buovjaga 2015-01-21 07:23:02 UTC
No problem with Win 7 Pro 64-bit, LibO 4.4 RC2

I used this registry patch to be able to enter my username:
http://www.sevenforums.com/tutorials/61650-log-user-name-password.html

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)?
Comment 13 QA Administrators 2015-09-04 02:56:39 UTC Comment hidden (obsolete)
Comment 14 QA Administrators 2015-10-14 19:49:13 UTC Comment hidden (obsolete)
Comment 15 a07cd040897db54e103c 2016-08-10 11:47:26 UTC
tested again in LO 5.1.5.2; bug is not reproducible anymore; WORKSFORME