Problems with NetworkManager in Mate (Possible Bugs)

Problems with NetworkManager in Mate (Possible Bugs)

Postby ikunat33 on Sun Feb 17, 2013 8:14 pm

First of all let me say I love the clean intuitive feel of the Mate Desktop. I have missed this in Ubuntu over the last few years and moved to Mint and then to Debian. I have come back to Mint because of Mate.

Now on to the 2 issues (and one question) I seem to have had in the first 2 minutes running:

1 - /etc/resolv.conf not updated
2 - /restarting network services in terminal MURDERS clock, nm-applet, NetworkManager
Q - /gnome-keyring daemon... should I really be seeing it try to load in the Mate release of Mint? It fails but is it needed? does it lead to the problem 1 and 2?

I could not find these things listed as bugs so I hope it is not just me. I looked for ways to post the bug but everything said closed. Any Suggestions??
I am hoping that someone has a solution other than manually plugging in my dhcp all the time because I am always switching networks and it would drive me nuts.
** sorry my pics are so large. you may have to open them in separate windows to get a good look at them**


Problem 1.. /etc/resolv.conf not updating

The NetworkManager joined my Network Nice and seamlessly but Firefox could not see anything.
First I looked at the connection information and, being as everything was there, said something like "uhhhhh...eh?"
so rejoined the network with no change.
checked that my buddy had connection with the same settings on his windows system.
turned the computer off and then on again (Moss suggested this several times)
all with no luck.

in the next image you can see that 1.) network manager reports DNS properly 2.) Menu->Administration->Network does not know about the DNS 3.) cat /etc/resolv.conf produces nothing.

WhatDNSDude.png
NetworkManager reports DNS. Networking thinks he is insane!
WhatDNSDude.png (172.33 KiB) Viewed 1598 times


Here are the associated logs with disconnecting from the network and then connecting.

syslog on disconnect:

