desktop-packages team mailing list archive

[Shahar Or <mightyiampresence@xxxxxxxxx>]

Public bug reported:

`service network-manager stop` does not kill the slave dnsmasq process.

I expected changes that I made to files in
`/etc/NetworkManager/dnsmasq.d/` to come into effect when I used
NetworkManager's init script to restart it.

But the dnsmasq process is not controlled from the init-script.

I know that the inclusion of dnsmasq in NetworkManager has raised some
controversy (bug #993298).

Fixing this issue may help alleviate that somewhat, perhaps?

In any case, I think this should be fixed. Seems like an easy fix to me.
Just make sure that the slave dnsmasq, if exists (as it can be
disabled), is sent some kill signal.

Any thoughts?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 0.9.10.0-4ubuntu21
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 11 23:25:37 2015
IfupdownConfig:
 auto lo
 iface lo inet loopback
 
 #auto eth1
 #iface eth1 inet dhcp
InstallationDate: Installed on 2010-10-12 (1764 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IpRoute:
 default via 192.168.0.1 dev eth0  proto static  metric 100 
 192.168.0.0/24 dev eth0  proto kernel  scope link  metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to wily on 2014-11-11 (273 days ago)
nmcli-dev:
 DEVICE    TYPE      STATE        DBUS-PATH                                  CONNECTION      CON-UUID                              CON-PATH                                           
 eth0      ethernet  connected    /org/freedesktop/NetworkManager/Devices/2  wire to router  fc8584db-811e-4099-acbf-93f53c51b3ef  /org/freedesktop/NetworkManager/ActiveConnection/0 
 eth1      ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --              --                                    --                                                 
 vboxnet1  ethernet  unmanaged    /org/freedesktop/NetworkManager/Devices/3  --              --                                    --                                                 
 lo        loopback  unmanaged    /org/freedesktop/NetworkManager/Devices/0  --              --                                    --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug wily

-- 
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/1483882

Title:
  init-script does not control slave dnsmasq

Status in network-manager package in Ubuntu:
  New

Bug description:
  `service network-manager stop` does not kill the slave dnsmasq
  process.

  I expected changes that I made to files in
  `/etc/NetworkManager/dnsmasq.d/` to come into effect when I used
  NetworkManager's init script to restart it.

  But the dnsmasq process is not controlled from the init-script.

  I know that the inclusion of dnsmasq in NetworkManager has raised some
  controversy (bug #993298).

  Fixing this issue may help alleviate that somewhat, perhaps?

  In any case, I think this should be fixed. Seems like an easy fix to
  me. Just make sure that the slave dnsmasq, if exists (as it can be
  disabled), is sent some kill signal.

  Any thoughts?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 0.9.10.0-4ubuntu21
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 11 23:25:37 2015
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   
   #auto eth1
   #iface eth1 inet dhcp
  InstallationDate: Installed on 2010-10-12 (1764 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  scope link  metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2014-11-11 (273 days ago)
  nmcli-dev:
   DEVICE    TYPE      STATE        DBUS-PATH                                  CONNECTION      CON-UUID                              CON-PATH                                           
   eth0      ethernet  connected    /org/freedesktop/NetworkManager/Devices/2  wire to router  fc8584db-811e-4099-acbf-93f53c51b3ef  /org/freedesktop/NetworkManager/ActiveConnection/0 
   eth1      ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --              --                                    --                                                 
   vboxnet1  ethernet  unmanaged    /org/freedesktop/NetworkManager/Devices/3  --              --                                    --                                                 
   lo        loopback  unmanaged    /org/freedesktop/NetworkManager/Devices/0  --              --                                    --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1483882/+subscriptions