network-manager-gnome must depend on dnsmasq for WiFi/Ethernet hotspots to work

[Mikhail Novosyolov]

There is a button in network-manager-gnome GUI that starts a WiFi hotspot, but it does not work out of the box on Ubuntu GNOME 17.04 untill dnsmasq is installed manually.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager-gnome 1.4.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 23 19:22:02 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-04-22 (1 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 192.168.1.1 dev enx582c80139263 proto static metric 100
 192.168.1.0/24 dev enx582c80139263 proto kernel scope link src 192.168.1.100 metric 100
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile

 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 enx582c80139263 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Проводное соединение 2 543da71d-1383-469f-95b0-114ce014d787 /org/freedesktop/NetworkManager/ActiveConnection/7
 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- --
 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.4.4 connected started full enabled enabled enabled enabled enabled

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.