[color=#0000BF]Feb 17 13:16:06 XTC NetworkManager[767]: <info> (wlan0): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
Feb 17 13:16:06 XTC NetworkManager[767]: <info> (wlan0): deactivating device (reason 'user-requested') [39]
Feb 17 13:16:06 XTC NetworkManager[767]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1841
Feb 17 13:16:06 XTC kernel: [ 235.655031] wlan0: deauthenticating from 00:25:9c:00:b4:49 by local choice (reason=3)
Feb 17 13:16:06 XTC wpa_supplicant[851]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
Feb 17 13:16:06 XTC kernel: [ 235.671113] cfg80211: All devices are disconnected, going to restore regulatory settings
Feb 17 13:16:06 XTC kernel: [ 235.671123] cfg80211: Restoring regulatory settings
Feb 17 13:16:06 XTC kernel: [ 235.671132] cfg80211: Calling CRDA to update world regulatory domain
Feb 17 13:16:06 XTC NetworkManager[767]: <warn> DNS: plugin dnsmasq update failed
Feb 17 13:16:06 XTC NetworkManager[767]: <info> ((null)): removing resolv.conf from /sbin/resolvconf
Feb 17 13:16:06 XTC dnsmasq[1845]: setting upstream servers from DBus
Feb 17 13:16:06 XTC kernel: [ 235.678527] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
Feb 17 13:16:06 XTC kernel: [ 235.678532] cfg80211: World regulatory domain updated:
Feb 17 13:16:06 XTC kernel: [ 235.678534] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 17 13:16:06 XTC kernel: [ 235.678537] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 17 13:16:06 XTC kernel: [ 235.678540] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 17 13:16:06 XTC kernel: [ 235.678542] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 17 13:16:06 XTC kernel: [ 235.678545] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 17 13:16:06 XTC kernel: [ 235.678547] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 17 13:16:06 XTC dbus[710]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb 17 13:16:06 XTC NetworkManager[767]: <info> (wlan0): supplicant interface state: completed -> disconnected
Feb 17 13:16:06 XTC dbus[710]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'


Syslog on connect:

Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) starting connection 'Gortex Kat'
Feb 17 13:18:22 XTC NetworkManager[767]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0/wireless): access point 'Gortex Kat' has security, but secrets are required.
Feb 17 13:18:22 XTC NetworkManager[767]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 17 13:18:22 XTC NetworkManager[767]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0/wireless): connection 'Gortex Kat' has security, and secrets exist. No new secrets needed.
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Config: added 'ssid' value 'Gortex Kat'
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Config: added 'scan_ssid' value '1'
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Config: added 'auth_alg' value 'OPEN'
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Config: added 'psk' value '<omitted>'
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 17 13:18:22 XTC NetworkManager[767]: <info> Config: set interface ap_scan to 1
Feb 17 13:18:22 XTC NetworkManager[767]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 17 13:18:24 XTC wpa_supplicant[851]: wlan0: SME: Trying to authenticate with 00:25:9c:00:b4:49 (SSID='Gortex Kat' freq=2437 MHz)
Feb 17 13:18:24 XTC kernel: [ 373.354029] wlan0: authenticate with 00:25:9c:00:b4:49
Feb 17 13:18:24 XTC kernel: [ 373.359327] wlan0: send auth to 00:25:9c:00:b4:49 (try 1/3)
Feb 17 13:18:24 XTC NetworkManager[767]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 17 13:18:24 XTC wpa_supplicant[851]: wlan0: Trying to associate with 00:25:9c:00:b4:49 (SSID='Gortex Kat' freq=2437 MHz)
Feb 17 13:18:24 XTC kernel: [ 373.361200] wlan0: authenticated
Feb 17 13:18:24 XTC kernel: [ 373.364061] wlan0: associate with 00:25:9c:00:b4:49 (try 1/3)
Feb 17 13:18:24 XTC NetworkManager[767]: <info> (wlan0): supplicant interface state: authenticating -> associating
Feb 17 13:18:24 XTC kernel: [ 373.379525] wlan0: RX AssocResp from 00:25:9c:00:b4:49 (capab=0x431 status=0 aid=2)
Feb 17 13:18:24 XTC wpa_supplicant[851]: wlan0: Associated with 00:25:9c:00:b4:49
Feb 17 13:18:24 XTC kernel: [ 373.381114] wlan0: associated
Feb 17 13:18:24 XTC NetworkManager[767]: <info> (wlan0): supplicant interface state: associating -> associated
Feb 17 13:18:24 XTC NetworkManager[767]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Feb 17 13:18:24 XTC wpa_supplicant[851]: wlan0: WPA: Key negotiation completed with 00:25:9c:00:b4:49 [PTK=CCMP GTK=TKIP]
Feb 17 13:18:24 XTC wpa_supplicant[851]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:25:9c:00:b4:49 completed (reauth) [id=0 id_str=]
Feb 17 13:18:24 XTC NetworkManager[767]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Feb 17 13:18:24 XTC NetworkManager[767]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Gortex Kat'.
Feb 17 13:18:24 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 17 13:18:24 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Feb 17 13:18:24 XTC NetworkManager[767]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb 17 13:18:24 XTC NetworkManager[767]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 17 13:18:24 XTC NetworkManager[767]: <info> dhclient started with pid 2608
Feb 17 13:18:24 XTC NetworkManager[767]: <info> Activation (wlan0) Beginning IP6 addrconf.
Feb 17 13:18:24 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Feb 17 13:18:24 XTC dhclient: Internet Systems Consortium DHCP Client 4.2.4
Feb 17 13:18:24 XTC dhclient: Copyright 2004-2012 Internet Systems Consortium.
Feb 17 13:18:24 XTC dhclient: All rights reserved.
Feb 17 13:18:24 XTC dhclient: For info, please visit https://www.isc.org/software/dhcp/
Feb 17 13:18:24 XTC dhclient:
Feb 17 13:18:24 XTC NetworkManager[767]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Feb 17 13:18:24 XTC dhclient: Listening on LPF/wlan0/00:13:02:14:ab:8e
Feb 17 13:18:24 XTC dhclient: Sending on LPF/wlan0/00:13:02:14:ab:8e
Feb 17 13:18:24 XTC dhclient: Sending on Socket/fallback
Feb 17 13:18:24 XTC dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 255.255.255.255 port 67
Feb 17 13:18:25 XTC dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Feb 17 13:18:25 XTC dhclient: bound to 192.168.1.101 -- renewal in 42438 seconds.
Feb 17 13:18:25 XTC NetworkManager[767]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Feb 17 13:18:25 XTC NetworkManager[767]: <info> address 192.168.1.101
Feb 17 13:18:25 XTC NetworkManager[767]: <info> prefix 24 (255.255.255.0)
Feb 17 13:18:25 XTC NetworkManager[767]: <info> gateway 192.168.1.1
Feb 17 13:18:25 XTC NetworkManager[767]: <info> nameserver '64.59.144.92'
Feb 17 13:18:25 XTC NetworkManager[767]: <info> nameserver '64.59.150.138'
Feb 17 13:18:25 XTC NetworkManager[767]: <info> domain name 'vc.shawcable.net'
Feb 17 13:18:25 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb 17 13:18:25 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Feb 17 13:18:26 XTC NetworkManager[767]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Feb 17 13:18:26 XTC NetworkManager[767]: <info> ((null)): writing resolv.conf to /sbin/resolvconf
Feb 17 13:18:26 XTC dnsmasq[1845]: setting upstream servers from DBus
Feb 17 13:18:26 XTC dnsmasq[1845]: using nameserver 64.59.150.138#53
Feb 17 13:18:26 XTC dnsmasq[1845]: using nameserver 64.59.144.92#53
Feb 17 13:18:26 XTC NetworkManager[767]: <info> Policy set 'Gortex Kat' (wlan0) as default for IPv4 routing and DNS.
Feb 17 13:18:26 XTC NetworkManager[767]: <info> Activation (wlan0) successful, device activated.
Feb 17 13:18:26 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Feb 17 13:18:26 XTC dbus[710]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb 17 13:18:26 XTC dbus[710]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 17 13:18:26 XTC ntpdate[2654]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Feb 17 13:18:26 XTC ntpdate[2654]: no servers can be used, exiting
Feb 17 13:18:45 XTC NetworkManager[767]: <info> (wlan0): IP6 addrconf timed out or failed.
Feb 17 13:18:45 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Feb 17 13:18:45 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Feb 17 13:18:45 XTC NetworkManager[767]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.


