[Desktop-packages] [Bug 997200] Re: [FFe] Add NetworkManager connectivity config package
I agree, about splitting off other bugs that take advantage of this feature. There is already a whoopsie bug for instance - https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481. Not everything needs to use this (immediately) for it to be useful. (huge +1 to this change btw) -- 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/997200 Title: [FFe] Add NetworkManager connectivity config package Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in network-manager source package in Precise: Won't Fix Status in update-manager source package in Precise: Won't Fix Status in network-manager source package in Quantal: Won't Fix Status in update-manager source package in Quantal: Won't Fix Status in network-manager source package in Raring: Won't Fix Status in update-manager source package in Raring: Won't Fix Bug description: Feature === A separate network-manager-config-connectivity package that contains the 3-line config snippet to enable NetworkManager's connectivity check. This is the same approach taken by Fedora since 2014 (their package is named config-connectivity-fedora). jbicha would like to have ubuntu-gnome-desktop recommend this package for zesty. With this config, GNOME Shell will popup a browser page when a captive portal is detected. The browser page is powered by webkit2gtk. https://help.gnome.org/misc/release-notes/3.14/#captive-portals By making it a separate package, it is very easy for Ubuntu flavors to opt in to installing it by default if they choose. And it's very easy for users to opt in or out without needing to mess around with system configuration files. This new feature (and how to opt out) will be mentioned in Ubuntu GNOME's Release Notes. Enabling the connectivity check by default for all of Ubuntu was discussed almost 5 years ago: https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html Link to new discussion: https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html Git merge proposal attached. Original Bug Report == When in a hotel there is a often a T page that is delivered when connecting to the network. Some combination of network manager and update manager (or something else entirely) doesn't seem to be able to handle this, and update are left in a non-working state after not being able to read package headers file. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 17:27:02 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IpRoute: default via 10.155.32.1 dev wlan0 proto static 10.155.32.0/19 dev wlan0 proto kernel scope link src 10.155.38.82 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/997200/+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 997200] Re: [FFe] Add NetworkManager connectivity config package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/997200 Title: [FFe] Add NetworkManager connectivity config package Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in network-manager source package in Precise: Won't Fix Status in update-manager source package in Precise: Won't Fix Status in network-manager source package in Quantal: Won't Fix Status in update-manager source package in Quantal: Won't Fix Status in network-manager source package in Raring: Won't Fix Status in update-manager source package in Raring: Won't Fix Bug description: Feature === A separate network-manager-config-connectivity package that contains the 3-line config snippet to enable NetworkManager's connectivity check. This is the same approach taken by Fedora since 2014 (their package is named config-connectivity-fedora). jbicha would like to have ubuntu-gnome-desktop recommend this package for zesty. With this config, GNOME Shell will popup a browser page when a captive portal is detected. The browser page is powered by webkit2gtk. https://help.gnome.org/misc/release-notes/3.14/#captive-portals By making it a separate package, it is very easy for Ubuntu flavors to opt in to installing it by default if they choose. And it's very easy for users to opt in or out without needing to mess around with system configuration files. This new feature (and how to opt out) will be mentioned in Ubuntu GNOME's Release Notes. Enabling the connectivity check by default for all of Ubuntu was discussed almost 5 years ago: https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html Link to new discussion: https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html Git merge proposal attached. Original Bug Report == When in a hotel there is a often a T page that is delivered when connecting to the network. Some combination of network manager and update manager (or something else entirely) doesn't seem to be able to handle this, and update are left in a non-working state after not being able to read package headers file. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 17:27:02 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IpRoute: default via 10.155.32.1 dev wlan0 proto static 10.155.32.0/19 dev wlan0 proto kernel scope link src 10.155.38.82 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/997200/+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 997200] Re: [FFe] Add NetworkManager connectivity config package
** Description changed: Feature === A separate network-manager-config-connectivity package that contains the 3-line config snippet to enable NetworkManager's connectivity check. This is the same approach taken by Fedora since 2014 (their package is named config-connectivity-fedora). jbicha would like to have ubuntu-gnome-desktop recommend this package for zesty. With this config, GNOME Shell will popup a browser page when a captive portal is detected. The browser page is powered by webkit2gtk. https://help.gnome.org/misc/release-notes/3.14/#captive-portals By making it a separate package, it is very easy for Ubuntu flavors to opt in to installing it by default if they choose. And it's very easy for users to opt in or out without needing to mess around with system configuration files. This new feature (and how to opt out) will be mentioned in Ubuntu GNOME's Release Notes. Enabling the connectivity check by default for all of Ubuntu was discussed almost 5 years ago: https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html + + Link to new discussion: + https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html Git merge proposal attached. Original Bug Report == When in a hotel there is a often a T page that is delivered when connecting to the network. Some combination of network manager and update manager (or something else entirely) doesn't seem to be able to handle this, and update are left in a non-working state after not being able to read package headers file. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 17:27:02 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IpRoute: default via 10.155.32.1 dev wlan0 proto static 10.155.32.0/19 dev wlan0 proto kernel scope link src 10.155.38.82 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled ** Changed in: network-manager (Ubuntu) Status: Triaged => New -- 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/997200 Title: [FFe] Add NetworkManager connectivity config package Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: New Status in update-manager package in Ubuntu: Confirmed Status in network-manager source package in Precise: Won't Fix Status in update-manager source package in Precise: Won't Fix Status in network-manager source package in Quantal: Won't Fix Status in update-manager source package in Quantal: Won't Fix Status in network-manager source package in Raring: Won't Fix Status in update-manager source package in Raring: Won't Fix Bug description: Feature === A separate network-manager-config-connectivity package that contains the 3-line config snippet to enable NetworkManager's connectivity check. This is the same approach taken by Fedora since 2014 (their package is named config-connectivity-fedora). jbicha would like to have ubuntu-gnome-desktop recommend this package for zesty. With this config, GNOME Shell will popup a browser page when a captive portal is detected. The browser page is powered by webkit2gtk. https://help.gnome.org/misc/release-notes/3.14/#captive-portals By making it a separate package, it is very easy for Ubuntu flavors to opt in to installing it by default if they choose. And it's very easy for users to opt in or out without needing to mess around with system configuration files. This new feature (and how to opt out) will be mentioned in Ubuntu GNOME's Release Notes. Enabling the connectivity check by default for all of Ubuntu was discussed almost 5 years ago: https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html Link to new discussion: https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html Git merge proposal attached.
