Question.
-
@lambdageek That's very interesting… to your knowledge, am I doing something *wrong* if I just switch publish-workstation to yes?
As far as I know what you just said is *correct*, but the fact I know what avahi is, but I don't know what nssswitch/libnss-mdns are, makes me nervous about touching the latter when making a change to avahi worked
@mcc I have no idea what i'm doing :-(
Just a guess: did sudo systemctl restart avahi-daemon.service in fact restart avahi? or did it start it? Maybe it wasn't running before?
what happens if you change the setting back to "no" and restart?
-
This is deeply upsetting https://mastodon.social/@lambdageek/116099461735423343
Another upsetting thing: Apparently systemd has its own mdns setup: https://www.reddit.com/r/debian/comments/1mnvzln/the_debian_technical_committee_made_a_baffling/ which Debian may, or may not, have disabled intentionally in Debian 13 (the file this poster claims is present is not present) because they expect they use Avahi instead. I don't understand why I'd use Avahi instead of systemd, or, if I decided systemd's mdns were better, how I'd switch to it.
@mcc for historical reasons the primary interface for software that wants to interact with mdns beyond simple name to IP resolution is the Avahi daemon dbus interface, and systemd-resolved does not implement that.
-
@mcc for historical reasons the primary interface for software that wants to interact with mdns beyond simple name to IP resolution is the Avahi daemon dbus interface, and systemd-resolved does not implement that.
@elomatreb ow. ow. ow. ow. ow.
thanks for the explanation.
-
@fcbsd Who controls the contents of /etc/avahi/avahi-daemon.conf? The Debian installer, or me? I sincerely do not know the answer to this question
@mcc I don't know the answer to that either, but a Debian tablet that I installed trixie on recently has:
publish-workstation=no
and systemctl status says the avahi-daemon.services is enables are running, and pinging hostname.local worked... -
@mcc I have no idea what i'm doing :-(
Just a guess: did sudo systemctl restart avahi-daemon.service in fact restart avahi? or did it start it? Maybe it wasn't running before?
what happens if you change the setting back to "no" and restart?
@lambdageek Oh, that is such a good question :(
-
This is deeply upsetting https://mastodon.social/@lambdageek/116099461735423343
Another upsetting thing: Apparently systemd has its own mdns setup: https://www.reddit.com/r/debian/comments/1mnvzln/the_debian_technical_committee_made_a_baffling/ which Debian may, or may not, have disabled intentionally in Debian 13 (the file this poster claims is present is not present) because they expect they use Avahi instead. I don't understand why I'd use Avahi instead of systemd, or, if I decided systemd's mdns were better, how I'd switch to it.
*rolling around on the floor in pain* this is even more upsetting
https://mastodon.social/@lambdageek/116099504356976778
this worked
the problem was not the publish-workstation=no
the problem was not debian; nothing changed
my local avahi daemon had simply locked up
at least one other person replied to say their avahi daemon wedges semifrequently and they have to restart it
now i kinda *do* want to use the systemd mdns provider
however unfortunately https://chaos.social/@elomatreb/116099505178400601
-
*rolling around on the floor in pain* this is even more upsetting
https://mastodon.social/@lambdageek/116099504356976778
this worked
the problem was not the publish-workstation=no
the problem was not debian; nothing changed
my local avahi daemon had simply locked up
at least one other person replied to say their avahi daemon wedges semifrequently and they have to restart it
now i kinda *do* want to use the systemd mdns provider
however unfortunately https://chaos.social/@elomatreb/116099505178400601
so to summarize, nothing was wrong, it's just the relevant daemon needed to be rebooted, and that's such a 1990s Linux kinda problem it didn't even occur to me to try it. i thought we were past that
-
@lambdageek Oh, that is such a good question :(
@lambdageek it worked. thank you
-
so to summarize, nothing was wrong, it's just the relevant daemon needed to be rebooted, and that's such a 1990s Linux kinda problem it didn't even occur to me to try it. i thought we were past that
@mcc do you have long uptime? This keeps causing me issues with desktop software because their devs don't seem to test that very well (pipewire leaks FDs until it runs out, KDE's calendar notifications daemon stop, etc.)
-
so to summarize, nothing was wrong, it's just the relevant daemon needed to be rebooted, and that's such a 1990s Linux kinda problem it didn't even occur to me to try it. i thought we were past that
@mcc i fear we will never get past "have you tried turning it on and off again"
-
@mcc i fear we will never get past "have you tried turning it on and off again"
@ratsnakegames It would have worked!! It would have worked!! I trained myself out of "turn it off and on again" and that was the correct solution!!!
-
undefined oblomov@sociale.network shared this topic