wpa supplicant service depends on 'dbus-system''s service, even when config says (dbus? #f)

  • Done
  • quality assurance status badge
Details
2 participants
  • calcium
  • Marius Bakke
Owner
unassigned
Submitted by
calcium
Severity
normal

Debbugs page

calcium wrote 4 years ago
(address . bug-guix@gnu.org)
c94ab198-0f1b-51c5-f473-9e8314c68a1b@disroot.org
It seems that even when disabling dbus for
wpa-supplicant, the service `dbus-system' is started for
wpa-supplicant.
And trying to stop it with 'herd stop dbus-system' also
stop the wpa-supplicant service (which should not depend on dbus when
configured with (dbus? #f))

```
(service wpa-supplicant-service-type
(wpa-supplicant-configuration
(dbus? #f)))
```

Thanks.
Marius Bakke wrote 4 years ago
(name . calcium)(address . calcium@disroot.org)(address . 43567-done@debbugs.gnu.org)
871rir5958.fsf@gnu.org
calcium <calcium@disroot.org> writes:

Toggle quote (13 lines)
> It seems that even when disabling dbus for
> wpa-supplicant, the service `dbus-system' is started for
> wpa-supplicant.
> And trying to stop it with 'herd stop dbus-system' also
> stop the wpa-supplicant service (which should not depend on dbus when
> configured with (dbus? #f))
>
> ```
> (service wpa-supplicant-service-type
> (wpa-supplicant-configuration
> (dbus? #f)))
> ```

Fixed in d48b17adb91d68acf6fb3f321c05102fcc8c39eb, thanks!
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl9s43MACgkQoqBt8qM6
VPoU5Qf/ZEsM7hHH4t+t29W+G6zPo3Sl7OqYZ9k7cty0SnflBvEALXeiHB64C/bs
eWLqTA6g+DKxhkv0MBlhjn9sRdqOOSpLgM9jUGWh5bL3PxpBJ35qPHKvinigWfxA
mguiCWuHfL3u6S4W921HqJ4Xh/PWNTbSbxloktdxBKUUvWRkzcxlAqBoU9c93XYA
V9JzQzZeWDZ8RiglZDjQQCZ3bnl283ZkhAuLx76QAiD+SZY/bUm6u2ZA27mm/DsL
SZ2ylJBbh+MkM7e8Q1LodY/72jZGl3z3wmGsNg8XJyP706ZmtX6CMJ9wgnUmqRbx
r+/ZBkfvNGIyXxg4C1kitSL2YCLsLQ==
=F4aY
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 43567@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 43567
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help