Hi, On Fri, Oct 10, 2025 at 02:49:09PM +0200, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Am 10.10.25 um 13:40 schrieb Guido Günther: > > Package: network-manager > > Version: 1.54.1-1 > > Severity: normal > > > > Hi, > > > > NetworkManager-initrd.service fails to start like > > > > `` > > $ systemctl status NetworkManager-initrd > > ○ NetworkManager-initrd.service - NetworkManager (initrd) > > Loaded: error (Reason: Unit NetworkManager-initrd.service failed to > > load properly, please adj> > > Active: inactive (dead) > > > > Okt 10 13:29:07 foo systemd[1]: NetworkManager-initrd.service: Two services > > allocated for the sa> > > Okt 10 13:29:57 foo systemd[1]: NetworkManager-initrd.service: Two services > > allocated for the sa> > > ``` > > > > Should that service be masked by default as it wants to acquire the same > > bus name as the "regular" service unit? > > Is there an actual problem?
Sending a clear message like masked (maining "not needed") is better than one sayhing "Error: " leaving the user (in this case me) wondering if something is wrong (thus maybe malfunctioning). Also on an mkosi built forky system it triggered neither NetworkManager.service nor the NetworkManager-initrd.service starting (although I'd understand if you deemed that unsupported). > This service is only enabled in the initrd (if a corresponding initrd > generator like dracut pulls it in). > > I'm not sure what we would gain by blacklisting it (aside from a different > kind of error message). Sending a clear message indicating that there is nothing wrong but the service is just not needed. Cheers, -- Guido
