I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot).
The expectation is that the hotspot is fully functional on startup meaning every device connected to it can reach the internet.
Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings.
All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup.
Running Ubuntu 22.04
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dconf-service 0.40.0-3
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 16 19:59:02 2022
InstallationDate: Installed on 2021-12-08 (159 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: dconf
UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-12-08 (173 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
IpRoute:
default via 10.0.0.138 dev enp2s0 proto dhcp metric 100
10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100
10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600
169.254.0.0/16 dev enp2s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
NonfreeKernelModules: nvidia_modeset nvidia
Package: network-manager 1.36.4-2ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Tags: wayland-session jammy
Uname: Linux 5.15.0-33-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago)
UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers
_MarkForUpload: True
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 enabled
no_proxy: localhost,127.0.0.0/8,::1
Thank you for your bug report. If the status is wrong at system start then the problem is probably due to network-manager itself.
Could you trigger the bug and then when the system is in the buggy state do
$ apport-collect 1973629
The issue is probably also worth reporting upstream on https:/