If the username contains special characters (umlaut, accents, ...), after starting the session the user ends up with an empty unusable desktop.
Steps to reproduce
Create a user with special characters in the name
Login from TDM
Observe crashes and unusable desktop result (note, TDE Personalizer will still run the first time)
## Basic information
- TDE version: R14.1.0-dev <!-- such as R14.0.5 -->
- Distribution: debian buster <!-- such as Debian 9 or Debian Stretch -->
- Hardware: amd64 <!-- amd64 / i386 / armhf / ... -->
<!--
Use SL/* labels to set the severity level.
Please do not set a milestone.
-->
## Description
This is a follow on from bug [2961](https://bugs.pearsoncomputing.net/show_bug.cgi?id=2961).
If the username contains special characters (umlaut, accents, ...), after starting the session the user ends up with an empty unusable desktop.
## Steps to reproduce
1. Create a user with special characters in the name
2. Login from TDM
3. Observe crashes and unusable desktop result (note, TDE Personalizer will still run the first time)
useradd does not care, but adduser does care about special characters
# adduser schnöller
adduser: To avoid problems, the username should consist only of
letters, digits, underscores, periods, at signs and dashes, and not start with
a dash (as defined by IEEE Std 1003.1-2001). For compatibility with Samba
machine accounts $ is also supported at the end of the username
seems I can not create a user with such characters easily and is rather exotic use case
useradd does not care, but adduser does care about special characters
```
# adduser schnöller
adduser: To avoid problems, the username should consist only of
letters, digits, underscores, periods, at signs and dashes, and not start with
a dash (as defined by IEEE Std 1003.1-2001). For compatibility with Samba
machine accounts $ is also supported at the end of the username
```
seems I can not create a user with such characters easily and is rather exotic use case
I did test long ago. I think I created a user in CLI first. I can login to CLI without problems, but when logging in into TDE all sort of missing things happens.
As for 2961, the password problem has already been fixed. This issue is a spinoff/generalization of that.
I did test long ago. I think I created a user in CLI first. I can login to CLI without problems, but when logging in into TDE all sort of missing things happens.
As for 2961, the password problem has already been fixed. This issue is a spinoff/generalization of that.
Hi Emanoil, I did the test at the time when I reported this bug.
I repeated the test today and I got the same result.
You can use KUser to create a user with accented characters. You can verify you can login from CLI without issues, but if you try to login to TDE you will end up with a broken KDesktop.
Hi Emanoil, I did the test at the time when I reported this bug.<br/>
I repeated the test today and I got the same result.
You can use KUser to create a user with accented characters. You can verify you can login from CLI without issues, but if you try to login to TDE you will end up with a broken KDesktop.
Basic information
Description
This is a follow on from bug 2961.
If the username contains special characters (umlaut, accents, ...), after starting the session the user ends up with an empty unusable desktop.
Steps to reproduce
useradd does not care, but adduser does care about special characters
seems I can not create a user with such characters easily and is rather exotic use case
Thanks Emanoil, I agree it is probably not a very common situation, but definitely possible. Perhaps this should not be marked as "major".
Hi,
not only this - how can it be reproduced?
And 2961 talks about characters in password while this issue talks about username
I did test long ago. I think I created a user in CLI first. I can login to CLI without problems, but when logging in into TDE all sort of missing things happens.
As for 2961, the password problem has already been fixed. This issue is a spinoff/generalization of that.
OK - understood. How long ago? I recall in the past few years a lot around UTF-8 changed.
May be I will try to test it again when time allows.
Hi Emanoil, I did the test at the time when I reported this bug.
I repeated the test today and I got the same result.
You can use KUser to create a user with accented characters. You can verify you can login from CLI without issues, but if you try to login to TDE you will end up with a broken KDesktop.
Bug 3188 also relates to the same problem.