wpa-supplicant dbus failure leads to networking service failure

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

Debbugs page

Christopher Howard wrote 5 years ago
(address . bug-guix@gnu.org)
fa92e4b242e05a58b70e86f4328a58b5fb0c24df.camel@alaskasi.com
Under this guix commit, wpa_supplicant service fails to initialize,
which takes out networking also.

'''
root@eowyn ~# guix describe
Generation 2 Dec 17 2019 08:30:38 (current)
guix 328dd9b
branch: master
commit: 328dd9b7c2030dfb66013e12f055b5b449c94007
'''

From /var/log/messages:

'''
Dec 17 09:31:29 localhost wpa_supplicant[361]: dbus: Could not request
service name: already registered
Dec 17 09:31:46 localhost vmunix: [ 35.824562] input: HDA Intel Rear
Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Dec 17 09:31:46 localhost vmunix: [ 35.824618] input: HDA Intel Line
as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Dec 17 09:31:46 localhost vmunix: [ 35.824673] input: HDA Intel Line
Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Dec 17 09:31:46 localhost vmunix: [ 35.824740] input: HDA Intel Front
Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Dec 17 09:31:46 localhost vmunix: [ 36.012141] fbcon: inteldrmfb
(fb0) is primary device
Dec 17 09:31:46 localhost vmunix: [ 36.048479] Console: switching to
colour frame buffer device 240x75
Dec 17 09:31:46 localhost vmunix: [ 36.070192] i915 0000:00:02.0:
fb0: inteldrmfb frame buffer device
Dec 17 09:31:46 localhost vmunix: [ 36.305107] iTCO_vendor_support:
vendor-support=0
Dec 17 09:31:46 localhost vmunix: [ 36.380964] gpio_ich
gpio_ich.1.auto: GPIO from 462 to 511
Dec 17 09:31:47 localhost vmunix: [ 36.403431] iTCO_wdt: Intel TCO
WatchDog Timer Driver v1.11
Dec 17 09:31:47 localhost vmunix: [ 36.403469] iTCO_wdt: Found a ICH7
or ICH7R TCO device (Version=2, TCOBASE=0x0860)
Dec 17 09:31:47 localhost vmunix: [ 36.403620] iTCO_wdt: initialized.
heartbeat=30 sec (nowayout=0)
Dec 17 09:31:47 localhost vmunix: [ 36.778818] tg3 0000:02:00.0
enp2s0: renamed from eth0
Dec 17 09:31:29 localhost dbus-daemon[321]: [system] Activating service
name='org.freedesktop.Accounts' requested by ':1.6' (uid=0 pid=360
comm="/gnu/store/akg524gv9skpl3pyj36rcw61xvpk3131-g
dm-3.") (using servicehelper)
Dec 17 09:31:47 localhost vmunix: [ 37.379918] dcdbas dcdbas: Dell
Systems Management Base Driver (version 5.6.0-3.3)
Dec 17 09:31:47 localhost vmunix: [ 37.446154] intel_powerclamp: No
package C-state available
Dec 17 09:31:47 localhost vmunix: [ 44.047624] usb 1-3.4.4: Warning!
Unlikely big volume range (=496), cval->res is probably wrong.
Dec 17 09:31:47 localhost vmunix: [ 44.047627] usb 1-3.4.4: [51] FU
[Mic Playback Volume] ch = 1, val = 0/7936/16
Dec 17 09:31:48 localhost vmunix: [ 44.052371] usb 1-3.4.4: Warning!
Unlikely big volume range (=1008), cval->res is probably wrong.
Dec 17 09:31:48 localhost vmunix: [ 44.052373] usb 1-3.4.4: [49] FU
[Speaker Playback Volume] ch = 2, val = -16129/-1/16
Dec 17 09:31:48 localhost vmunix: [ 44.057121] usb 1-3.4.4: Warning!
Unlikely big volume range (=496), cval->res is probably wrong.
Dec 17 09:31:48 localhost vmunix: [ 44.057123] usb 1-3.4.4: [50] FU
[Mic Capture Volume] ch = 1, val = 0/7936/16
Dec 17 09:31:48 localhost vmunix: [ 44.057512] usbcore: registered
new interface driver snd-usb-audio
Dec 17 09:31:48 localhost vmunix: [ 44.906195] usbcore: registered
new interface driver usbkbd
Dec 17 09:31:48 localhost vmunix: [ 45.868354] usbcore: registered
new interface driver usbmouse
Dec 17 09:31:30 localhost wpa_supplicant[361]: Failed to initialize
wpa_supplicant
Dec 17 09:31:32 localhost dbus-daemon[321]: [system] Activating service
name='org.freedesktop.PolicyKit1' requested by ':1.7' (uid=0 pid=365
comm="/gnu/store/awhfvskmqyf1p1ddnh9v9s7pqh7cdfyl
-accoun") (using servicehelper)
Dec 17 09:31:48 localhost shepherd[1]: Service wpa-supplicant could not
be started.
Dec 17 09:31:48 localhost shepherd[1]: Service networking depends on
wpa-supplicant.
'''

