Public bug reported:
I do not have a wealth of knowledge when it comes to networking and the inner
working of network manager, but upon starting my computer I noticed that
NetworkManager was failing to start correctly.
I checked my syslog in hope of finding a reason for this problem and here are
the lines that seems to be the cause:
-
Nov 19 10:39:04 NetworkManager[12596]: dnsmasq exited with error:
Filesystem problem (missing file/directory; permissions; etc) (3)
Nov 19 10:39:04 NetworkManager[12596]: Writing DNS information to
/sbin/resolvconf
Nov 19 10:39:04 NetworkManager[12596]: DNS: plugin dnsmasq child quit
unexpectedly; refreshing DNS
Nov 19 10:39:04 NetworkManager[12596]: DNS: starting dnsmasq...
Nov 19 10:39:04 NetworkManager[12596]: dnsmasq not available on the
bus, can't update servers.
Nov 19 10:39:04 NetworkManager[12596]: [1447929544.956041]
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus:
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such
name
Nov 19 10:39:04 NetworkManager[12596]: DNS: plugin dnsmasq update
failed
Nov 19 10:39:04 NetworkManager[12596]: Writing DNS information to
/sbin/resolvconf
Nov 19 10:39:04 NetworkManager[12596]: dnsmasq: failed to open pidfile
/run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory
Nov 19 10:39:04 dnsmasq[14381]: failed to open pidfile
/run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory
Nov 19 10:39:04 Misa dnsmasq[14381]: FAILED to start up
-
As you will notice in the configuration file of NetworkManager, I worked
around this problem by commenting the use of dnsmasq as a dns plugin.
However, that is not a long term solution and if more users have the
same problem it might help to have a real solution.
I am currently running the desktop version of Ubuntu 15.10-64bits with
network-manager 1.0.4-0ubuntu5.1 installed.
Thank you in advance for your help.
Sincerely.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Thu Nov 19 11:24:45 2015
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-07-13 (128 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
default via 10.78.192.1 dev eth0 proto static metric 100
10.78.192.0/20 dev eth0 proto kernel scope link src 10.78.206.15 metric 100
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=false
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SourcePackage: network-manager
UpgradeStatus: Upgraded to wily on 2015-11-12 (6 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2015-11-19T11:22:54.882153
nmcli-dev:
DEVICE TYPE STATEDBUS-PATH
CONNECTION CON-UUID CON-PATH
eth0ethernet connected/org/freedesktop/NetworkManager/Devices/0
LifeSource 23d38626-0b26-4ffb-b610-da784136236f
/org/freedesktop/NetworkManager/ActiveConnection/0
wlan0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 --
----
lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 --
----
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/1517855
Title:
NetworkManager dnsmasq failing on start
Status in network-manager package in Ubuntu:
New
Bug description:
I do not have a wealth of knowledge when it comes to networking and the inner
working of network manager, but upon starting my computer I noticed that
NetworkManager was failing to start correctly.
I checked my syslog in hope of finding a reason for this problem and here are
the lines that seems to be the cause:
-
Nov 19 10:39:04 NetworkManager[12596]: dnsmasq exited with error:
