Wifi hotspot does not work when band A is selected

Bug #1975685 reported by Tom Cook
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm using a built-in RTL8822BE WiFi adapter on a Ryzen 7 system. When I create a hotspot by opening the GNOME settings app, opening the WiFi settings page and selecting "Turn on hotspot..." from the drop-down menu, everything works fine. If I then open nm-connection-editor and edit the connection to select band A (5GHz), the hotspot fails to start. If I then open the connection editor again and switch back to automatic band selection, the hotspot works again.

When it fails, this appears in syslog:

May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8638] device (wlo1): Activation: starting connection 'Hotspot' (514f603b-25e2-4c1e-9220-7b77ed966ff5)
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8643] device (wlo1): supplicant interface state: completed -> disconnected
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8653] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8676] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8783] device (wlo1): Activation: (wifi) access point 'Hotspot' has security, but secrets are required.
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8783] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8800] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8810] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 25 10:21:30 frog NetworkManager[815]: <info> [1653470490.8883] device (wlo1): Activation: (wifi) connection 'Hotspot' has security, and secrets exist. No new secrets needed.
May 25 10:21:30 frog wpa_supplicant[866]: wlo1: Failed to start AP functionality
May 25 10:21:56 frog NetworkManager[815]: <warn> [1653470516.1521] device (wlo1): Activation: (wifi) Hotspot network creation took too long, failing activation
May 25 10:21:56 frog NetworkManager[815]: <info> [1653470516.1522] device (wlo1): state change: config -> failed (reason 'supplicant-timeout', sys-iface-state: 'managed')
May 25 10:21:56 frog NetworkManager[815]: <warn> [1653470516.1526] device (wlo1): Activation: failed for connection 'Hotspot'
May 25 10:21:56 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
May 25 10:21:56 frog NetworkManager[815]: <info> [1653470516.1530] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
May 25 10:21:56 frog wpa_supplicant[866]: wlo1: Reject scan trigger since one is already pending
May 25 10:21:59 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

I'm guessing that NetworkManager is getting the way it drives wpa_supplicant wrong when the 5GHz band is selected, but it's only a guess.

Ubuntu version is:

tkcook@frog:~$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04

NetworkManager version is:

tkcook@frog:~$ apt-cache policy network-manager-gnome
network-manager-gnome:
  Installed: 1.24.0-1ubuntu3
  Candidate: 1.24.0-1ubuntu3
  Version table:
 *** 1.24.0-1ubuntu3 500
        500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager-gnome 1.24.0-1ubuntu3
Uname: Linux 5.18.0 x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 25 10:29:37 2022
InstallationDate: Installed on 2021-08-27 (270 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to jammy on 2022-05-05 (19 days ago)
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.36.4 connected started full enabled enabled enabled enabled disabled

Revision history for this message
Tom Cook (tom-k-cook) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.