'''
root@eowyn ~# herd start networking
Service wpa-supplicant could not be started.
Service networking depends on wpa-supplicant.
Service networking could not be started.
herd: failed to start service networking
'''

from NeoFetch:
'''
OS: Guix System 328dd9b7c2030dfb66013e12f055b5b449c94007 x86_64
Host: Vostro 230 00
Kernel: 5.1.2-gnu
Uptime: 8 mins
Packages: 55 (guix-system), 30 (guix-user)
Shell: bash 5.0.7
DE: GNOME 3.28.2
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: .gnome-terminal
CPU: Intel Core 2 Duo E7500 (2) @ 2.291GHz
GPU: Intel 4 Series Chipset
Memory: 1496MiB / 3909MiB
'''

Please let me know if there is a workaround.

--
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com
Christopher Howard wrote 5 years ago
bug#38653: Acknowledgement (wpa-supplicant dbus failure leads to networking service failure)
(address . 38653@debbugs.gnu.org)
4abad7e3324fcb19aaa97fdf5cfbd91dc1eb3735.camel@alaskasi.com
I took the neofetch pull after rebooting into an older profile, so some
data there might be suspect.

--
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com
Marius Bakke wrote 5 years ago
Re: bug#38653: wpa-supplicant dbus failure leads to networking service failure
87a765p3s5.fsf@devup.no
Christopher,

Thanks for the bug report, and sorry for the late response.

Christopher Howard <christopher@alaskasi.com> writes:

