- Package:
- installation-reports
- Source:
- installation-reports
- Submitter:
- Nick Gawronski
- Date:
- 2025-09-22 16:19:02 UTC
- Severity:
- normal
(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: Debian Trixie RC3 network installation written to a 32 gig SMI USB stick
Date: September 20, 2025 10:00 AM
Machine: Dell Inspironn7110
Partitions: <df -Tl will do; the raw partition table is preferred>
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev devtmpfs 3975076 0 3975076 0% /dev
tmpfs tmpfs 803020 1384 801636 1% /run
/dev/mapper/dellinspironn7110--vg-root ext4 951957092 4792900 937464988 1% /
tmpfs tmpfs 4015088 4 4015084 1% /dev/shm
tmpfs tmpfs 5120 8 5112 1% /run/lock
tmpfs tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service
tmpfs tmpfs 1024 0 1024 0% /run/credentials/systemd-cryptsetup@sda5_crypt.service
tmpfs tmpfs 4015092 72 4015020 1% /tmp
/dev/sda1 ext4 964900 184244 714304 21% /boot
tmpfs tmpfs 803016 2760 800256 1% /run/user/105
tmpfs tmpfs 1024 0 1024 0% /run/credentials/getty@tty1.service
tmpfs tmpfs 803016 64 802952 1% /run/user/1000
tmpfs tmpfs 803016 56 802960 1% /run/user/0
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O ]
Detect network card: [O ]
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 am totally blind and so used the install with software speech option. After the installation I had speech at the mate login screen and after logging in but no speech what so ever in the console when pressing control and alt and f1. If I try to ssh into the system and run alsamixer I get the message that the host is down.
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
Make sure that speech can be ran both in the console and the mate desktop side by side as often when Trixie worked properly as some update caused this issue so I thought i would reinstall to see if the issue was fixed and it is notit would be nice not to have to reboot to just use the console with a screen reader.
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.
Another issue I found is with using encryption with LVM I am unable to use BTRFS as the root filesystem either with or without encryption.
Here are my installation logs.
This statement does not provide any useful information. Can you please elaborate ?
If I have selected BTRFS instead of ext4 when the partition tries to format itself with or without LVM it fails to mount with BTRFS so I had to go back to ext4. The installation logs I attached should have that information in them as I think it is the fact that either the BTRFS support is not in the installation kernel or that the proper tools are not inside the installer.
To add a bit of context to this bug, the OP has also posted at [1] and [2]. [1] https://lists.debian.org/debian-accessibility/2025/09/msg00022.html [2] https://lists.debian.org/debian-accessibility/2025/09/msg00008.html
Control: clone -1 -2 Control: retitle -2 partman-btrfs: Wrong usrquota and grpquota options Control: reassign -2 partman-btrfs 1 btrfs: Unknown parameter 'usrquota' I suppose that you selected the "usrquota" mount option, but btrfs does not seem to support it. btrfs(5) does not mention it. Same with "grpquota". I guess they were inadvertently copied from partman-xfs when partman-btrfs was created. So cloning the bug for this separate issue. Note: you should compress installation logs before attaching them. Your mail was too big and not forwarded to the debian-boot mailing list, so people were not aware of it until you mentioned them in another mail.
Hi Nick, Am 20. September 2025 22:32:50 MESZ schrieb Nick Gawronski <nick@nickgawronski.com>: So just to let you know: the release of trixie has already happened in the mid of august, and you should best use a debian-13.X image instead of a pre-release image. I'm not sure this will make a difference here, but to be sure we are not hunting an issue which has already been fixed, you should try reinstalling with the latest trixie image first, maybe? <https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-13.1.0-amd64-netinst.iso> Holger
https://salsa.debian.org/installer-team/partman-btrfs/-/merge_requests/4 Oops, I just noticed that this fix is already included in an open (larger) merge request: https://salsa.debian.org/installer-team/partman-btrfs/-/merge_requests/3
I tagged the wrong bug, sorry for the noise.
Here are the compressed installation logs.
Here are the new installation logs from the stable installation image with the same issue and the BTRFS choice works.
Hi Nick, I did some test installations with Debian 13: When installing a console-only system, means without any desktop environment, speech works on the virtual console. Installing MATE makes speech working in the graphical MATE environment, but not on the virtual console, identical to your findings. espeakup is running, but no output. Here pipewire is additionally installed, while it is not in the console-only installation. So maybe alsa and pipewire don't work together correctly? Did that work with Debian 12? Holger Nick Gawronski <nick@nickgawronski.com> wrote (Sun, 21 Sep 2025 13:21:32 -0500):
The OP (Nick Gawronski) has also posted on the Debian forum, [1] has a workaround and also contains the URL for the forum post. [1] https://lists.debian.org/debian-accessibility/2025/09/msg00031.html
Yes it did work just fine and it use to work in Trixie to up until some updates ago but not totally sure what was changed to cause this issue. Not sure if you also saw this but if you login to the mate desktop and also try to access the console with control and alt and f1 you get no speech. This was also seen in version 12 but at the mate login screen I was able to get speech working in the console just not once I was loggd in.
Here is a message from the debian-accessibility mailing list that might help so I am posting it here to have you look at it.-------- Forwarded Message -------- Subject: Re: Sound / voice issues Resent-Date: Mon, 22 Sep 2025 14:59:15 +0000 (UTC) Resent-From: debian-accessibility@lists.debian.org Date: Mon, 22 Sep 2025 10:58:52 -0400 From: Chevelle <cstrobel@purelymail.com> To: debian-accessibility@lists.debian.org After I read some of these messages again, I realized that my system was upgraded from Bookworm and not installed fresh. This is why my audio works for speakup and Nick's doesn't. I installed a Trixie system in a Virtual machine from. debian-13.1.0-amd64-netinst.iso. It has the problem where speakup can't speak. When I compare the systems I notice that files are missing in: /etc/alsa/conf.d My upgraded bookworm system has 10-rate-lav.conf 10-samplerate.conf 10-speexrate.conf 50-arcam-av-ctl.conf 50-jack.conf 50-oss.conf 50-pulseaudio.conf 60-a52-encoder.conf 60-speex.conf 60-upmix.conf 60-vdownmix.conf 98-usb-stream.conf 99-pulseaudio-default.conf.example 99-pulse.conf I was able to fix the virtual machine system by doing sudo apt install pulseaudio Now if you type 'amixer' it will work. sudo apt purge pulseaudio Now 'amixer' and speakup still worked. I'm not saying this is the correct solution, but it might be a work-around. If you read this message from the Debian forum he is asking about essentially the same problem, but nobody gave him an answer. https://forums.debian.net/viewtopic.php?t=156266