Your message dated Wed, 13 Aug 2025 19:55:45 +0300
with message-id
<capzxpqc+onwi032dkfngpy4fqmhv_kuthp4spgb+1chwnq0...@mail.gmail.com>
and subject line Re: Bug#1104094: dhcpcd gets stuck after system reboot
has caused the Debian Bug report #1104094,
regarding dhcpcd gets stuck after system reboot
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 [email protected]
immediately.)
--
1104094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104094
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dhcpcd
Version: 1:10.1.0-9
Severity: important
Dear Maintainer,
I've encountered an issue that I've initially reported upstream:
https://github.com/NetworkConfiguration/dhcpcd/issues/503
However, I just installed version 1:10.2.2-5 from experimental and it seems
that this does has fixed the issue. I thought I would flag this, as this issue
is present in the dhcpcd package that is currently in the testing release, and
thus, might affect the next stable release of Debian.
Cheers,
Timo
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'stable'),
(400, 'unstable'), (300, 'experimental')
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 dhcpcd depends on:
ii dhcpcd-base 1:10.2.2-5
ii sysvinit-utils [lsb-base] 3.14-4
Versions of packages dhcpcd recommends:
ii wpasupplicant 2:2.10-24
Versions of packages dhcpcd suggests:
pn dhcpcd-gtk <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 16 May 2025 20:50:17 +0200 Timo van Roermund
<[email protected]> wrote:
> No, I didn't.
>
> I also haven't experienced it anymore using version 1:10.2.2-5/6 from
> experimental.
Since this was fixed in 1:10.2.2-5 and unstable has 1:10.2.4-3, I'll
close this now.
Martin-Éric
--- End Message ---
