Bug#1101546: Acknowledgement (installation-reports: Wifi is no longer detected in Debain after I started windows 100 dual boot, until reinstalled the bios. Applies also to debain installer)

[Michael Josenhans]

> You do not have to reinstall Debian. If the wifi is not working now,
please provide the output of
># lspci -nnk
># dmesg
>
>not too long after boot so that the first kernel messages ("Linux
version...") have not been flushed, else
>
># journalctl -k

Hi Pascal,

Here are attached the requested additional logs.

Br,

Michael


On 29.03.25 08:21, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1101546: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101546.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian Install Team 

If you wish to submit further information on this problem, please
send it to 1101...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



lspci-nnk.log.gz
Description: application/gzip


journalctl-k.log.gz
Description: application/gzip


dmesg.log.gz
Description: application/gzip

Bug#1101196: installation-reports: Trixie Installer fails to create first user when full name contains non-ASCII characters and spaces

[Holger Wansing]

Hi,

Am 29. März 2025 22:47:24 MEZ schrieb Pascal Hambourg :
>On 29/03/2025 at 21:13, Holger Wansing wrote:
>>> 
>>> commentre => qr/["-_\.+!\$%&()\]\[;0-9a-zA-Z\/ ]*/
>> 
>> If above sanitation regex is new in adduser, then this choice looks to me
>> like the way to go.
>
>I would be disappointed if Debian stopped allowing international characters in 
>the full name without a good reason.

My sight was, that this change in adduser was made for a good reason ...
Hopefully adduser maintainer can comment on this.


Holger



-- 
Sent from /e/ OS on Fairphone3

Bug#1101196: installation-reports: Trixie Installer fails to create first user when full name contains non-ASCII characters and spaces

[Cyril Brulebois]

Hi,

David  (2025-03-29):
> (I am not the maintainer, just an observer)
> 
> Thank you for your work on Debian!
> 
> The discussion on this bug so far seems to have not noticed that
> there was recent discussion on the debian-devel mailing list about
> this topic.
> 
> Approximately 40 messages beginning in November 2024:
>   https://lists.debian.org/debian-devel/2024/11/msg00250.html
> Approximately 60 messages continuing in December 2024:
>   https://lists.debian.org/debian-devel/2024/12/msg00012.html

Thanks for the pointer, but a discussion on debian-devel@ isn't exactly
an explanation for becoming overly strict, especially if it isn't quite
self-explanatory in the changelog. As far as I understand the git
history, that strictness was implemented in 3.138, and the best I could
find was the following:

  * adapt adduser to more strict user name checking now enforced by
useradd. This unfortunately meant to disable some more of our tests.

which doesn't quite capture what's happening.

Maybe I'm just misunderstanding the code base and/or failing to find
proper documentation, that's entirely possible.

Moreover, useradd(8) mentions:

   -c, --comment COMMENT
   Any text string. It is generally a short description of the account,
   and is currently used as the field for the user's full name.

While adduser(8) has:

   --comment comment
  Set  the comment field for the new entry generated.  adduser will
  not ask for the information if this option is given.  This  field
  is also known under the name GECOS field and contains information
  that  is  used  by  the  finger(1)  command.  This used to be the
  --gecos option, which is deprecated and will be removed after De‐
  bian bookworm.  Valid modes: adduser, adduser --system.

Neither of those mentions any restrictions, nor a way to bypass them.

There are a number of options to allow bad or even all names, but that's
a very different logic and doesn't apply to the comment sanitization.


Side note for user-setup, we should apparently migrate from --gecos to
--comment at some point, but that doesn't change the way things are
managed, both set $new_comment as a string via GetOptions.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1101196: installation-reports: Trixie Installer fails to create first user when full name contains non-ASCII characters and spaces

[David]

On Sat, 29 Mar 2025 at 23:15, Holger Wansing  wrote:
> Am 29. März 2025 22:47:24 MEZ schrieb Pascal Hambourg 
> :
> >On 29/03/2025 at 21:13, Holger Wansing wrote:

> >>> commentre => qr/["-_\.+!\$%&()\]\[;0-9a-zA-Z\/ ]*/
> >>
> >> If above sanitation regex is new in adduser, then this choice looks to me
> >> like the way to go.
> >
> > I would be disappointed if Debian stopped allowing international
> > characters in the full name without a good reason.
>
> My sight was, that this change in adduser was made for a good reason ...
> Hopefully adduser maintainer can comment on this.

Hello,

(I am not the maintainer, just an observer)

Thank you for your work on Debian!

The discussion on this bug so far seems to have not noticed that
there was recent discussion on the debian-devel mailing list about
this topic.

Approximately 40 messages beginning in November 2024:
  https://lists.debian.org/debian-devel/2024/11/msg00250.html
Approximately 60 messages continuing in December 2024:
  https://lists.debian.org/debian-devel/2024/12/msg00012.html

Bug#1101196: installation-reports: Trixie Installer fails to create first user when full name contains non-ASCII characters and spaces

[Pascal Hambourg]

On 29/03/2025 at 21:13, Holger Wansing wrote:


I have tested an install with not selecting anything in tasksel (even
standard was unselected), and both adduser and useradd were installed
in this minimal setup.


adduser is installed by debootstrap as part of the base system.


So useradd seems to be mostly not in use (anymore).


Actually useradd is used as a back-end by adduser.


Anyway, it seems that adduser is the program, that's used when this error
occures, not useradd.


Right.


IIUC adduser's new sanitation regex for the 'comment' (ex-gecos) value)
is defined by:

commentre => qr/["-_\.+!\$%&()\]\[;0-9a-zA-Z\/ ]*/

It looks like only ASCII characters are allowed.


Also, the regex matches the whole range from '"' to '_' (including ':' 
which is the field separator in /etc/passwd so should be prohibited). Is 
this intended or is it a mistake ?



Possible options may include:
- align adduser's comment sanitation regex on useradd
- make user-setup have the same restriction on the full name as adduser
(it currently does not seem to have any)


If above sanitation regex is new in adduser, then this choice looks to me
like the way to go.


I would be disappointed if Debian stopped allowing international 
characters in the full name without a good reason.

Bug#1100878: Installing from the Trixie live ISO results in a working install

[Holger Wansing]

Hi,

Am 25. März 2025 00:28:39 MEZ schrieb Nolan :
>On 3/23/25 14:20, Holger Wansing wrote:
>
>> To be sure:
>> you used the live ISO, to boot the normal debian-installer as you did with
>> the netinst ISO, then went through the whole installation as you did with the
>> netinst ISO, and the result is different from what you get with the netinst 
>> ISO?
>
>Correct, I chose the installer from the live cd's (GRUB?) boot menu. This 
>resulted in a graphical install that works. Choosing (graphical or text-mode) 
>install in the netinst ISO resulted in a non-working install.
>
>> So, you did NOT boot into the live environment and started the debian
>> installation from there? (There is a different, graphical installer, the
>> Calamares installer accessible from the live environment (I think the icon
>> is named something like 'Install Debian'), which could be different in some
>> regards, compared to the usual debian-installer.)
>
>Correct. I have not tried doing an install from the booted live environment.

That's unexpected to me.
My expectation would have been, that there is no difference between the netinst 
and the live ISO, using d-i ...


Holger

-- 
Sent from /e/ OS on Fairphone3

Bug#1101196: installation-reports: Trixie Installer fails to create first user when full name contains non-ASCII characters and spaces

[Holger Wansing]

Hi,

Pascal Hambourg  wrote (Wed, 26 Mar 2025 20:54:09 
+0100):
> On 24/03/2025 at 20:29, Cyril Brulebois wrote:
> > 
> > Oh wow, that's indeed badly broken, and will need fixing before the next
> > release. Reproduced locally with a 'û' in my last name:
> > 
> >  Mar 24 19:17:59 finish-install: info: Running 
> > /usr/lib/finish-install.d/06user-setup
> >  Mar 24 19:17:59 user-setup: Shadow passwords are now on.
> >  Mar 24 20:17:59 chpasswd[8387]: pam_unix(chpasswd:chauthtok): password 
> > changed for root
> >  Mar 24 19:17:59 user-setup: invalid characters in Cyril 
> > Br\x{fffd}\x{fffd}lebois at /usr/share/perl5/Debian/AdduserCommon.pm line 
> > 141.
> (...)
> > No feedback during the installation process, just silent failure to
> > create the user. :(
> > 
> > Looping in adduser people for awareness and maybe tips. A quick look at
> > adduser.git suggests sanitation got added end 2024/beginning 2025…
> 
> If adduser exists in the target system then user-setup runs
> 
>adduser --disabled-password --gecos "$fullname" "$user" || true
> 
> else it runs
> 
>useradd -c "$fullname" -m "$user" || true
> 
> What is the advantage of calling adduser instead of useradd ?

When looking at the manpages of these both, it seems as adduser is 
preferred over useradd; people are recommended to not use useradd.

Why have the above logic in the installer at all?
useradd looks as some kind of backup... Maybe there may be/were situations,
where adduser package is not installed, but shadow is?
I have tested an install with not selecting anything in tasksel (even
standard was unselected), and both adduser and useradd were installed
in this minimal setup. So useradd seems to be mostly not in use (anymore).

Anyway, it seems that adduser is the program, that's used when this error
occures, not useradd.

> IIUC adduser's new sanitation regex for the 'comment' (ex-gecos) value) 
> is defined by:
> 
>commentre => qr/["-_\.+!\$%&()\]\[;0-9a-zA-Z\/ ]*/
> 
> It looks like only ASCII characters are allowed. Oddly, adduser allows 
> non ASCII characters in interactive mode. useradd does not seem to have 
> such restriction for -c.
> 
> Possible options may include:
> - align adduser's comment sanitation regex on useradd
> - make user-setup have the same restriction on the full name as adduser 
> (it currently does not seem to have any)

If above sanitation regex is new in adduser, then this choice looks to me
like the way to go.

> - make user-setup always call useradd
> 
> PS: Why are user settings collected early in the installation process 
> (before partitioning) even though they are written out at the end ?


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1101546: installation-reports: Wifi is no longer detected in Debain after I started windows 100 dual boot, until reinstalled the bios. Applies also to debain installer

[Michael Josenhans]

Package: installation-reports
Severity: normal
Tags: d-i

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: usb
Image version: likely debian 12.10.0 AMD 64 DVD
Date: 
26.3. 0:00
Machine: HP Elitebook 840 G6
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: I had to reinstall the Bios in order to get the wifi working 
and be detected by debian. In Windows 11 the Wifi is detected. After I 
reinstalled the bios and booted Windows 11 again, when I have enabled allow 
native OS update the bios, the after booting debian the Wifi is no longer 
detected. I assume that Windows 11 is overwriting the bios. When I reinstall 
the bios from the bios (its same version of the bios, which is installed again 
as before) when I then boot debian wifi is detected.
For installation I have reinstalled the bios from bios and installed debain 
using usb netinstall. Now after installation I have allowed to reinstall the 
bios by the native OS and rebooted windows 11. After rebooting debain wifi is 
no longer detected. (note



Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.
root@debian:/home/michael# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM 
Controller [8086:3e34] (rev 0c)
00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 
[UHD Graphics 620] [8086:3ea0] (rev 02)
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c)
00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Point-LP 
Thermal Controller [8086:9df9] (rev 11)
00:14.0 USB controller [0c03]: Intel Corporation Cannon Point-LP USB 3.1 xHCI 
Controller [8086:9ded] (rev 11)
00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM 
[8086:9def] (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial 
IO I2C Controller #0 [8086:9de8] (rev 11)
00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial 
IO I2C Controller #1 [8086:9de9] (rev 11)
00:16.0 Communication controller [0780]: Intel Corporation Cannon Point-LP MEI 
Controller #1 [8086:9de0] (rev 11)
00:16.3 Serial controller [0700]: Intel Corporation Cannon Point-LP Keyboard 
and Text (KT) Redirection [8086:9de3] (rev 11)
00:17.0 SATA controller [0106]: Intel Corporation Cannon Point-LP SATA 
Controller [AHCI Mode] [8086:9dd3] (rev 11)
00:1c.0 PCI bridge [0604]: Intel Corporation Cannon Point-LP PCI Express Root 
Port #5 [8086:9dbc] (rev f1)
00:1c.7 PCI bridge [0604]: Intel Corporation Cannon Point PCI Express Root Port 
#8 [8086:9dbf] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Cannon Point-LP LPC Controller 
[8086:9d84] (rev 11)
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Cannon Point-LP 
High Definition Audio Controller [8086:9dc8] (rev 11)
00:1f.4 SMBus [0c05]: Intel Corporation Cannon Point-LP SMBus Controller 
[8086:9da3] (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI 
Controller [8086:9da4] (rev 11)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (6) 
I219-LM [8086:15bd] (rev 11)
01:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 2C 2018] [8086:15e7] (rev 06)
02:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 2C 2018] [8086:15e7] (rev 06)
02:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 2C 2018] [8086:15e7] (rev 06)
02:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 2C 2018] [8086:15e7] (rev 06)
03:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI 
[Titan Ridge 2C 2018] [8086:15e8] (rev 06)
39:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] [8086:15e9] (rev 06)
3a:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] 
(rev 1a)


Currently I have problems to install rfkill with apt install rfkill (rfkill is 
not found after installation)

root@debian:/home/michael# which rfkill
root@debian:/home/michael# 

In an installation before I installed the deb package directly as deb a

Bug#1101546: installation-reports: Wifi is no longer detected in Debain after I started windows 100 dual boot, until reinstalled the bios. Applies also to debain installer

[Pascal Hambourg]

On 29/03/2025 at 01:14, Michael Josenhans wrote:


Comments/Problems: I had to reinstall the Bios in order to get the wifi 
working and be detected by debian. In Windows 11 the Wifi is detected. 
After I reinstalled the bios and booted Windows 11 again, when I have 
enabled allow native OS update the bios, the after booting debian the 
Wifi is no longer detected.


In the attached logs the wifi seems to work. Do you have installer or 
kernel logs and the output of "lspci -nnk" when the wifi does not work ?

GRUB Boot Issues on high resolution screens

[Steven Hansen]

Dear Debian Boot Team,

I’d like to suggest a small improvement to GRUB's default
configuration in Debian.

On my high-resolution laptop screen, GRUB sometimes fails to boot
properly. I’ve seen repeated errors like:

```
error: out of memory.
error: syntax error.
error: Incorrect command.
```

This has happened multiple times over the course of using the current
Debian version. The workaround I’ve found is to manually set the GRUB
resolution to 640x480. For example, one way I’ve done this is by
removing the hard drive, attaching it to another machine, and changing
the resolution there.

If there’s a better solution I’m unaware of, I’d greatly appreciate
any recommendations. But for now, lowering the resolution seems to be
the only way, and it's a cumbersome process.

I would really like to be able to install Debian on high-resolution
laptops and have it just work out of the box. I know this issue has
affected other users and I know people have switched to other distros
after giving up because of this.

For better hardware compatibility out of the box—especially with
high-DPI screens—I’d like to suggest setting the default GRUB
resolution to 640x480 or another low resolution.

Thank you for your time and all your work on Debian.

Sincerely,

Steven O. Hansen

Re: Planning for 12.11

[Anupa Ann Joseph]

Hello Jonathan,

On 15/03/25 15:23, Jonathan Wiltshire wrote:

Hi,

The next cycle for bookworm should end somewhere around 10th May.
Please indicate your availability for:

  3 May
10 May
17 May



Sorry for the delay in replying.

I will be available on 3 May and 10 May.
Jean-Pierre Giraud will be available on 17 May if necessary.

Thank you.

--
Anupa Ann Joseph




OpenPGP_0xEE94D766BAE97405.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Uploading linux (6.12.21-1)

[Salvatore Bonaccorso]

Hi

I would like to upload linux version 6.12.21-1 to unstable.

It imports 6.12.21 only on top of the current packaging, which
includes security fixes. There are on top additional changes for the
packaging and adding support. In details they are the following:

   * lintian: Restore override for perf-read-vdso32 in linux-perf
   * linux-perf: Fix perf-check manual page built with asciidoctor
   * rtla: Add man page link for hwnoise(1)
   * intel-sdsi, rtla: Add "Depends: ${misc:Depends}"
   * d/copyright: Update filenames under arch/arm/boot/dts
   * d/copyright: Remove special case for drivers/crypto/vmx/*.pl
   * lintian: Override superfluous-file-pattern for d/copyright in
 linux-signed-*
   * d/salsa-ci.yml: Run lintian from the target release, not always unstable
   * [powerpc*] Revert "fbdev/offb: Update expected device name" (Closes:
 #1085949)
   * d/b/genpatch-rt: Fix subprocess cleanup with Python 3.13
   * sound/soc/amd/acp: Enable SND_AMD_ASOC_RENOIR as module (Closes: #1101155)
   * d/b/genpatch-rt: Drop now unused 'io' module.
   * drivers/net/wireless/realtek/rtw88: Enable RTW88_8723CS as a module
   * [amd64,arm64/cloud] Enable virtualisation drivers on cloud flavours,
 (Closes: #1101378)
 - drivers/virt: Enable VIRT_DRIVERS
 - drivers/virt: Enable VMGENID
 - drivers/virt/nitro_enclaves: Enable NITRO_ENCLAVES as module
 - drivers/virt/coco/sev-guest: Enable SEV_GUEST as module
 - drivers/virt/coco/tdx-guest: Enable TDX_GUEST_DRIVER as module

Regards,
Salvatore


signature.asc
Description: PGP signature

Core Debian Team participation DebConf 25

[Stefano Rivera]

Hello Everybody,

DebConf 25 is coming soon [0], and we'd like to remind all Debian's core 
teams to consider who is going to represent your team at DebConf. In 
recent years, Debian's core teams have not been well represented, and we 
should improve on that. DebConf is one of the best times to have casual 
conversations with people and unblock gnarly problems.


[0]: https://debconf25.debconf.org/news/2025-03-24-dc25-registration-cfp-open/

This is the first DebConf in Western Europe for many years, so we expect 
many more attendees to be able to attend conveniently, by train, than in 
recent years. If you've been waiting to come to a nearby DebConf, now is 
the time.


Bursaries for DebConf are available [1] if you register before April 
14th. If you're active in one of the core teams, you'll alomst certainly 
be able to receive financial assistance to attend. If finances are a 
blocker for your team attending, please get in contact with the DPL, the 
DebConf Content Team  or even me, I'm sure we can 
make a plan.


[1]: https://debconf25.debconf.org/about/bursaries/

Personally, I've found that almost every team in Debian can benefit from 
having a regular BoF. If it seems like nothing is happening in the team, 
worth talking about, even a noop BoF can be a good way to find out who 
is interested in joining the team and helping out. Just talking about 
the long-standing problems is the first step to fixing them.


Apologies for spam to all the teams listed on our project organization 
page [2]. I think this is a good way to ensure that all core teams are 
contacted, but I'm sure there's a lot of duplication.


[2]: https://www.debian.org/intro/organization

Stefano Rivera
for the DebConf Committee


signature.asc
Description: PGP signature