Bug#1112535: /usr/lib/systemd/systemd-networkd: segfault after upgrade to 257.8-1~deb13u1, no connectivity after reboot

[Kevin Otte]

On Sun, 07 Sep 2025 23:58:46 +0100 Luca Boccassi <bluca at debian.org> wrote:
> Control: severity -1 minor

This is rather insulting.

> On Sun, 07 Sep 2025 23:02:13 +0100 "Adam D. Barratt"
> <adam at adam-barratt.org.uk> wrote:
> > On Sun, 2025-09-07 at 22:52 +0100, Tim Small wrote:
> > > This was reported a good week before Debian 13.1 went out, so I'm a
> > > bit surprised it still went into that?
> > 
> > It was reported at a non release critical severity, tagged "moreinfo"
> > and neither the submitter nor the maintainer (nor anyone else) raised
> > it to the Release Team's attention.

And why is that? It was filed against proposed-updates. I thought the 
whole point of that mechanism was to test the proposed update and 
withdraw it if problems were found, avoiding this very scenario. The 
process clearly broke down here.

> There was absolutely no need to disturb RT and waste your time, as you
> have much more important things to take care of, as this is just a
> minor issue

I would hardly call my network failing out from under me during a 
routine "apt upgrade" a minor issue. (The OP filed as after reboot, mine 
died during the upgrade. I did not mention this in the confirmation as 
the problem seemed to be under control at the time with the upstream fix 
being documented.)

> with a particular corner case of a custom config

The use of VLAN filtering bridges is a normal feature introduced in 
kernel 3.8. This configuration is well documented in the manual of 
systemd-networkd. I began using it under Debian 13 as libvirt gained the 
ability to assign VMs to those VLANs. This is hardly a corner case nor a 
custom configuration.

> of an optional component.

systemd-networkd is part of the systemd package which is included in 
base. It is referred to in the fine manual at 
https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_modern_network_configuration_without_gui 
. I would hardly call this an optional component.

> Anybody who is unable to deal with that should just
> stick to the default Debian components. The next stable update in ~2
> months will contain a fix.

Any package maintainer that can't adequately maintain their package, 
especially one as critical as systemd, and essentially tells the user 
"sucks to be you" should step down. Given this response, and your 
handling of the systemd-resolved mDNS issue a few months ago, I get the 
impression you're burned out. Maybe it would be best to let someone else 
take the reins for awhile.