Toggle quote (18 lines)
> Under this guix commit, wpa_supplicant service fails to initialize,
> which takes out networking also.
>
> '''
> root@eowyn ~# guix describe
> Generation 2 Dec 17 2019 08:30:38 (current)
> guix 328dd9b
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 328dd9b7c2030dfb66013e12f055b5b449c94007
> '''
>
> From /var/log/messages:
>
> '''
> Dec 17 09:31:29 localhost wpa_supplicant[361]: dbus: Could not request
> service name: already registered

I suspect what happened is that you are using
wpa-supplicant-service-type, and also added 'wpa-supplicant' to the
(packages ...) field of your system configuration. The latter will
include a D-Bus policy file for "fi.w1.wpa_supplicant1", which
wpa-supplicant-service-type also tries to register.

As a workaround, you can set (dbus? #f) in wpa-supplicant-configuration,
or remove 'wpa-supplicant' from the system packages. If you want
wpa-supplicant installed globally, you can use 'wpa-supplicant-minimal'
instead.

Can you confirm?

Not sure how we can make this more robust. The easiest fix is probably
to default to (dbus? #f); the only program I know that use the D-Bus
interface is NetworkManager, which has its own service in Guix.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl4ywZsACgkQoqBt8qM6
VPqh/QgAnUTsxlC3aFTyyYCrfyAdbaDKAVMRF+wlg63scP1L4SNzR07zKawNGY5c
mj9Svd6JEchrBC7VsfD3Mp9QwnaBzIfR4uYOnpOI4XAmL3GL+Py9HdPE9bW36Yxx
3tSkcuqqXPw9lQlNbwxUNjHGBxvC4I5kxSmk9D3IPdyy51NAhsQ6jCAdRFSW2i3V
LCvuZkcRTGijQu9BvHUBeXboYdm8xTAPJKNjNTZ3yewF+TBdCenCN9Ag25AfEx4J
2Prr2bz5Gp8khe4Df3JcNz0Mk9/X9jmi2oflPis7UKFJnRZ9SyK5NokmCDQ6LFBb
0I7Qx+T0K/dcYvUD+7AQqcBcteaVLg==
=WiZs
-----END PGP SIGNATURE-----

Christopher Howard wrote 5 years ago
9a05beb67c3b632532927b5be80318d48ee16cef.camel@alaskasi.com
Hi, it has been so long... I think the last config.scm I tried to use
(some time ago) was:

"""
(use-modules (gnu)
(gnu packages cups)
(gnu packages scanner))

(use-service-modules desktop networking ssh xorg cups)

(operating-system
(locale "en_US.utf8")
(timezone "America/Anchorage")
(keyboard-layout
(keyboard-layout "us" "altgr-intl"))
(bootloader
(bootloader-configuration
(bootloader grub-bootloader)
(target "/dev/sda")
(keyboard-layout keyboard-layout)))
(mapped-devices
(list (mapped-device
(source
(uuid "e95c1dba-a729-4a99-a5fd-d756539e545e"))
(target "cryptroot")
(type luks-device-mapping))))
(file-systems
(cons* (file-system
(mount-point "/")
(device "/dev/mapper/cryptroot")
(type "ext4")
(dependencies mapped-devices))
%base-file-systems))
(host-name "eowyn")
(users (cons* (user-account
(name "christopher")
(comment "Christopher Howard")
(group "users")
(home-directory "/home/christopher")
(supplementary-groups
'("wheel" "netdev" "audio" "video"
"dialout" "lp" "disk" "floppy"
"cdrom" "lpadmin")))
%base-user-accounts))
(packages
(append
(list (specification->package "nss-certs"))
%base-packages))
(services
(modify-services
(append
(list (service gnome-desktop-service-type)
(service openssh-service-type)
(set-xorg-configuration
(xorg-configuration
(keyboard-layout keyboard-layout)))
(service cups-service-type
(cups-configuration
(web-interface? #t)
(extensions
(list hplip-minimal cups-filters)))))
%desktop-services)
(udev-service-type
config =>
(udev-configuration (inherit config)
(rules (cons sane-backends
(udev-configuration-rules
config))))))))

"""

I had more or less given up on bothering to try to upgrade system until
the next official guix release. That would be the ideal time for
another test run of this, so I could update both system and all my user
packages as well to the same target. Is there a rough idea of when the
next official release is coming?


-----Original Message-----
From: Marius Bakke <mbakke@fastmail.com>
To: Christopher Howard <christopher@alaskasi.com>, 38653@debbugs.gnu.or
g
Subject: Re: bug#38653: wpa-supplicant dbus failure leads to networking
service failure
Date: Thu, 30 Jan 2020 12:44:26 +0100

Christopher,
Thanks for the bug report, and sorry for the late response.
Christopher Howard <christopher@alaskasi.com> writes:
Under this guix commit, wpa_supplicant service fails to
initialize,which takes out networking also.
'''root@eowyn ~# guix describeGeneration 2 Dec 17 2019 08:30:38
(current) guix 328dd9b repository URL: https://git.savannah.gnu.org
/git/guix.gitt branch: master commit:
328dd9b7c2030dfb66013e12f055b5b449c94007'''
From /var/log/messages:
'''Dec 17 09:31:29 localhost wpa_supplicant[361]: dbus: Could not
requestservice name: already registered
I suspect what happened is that you are usingwpa-supplicant-service-
type, and also added 'wpa-supplicant' to the(packages ...) field of
your system configuration. The latter willinclude a D-Bus policy file
for "fi.w1.wpa_supplicant1", whichwpa-supplicant-service-type also
tries to register.
As a workaround, you can set (dbus? #f) in wpa-supplicant-
configuration,or remove 'wpa-supplicant' from the system packages. If
you wantwpa-supplicant installed globally, you can use 'wpa-supplicant-
minimal'instead.
Can you confirm?
Not sure how we can make this more robust. The easiest fix is
probablyto default to (dbus? #f); the only program I know that use the
D-Businterface is NetworkManager, which has its own service in Guix.

--
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com
Attachment: file
Christopher Howard wrote 5 years ago
bebc317f218e8bd222ff3c5bb5df606b16fba90c.camel@alaskasi.com
I updated userland and system to
9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3 and am not experiencing this
problem now. You may close the ticket.


--
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com
Attachment: file
Marius Bakke wrote 5 years ago
871rqx880b.fsf@devup.no
Christopher Howard <christopher@alaskasi.com> writes:

Toggle quote (4 lines)
> I updated userland and system to
> 9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3 and am not experiencing this
> problem now. You may close the ticket.

Great, thanks for following up. I'm closing this ticket now by adding a
'-close' to the bug email address.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl5GxnQACgkQoqBt8qM6
VPprPgf/cnNdurflfZKSDlxaTnwtTcclat84YCSiZt5A8qTj+ZPdRrPERy/9+5QO
qA0+2lbU27PYtD4fE8jviDYNmfypMXa0HxZjXEncITn/jswtOVYuVeD5t0Kk4VA/
NBOGUW1ujKP4JFdXosZjd1NoPEKKJ9FDazZGDpSTkxaWwIYomJyd/Kms2w78StyR
C2GeT9DoW353706a9y3suJYzT3BovzMaU3Igzlmx/Xao9+yYPU+bxguDw/CA5ACj
fvcHSihdFC72HD2yYgd5EqJ22Pm0fSaXznlJLTNVNXgEapVhlE5DNqLBBUUhM2kA
eRZ+SSq0h6a6miVoWJ8dIptuXQynCg==
=AmC4
-----END PGP SIGNATURE-----

?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 38653
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