Problem 2... restarting network services in terminal MURDERS clock, nm-applet, NetworkManager

The first image shows what happens to the clock when I stop then start Network Services.

The second Image shows the strangeness it creates with NetworkManager... the job is clearly running but on the network icon where my mouse is it says networking is dissabled. when I click on it a further message comes up saying "NetworkManager is not running" but umm... it is.
You can also see what happens when I try restart nm-applet.
My screenshot would not work while the "NetworkManager is not running" message was displaying for some reason so you will just have to imagine it.

The log files following these imagest show a lot of issues with Dbus when I try to restart NetworkManager and I have nooooo idea what goes on behind those doors.

ClockQuitsWhat.png
Why would the clock die? SNTP???
ClockQuitsWhat.png (352.08 KiB) Viewed 1598 times


NetWorkManagerNotRunningWhat.png
Sorry NetworkManager is not here right now.... UMmm yes it is.
NetWorkManagerNotRunningWhat.png (171.28 KiB) Viewed 1598 times



Syslog on attempt to start NetworkManager anyway:
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> NetworkManager (version 0.9.6.0) is starting...
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> WEXT support is enabled
Feb 17 14:40:36 XTC NetworkManager[3581]: <error> [1361140836.188030] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> DNS: loaded plugin dnsmasq
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_connection_register_g_object: assertion `connection != NULL' failed
Feb 17 14:40:36 XTC NetworkManager[3581]: <error> [1361140836.197243] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (1) Error initializing authority: Could not connect: No such file or directory
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: init!
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: update_system_hostname
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPluginIfupdown: management mode: unmanaged
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/eth0, iface: eth0)
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/eth0, iface: eth0): no ifupdown configuration found.
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/net/wlan0, iface: wlan0)
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: end _init.
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Feb 17 14:40:36 XTC NetworkManager[3581]: Ifupdown: get unmanaged devices count: 0
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: (144578360) ... get_connections.
Feb 17 14:40:36 XTC NetworkManager[3581]: SCPlugin-Ifupdown: (144578360) ... get_connections (managed=false): return empty list.
Feb 17 14:40:36 XTC NetworkManager[3581]: keyfile: parsing The Network ...
Feb 17 14:40:36 XTC NetworkManager[3581]: keyfile: read connection 'The Network'
Feb 17 14:40:36 XTC NetworkManager[3581]: keyfile: parsing Azad-guest ...
Feb 17 14:40:36 XTC NetworkManager[3581]: keyfile: read connection 'Azad-guest'
Feb 17 14:40:36 XTC NetworkManager[3581]: keyfile: parsing Gortex Kat ...
Feb 17 14:40:36 XTC NetworkManager[3581]: keyfile: read connection 'Gortex Kat'
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_connection_register_g_object: assertion `connection != NULL' failed
Feb 17 14:40:36 NetworkManager[3581]: last message repeated 2 times
Feb 17 14:40:36 XTC NetworkManager[3581]: Ifupdown: get unmanaged devices count: 0
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_connection_register_g_object: assertion `connection != NULL' failed
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Feb 17 14:40:36 XTC NetworkManager[3581]: <warn> NameHasOwner request failed: (unknown)
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> trying to start the modem manager...
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_proxy_begin_call_with_timeout: assertion `DBUS_IS_G_PROXY (proxy)' failed
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
Feb 17 14:40:36 XTC NetworkManager[3581]: <warn> could not initialize avahi-autoipd D-Bus proxy
Feb 17 14:40:36 XTC NetworkManager[3581]: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
Feb 17 14:40:36 XTC NetworkManager[3581]: <warn> could not initialize UPower D-Bus proxy
Feb 17 14:40:36 XTC NetworkManager[3581]: <error> [1361140836.204797] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (1) Error initializing authority: Could not connect: No such file or directory
Feb 17 14:40:36 XTC NetworkManager[3581]: <info> monitoring kernel firmware directory '/lib/firmware'.

Thanks for any help.
ikunat33
Level 1
Level 1
 
Posts: 6
Joined: Sat Feb 16, 2013 11:11 pm

Linux Mint is funded by ads and donations.
 

Re: Problems with NetworkManager in Mate (Possible Bugs)

Postby cebe on Wed Sep 04, 2013 6:11 am

Hi,

had the same problem with resolv.conf not getting updated.
Seems to be the case that resolv.conf gets written to /run/resolvconf/resolv.conf instead of /etc/resolv.conf
For me this resulted in slow internet connection as there was a non existing nameserver listed in /etc/resolv.conf which caused timeout on every DNS request.
I removed the resolv.conf in /etc and created a link to solve this issue for me:

Code: Select all
sudo mv /etc/resolv.conf /etc/resolv.conf.old
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf


hope this helps, I think there should be a bug report on this issue. Will try to write one.

best regards,
Carsten
cebe
Level 1
Level 1
 
Posts: 2
Joined: Tue Jul 30, 2013 7:55 am



Return to MATE

Who is online

Users browsing this forum: No registered users and 6 guests