Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#79770 - [passim] should depend on avahi-daemon

Attached to Project: Arch Linux
Opened by Andrej Podzimek (andrej) - Sunday, 24 September 2023, 20:37 GMT
Last edited by freswa (frederik) - Sunday, 24 September 2023, 21:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

fwupd requires a new daemon, passim. This daemon fails to start on the default installation when avahi-daemon is not running.

Workaround / “fix”:

# systemctl enable --now avahi-daemon
# systemctl restart passim
# mkdir /etc/systemd/passim.service.d
# cat <<- 'BLAH' > /etc/systemd/passim.service.d/blah.conf
[Unit]
After=avahi-daemon.service
BLAH

A possible solution would be to make passim depend on avahi-daemon, both on systemd unit level (to make sure avahi-daemon starts before passim) and on the package level (to make sure avahi is installed). (Another option would be to somehow (?) build libpassim so that avahi-daemon is optional, but this sounds infeasible.)

Additional info:
* package version(s)

* config and/or log files etc.
Sep 24 22:20:58 passimd[3960]: failed to contact daemon: failed to contact Avahi: Error calling StartServiceByName for org.freedesktop.Avahi: Unit dbus-org.freedesktop.Avahi.service not found.
Sep 24 22:20:58 systemd[1]: passim.service: Main process exited, code=exited, status=1/FAILURE
Sep 24 22:20:58 systemd[1]: passim.service: Failed with result 'exit-code'.
Sep 24 22:20:58 systemd[1]: Failed to start A local caching server.

* link to upstream bug report, if any
Haven’t checked. (I’m too lazy.) Whether this is an upstream bug depends on whether the unit file (/usr/lib/systemd/system/passim.service) is provided by ArchLinux or by upstream.

Steps to reproduce: Sync everything, install fwupd, perhaps reboot, look at systemctl --failed, try to use fwupdmgr.
This task depends upon

Closed by  freswa (frederik)
Sunday, 24 September 2023, 21:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  Dependency on avahi added.
Comment by Andrej Podzimek (andrej) - Sunday, 24 September 2023, 20:39 GMT
Forgot the package versions:

avahi 1:0.8+r127+g55d783d-1
fwupd 1.9.5-2
passim 0.1.1-1
systemd 254.4-2
Comment by loqs (loqs) - Sunday, 24 September 2023, 20:52 GMT
 FS#79636 
Comment by Andrej Podzimek (andrej) - Sunday, 24 September 2023, 20:56 GMT
Right, in this case enabling of avahi-daemon.service actually sounds like a tremendous overkill.

What would have sufficed is to enable avahi-daemon.socket and that’s it. Then also the After dependency is not needed.
Comment by Andrej Podzimek (andrej) - Sunday, 24 September 2023, 21:03 GMT
So for the record, the only thing that needs to be done is:

systemctl enable --now avahi-daemon.socket

Not an ArchLinux bug in that case; there’s no config file that could fix this automatically.

Loading...