[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
** Attachment added: "Screenshot from 2022-07-08 09-16-59.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+attachment/5602037/+files/Screenshot%20from%202022-07-08%2009-16-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
By setting the priority quite high (see attachment) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
I have also reported the issue upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1016 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1016 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1016 ** Description changed: 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 hotpot to be fully functional on startup + 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 + 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 + 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: New Bug description: 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 NonfreeK
[Desktop-packages] [Bug 1973629] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593893/+files/nmcli-dev.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593892/+files/nmcli-con.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593891/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593890/+files/RfKill.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.veth2665f1e.txt
apport information ** Attachment added: "NetDevice.veth2665f1e.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593882/+files/NetDevice.veth2665f1e.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593881/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593886/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.veth3b712b0.txt
apport information ** Attachment added: "NetDevice.veth3b712b0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593883/+files/NetDevice.veth3b712b0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.wlp3s0.txt
apport information ** Attachment added: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593885/+files/NetDevice.wlp3s0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.enp2s0.txt
apport information ** Attachment added: "NetDevice.enp2s0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593880/+files/NetDevice.enp2s0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.docker0.txt
apport information ** Attachment added: "NetDevice.docker0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593879/+files/NetDevice.docker0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593889/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593887/+files/PciNetwork.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593888/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.veth542edda.txt
apport information ** Attachment added: "NetDevice.veth542edda.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593884/+files/NetDevice.veth542edda.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593877/+files/IpAddr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593878/+files/IwConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593876/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
apport information ** Tags added: apport-collected wayland-session ** Description changed: 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 hotpot to be 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 ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593875/+files/CRDA.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: 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 hotpot to be 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
[Desktop-packages] [Bug 1973629] [NEW] Wifi hotspot not configured correctly on restart
Public bug reported: 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 hotpot to be 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) ** Affects: dconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Wifi disabled while hotspot is running" https://bugs.launchpad.net/bugs/1973629/+attachment/5590114/+files/screen1.png ** Attachment removed: "Wifi disabled while hotspot is running" https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1973629/+attachment/5590114/+files/screen1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dconf in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in dconf package in Ubuntu: New Bug description: 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 hotpot to be 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
