On 6/1/23 17:44, Facundo Gaich wrote:
On Thu, Jun 1, 2023 at 11:54 AM Debian Bug Tracking System
mailto:ow...@bugs.debian.org>> wrote:
Hi,
This is IMO a missconfiguration, not a bug. Closing accordingly.
Cheers,
Thomas Goirand (zigo)
Hi Thomas,
Thanks, although, isn't it
On Thu, Jun 1, 2023 at 11:54 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Hi,
>
> This is IMO a missconfiguration, not a bug. Closing accordingly.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
Hi Thomas,
Thanks, although, isn't it still a bug if it arrived at a misconfigured
state
On 6/1/23 10:07, Jonathan Dowland wrote:
But I suggest to the maintainer (Hi Thomas!): If you're confident that
you can guess the right interface at install time, why not do that at
service start up time instead? That way it will adjust to changing
environments.
I don't think it'd be such a gre
I've hit something similar. In my case the error in the logs is
Mar 07 17:59:33 phobos minissdpd-systemd-wrapper[1302]: Error parsing
address/mask (or interface name) : enp3s0
Mar 07 17:59:33 phobos minissdpd-systemd-wrapper[1302]: can't parse
"enp3s0" as a valid address or interface na
Package: minissdpd
Version: 1.6.0-1
Severity: important
Dear Maintainer,
The minissdpd service fails on boot with the following:
minissdpd[834]: ioctl(s, SIOCGIFFLAGS, ...): No such device
minissdpd-systemd-wrapper[834]: Error parsing address/mask (or interface name)
: br-REDACTED
minissdpd-sys
5 matches
Mail list logo