I also experience this bug.
I got in touch with the debian maintainers for systemd at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904079
According to the maintainer, the issue should be solved by using the
`After=` directive in the unit file for console-setup.
Regards,
Arnaud
Package: netcfg
Severity: normal
Tags: d-i
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
the default hostname "debian" is hardcoded in two places in the file
netcfg-common.c:
https://salsa.debian.org/installer-team/netcfg/-/blob/master/netcfg-common.c#L1043
https://salsa.debian.org
Package: debootstrap
Version: 1.0.123
Severity: normal
Tags: patch
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
The code that is meant to detect if debootstrap is running from within a
docker container is broken with cgroup v2. Talking about this particular
function and line in the
Package: debian-installer
Severity: normal
Tags: a11y
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
some recent Intel sound cards require a firmware to work. This firmware
is packaged under 'firmware-sof-signed'. For reference, you might want
to look at the ITP [1].
As expected, se
Package: debootstrap
Version: 1.0.123
Severity: normal
Tags: patch
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
I noticed that, when auto-apt-proxy is installed on my machine,
debootstrap does not detect it as it should. It turns out that
debootstrap checks for 'Acquire::http::Prox
Package: hw-detect
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
hw-detect already installs the package qemu-guest-agent when kvm/qemu
virtualization is detect, in 'hw-detect.finish-install.d/08hw-detect':
kvm|qemu)
apt-install --with-recommends qemu-gu
0
pgfault 2310
pgmajfault 0
pgrefill 0
pgscan 0
pgsteal 0
pgactivate 759
pgdeactivate 0
pglazyfree 0
pglazyfreed 0
thp_fault_alloc 0
thp_collapse_alloc 0
==> /sys/fs/cgroup/memory.swap.current <==
0
==> /sys/fs/cgroup/memory.swap.events <==
high 0
max 0
fail 0
==> /sys/fs/cgroup/memory.swap.high <==
max
==> /sys/fs/cgroup/memory.swap.max <==
max
==> /sys/fs/cgroup/pids.current <==
2
==> /sys/fs/cgroup/pids.events <==
max 0
==> /sys/fs/cgroup/pids.max <==
18738
==> /sys/fs/cgroup/rdma.current <==
==> /sys/fs/cgroup/rdma.max <==
--
Arnaud Rebillout
Hello Tianon,
On 4/20/21 2:39 AM, Tianon Gravi wrote:
Hey Arnaud, thanks for the CC (and sorry for the delay).
On Mon, 12 Apr 2021 at 20:48, Arnaud Rebillout wrote:
> Originally, ".dockerenv" was for transmitting the environment
> variables of the container across the co
Package: debian-installer
Version: 20230607
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
This issue doesn't affect Debian (as Debian's installer images come with
a signed GRUB), but it affects Debian derivatives that use a unsigned
GRUB in their installer. In parti
case it was not clear, even though
"tested" for me just means booting the .iso in a QEMU VM.
Cheers,
--
Arnaud Rebillout / OffSec / Kali Linux Developer
ects a BIOS VM. If I boot a UEFI VM, everything
works fine.
Thanks
--
Arnaud Rebillout / OffSec / Kali Linux Developer
tuations: when mkdir fails, or when
mount fails, and for either /proc, /sys or /sys/firmware/efi/efivars...
Cheers,
--
Arnaud Rebillout / OffSec / Kali Linux Developer
gives nothing, hence the grub-installer
postinst doesn't try to mount the efivarfs.
Today's iso has kernel 6.3.0-kali1-amd64. In this iso, `cat
/proc/filesystems | grep efi` gives `nodev efivarfs`, hence the
grub-installer postinst tries to mount efivarfs, and fails.
--
Arnaud Reb
Tentative fix, for what it's worth:
https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/19
--
Arnaud Rebillout / OffSec / Kali Linux Developer
n device "/dev/sda1": No such device
Unknown device "/dev/sda1": No such device
Unknown device "/dev/sda1": No such device
Unknown device "/dev/sda1": No such device
Installation finished. No error reported.
info: grub-install ran successfully
Cheers,
--
Arnaud Rebillout / OffSec / Kali Linux Developer
Package: tasksel
Version: 3.68
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
in Kali Linux we made the mistake to put a comma in a task description:
Description: everything -- almost all tools [>= 7 GB to download, >= 16 GB
installed]
Cf https://gitlab.com/kali
Source: hw-detect
Version: 1.147
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
A Kali Linux user reported a fail install on a Dell XPS 9510. For the
background, the Kali Linux installer is a super lightweight fork of the
Debian installer, kept in sync with Debian.
Source: hw-detect
Version: 1.147
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
The package open-vm-tools 11.3.5, released in January 2022, depends on
fuse3 rather than fuse [1].
As a consequence, hw-detect fails to install open-vm-tools if ever the
package fuse was
On Thu, 14 Jul 2022 20:14:15 +0200 Ben Hutchings
wrote:
>
> You should find out why that is, before proposing to override it. What
> if something in KDE really does need FUSE 2?
I don't think that it can happen. A package might need FUSE3 (in such
case it depends on fuse3), or it might need FU
Package: cdebconf
Version: 0.265
Severity: normal
User: de...@kali.org
Usertags: origin-kali
X-Debbugs-Cc: sthiba...@debian.org
Dear Maintainer,
Short story: task selection is ignored in speech synthesis mode. This is
due to a regression in the cdebconf text frontend. The issue is easily
fixed, a
20 matches
Mail list logo