[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1104550: marked as done (d-i fails to create user with non-ASCII full name)

Your message dated Mon, 2 Jun 2025 00:08:51 +0200
with message-id <7fad340a-7633-4b06-9fb0-abf5d5c39b23@plouf.fr.eu.org>
and subject line Re: debian-cd: fails to create user when keyboard layout is specified as Turkish Q
has caused the Debian Bug report #1104550,
regarding d-i fails to create user with non-ASCII full name
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1104550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104550
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-cd
Version: 3.2.1
Severity: normal
X-Debbugs-Cc: sukruerengokirmak@gmail.com

Dear Maintainer,

I was trying to install Debian testing on my computer. I picked Turkish Q keyboard layout,
as that is my laptop's layout. I then used a username which has only latin characters,
and a password which only contains numbers. I picked GNOME as my desktop environment.
The rest of the configuration went fine.

However, when I rebooted the machine to log in, I found out that the user I defined was not created.
I later tried the same installation using an American keyboard layout, which went as expected.
I entered my credentials and successfully logged in, in this case.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.22-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debian-cd depends on:
ii  apt                        3.0.0
ii  bc                         1.07.1-4
ii  bzip2                      1.0.8-6
ii  cpp                        4:14.2.0-1
pn  curl                       <none>
pn  dpkg-dev                   <none>
pn  grep-dctrl                 <none>
pn  libcompress-zlib-perl      <none>
pn  libdigest-md5-perl         <none>
pn  libdpkg-perl               <none>
pn  libfile-slurp-perl         <none>
pn  libyaml-libyaml-perl       <none>
ii  lynx                       2.9.2-1
pn  make                       <none>
ii  perl [libdigest-sha-perl]  5.40.1-3
pn  pigz                       <none>
pn  tofrodos                   <none>
pn  uuid-runtime               <none>
ii  wget                       1.25.0-2
pn  xorriso | genisoimage      <none>

Versions of packages debian-cd recommends:
ii  dosfstools       4.2-1.2
pn  hfsutils         <none>
pn  isolinux         <none>
pn  mtools           <none>
pn  syslinux-common  <none>

debian-cd suggests no packages.

--- End Message ---
--- Begin Message --- 
Version: 1.105

On 07/05/2025 at 13:56, Pascal Hambourg wrote:
The bug is caused by the combination of user-setup (the installer component in charge of setting up the user account) not doing full name sanitation and adduser (the program used to actually create the user in the installed system) starting doing overly strict sanitation. 

Fixed in user-setup 1.105 and adduser 3.152.

--- End Message ---
Reply to: