I believe it's got something to do with NetworkManager, because mpc
started working as soon as I run:
$ sudo service network-manager stop
And then I run this, and while trying to connect, or later if connecting
fails, mpc won't work again:
$ sudo service network-manager start
The version of NetworkManager installed is 0.9.4.0-10 on wheezy. I
believe NM kind of advertises to the system if there is a connection
available. As an example, if configured as such, Claws Mail will only
check for emails based on information passed by NetworkManager.
On Mon, 9 Jun 2014 10:46:12 -0400, Tom H wrote:
For testing only!: Does mpc run without the network being up if you
add "127.0.2.2 r.usyncapp.com." (Trying to determine whether mpc needs
something from that host or whether it just needs to resolve the
hostname.)
r.usyncapp.com. has something to do with Bittorrent Sync, but disabling
btsync or adding that line to /etc/hosts won't make any difference.
On Mon, 9 Jun 2014 10:46:12 -0400, Tom H wrote:
> If the OP's problem has to do with dns resolution and the OP's using
> NM, then the lack of a "127.0.1.1" entry is probably a problem because
> NM uses dnsmasq by default and "/etc/resolv.conf" is then set to
> "127.0.1.1".
I had a look, and network-manager recommends dnsmasq-base, which I don't
have installed.
Thanks to all for your help!
Teresa and Junior
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53967607.4010...@gmail.com
