[SOLVED] NetworkManager keeps on reconnecting

My NetworkManager keeps on reconnecting no matter whether I use wired or wireless network. This annoys me a few days.
I find that `sudo systemctl restart NetworkManager` could solve this problem temporarily. After reboot the problem arises again.
My system is up to date. And I am using Gnome 3.
Any idea why does it happen and how could I get rid of it?
Last edited by vanitas (2015-02-04 04:01:10)

@frank604, I didn't enabled dhcpcd, netctl, or wicd.
I ran `journalctl -u NetworkManager.service` and noticed these lines:
Feb 04 10:36:52 xbull NetworkManager[4339]: <warn> the dhcpcd backend does not support IPv6.
Feb 04 10:36:52 xbull NetworkManager[4339]: <info> (enp4s0): device state change: activated -> failed (reason 'dhcp-start-failed') [100 120 15]
After some googling, I find this post: dhcpcd not work with NetworkManager 1.0.
Someone metions that NetworkManager 1.0 embed an internal DHCP client, and the DHCP client does not support IPv6 yet.
I edit the connection and disable IPv6, then the problem disappears.
Thanks for your help!

Similar Messages

Why does my 4s with ios7 wifi keep disconnecting/reconnecting?

why does my 4s with ios7 wifi keep disconnecting/reconnecting?

Same problem here. It just keeps connecting/disconnecting indefinitely. This does not started immediately after IO7 upgrade and it does not happen all the time. Sometimes it does it, sometimes not. Very frustrating. So far no solution found.

NetworkManager dis- and reconnects

Hi everyone,
there is an annoying problem that keeps me from using NetworkManager (latest version i.e. 0.7.0-1). It disconnects my network connections when I log out (that is, I quit nm-applet) and reconnects when I log in.
I want it to keep my connections alive until I tell it otherwise. It shouldn't care about whether I'm logged in or the nm-applet is running.
Is there a way to change this behavior? Maybe the problem lies within nm-applet as it might tell the daemon to reconnect every time it starts up.
Thanks in advance!
Last edited by Vortex375 (2009-02-24 02:59:41)

It seems this can be "fixed" by configuring the network connection as "available to all users".
It actually makes sense to disconnect when you log out otherwise...:rolleyes:

[SOLVED]NetworkManager won't work since updating to KDE 4.3.4

Hello there,
I'm running Arch64 on Qosmio X300 notebook. I have just updated to KDE 4.3.4 and since the update the NetworkManager won't connect to my wifi (I haven't tried wired yet). I use following packages for NetworkManager and KNetworkManager applet
kdeplasma-applets-networkmanager 1047027-1
networkmanager 0.7.2-1
There seems to be nothing strange in the daemons.log, but the KNMgr tray icon keeps saying "Networking information not available" and when I click it I get "Network Management Disabled" instead of the usual menu. I still can configure network manually and wicd is also working fine.
I remember putting my notebook to suspend-to-disk by mistake instead of shutting it down right after the update, so that's when it might have gone crazy. I tried reinstalling NetworkManager and the KDE applet and googling around a bit, but nothing has helped so far...
Last edited by MadCat_X (2009-12-02 18:34:55)

NM is definitely running, "ps aux | grep Network" gives me
root 1573 0.0 0.0 61976 3876 ? Ss 01:35 0:00 /usr/sbin/NetworkManager
root 1589 0.0 0.0 68868 3176 ? S 01:35 0:00 /usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf
madcat 1849 0.0 0.0 8360 976 pts/2 S+ 01:36 0:00 grep Network
I tried uninstall -reinstall method, but the plasma applet still sticks to the "Networking information not available" message.
This is how the NM related info in daemon.log looks like
Dec 2 01:35:34 Qosmio-X300 NetworkManager: <info> starting...
Dec 2 01:35:34 Qosmio-X300 NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
Dec 2 01:35:34 Qosmio-X300 NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_8086_4232_rfkill_phy0_wlan
Dec 2 01:35:34 Qosmio-X300 NetworkManager: <info> Trying to start the supplicant...
Dec 2 01:35:34 Qosmio-X300 NetworkManager: <info> Trying to start the system settings daemon...
Dec 2 01:35:35 Qosmio-X300 nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.

[SOLVED] NetworkManager dumped core

Symptoms: WiFi randomly drops out.
More specifically: NetworkManager core dumps and network-manager-applet stops (Gnome 3.8)
If anyone has suggestions, I'd be grateful. I'm at a loss, other than disabling NetworkManager and enabling netctl. Details follow below.
Thanks so much!
uname -r
3.9.0-2-ARCH
uname -m
x86_64
lspci -v
Network controller: Intel Corporation Centrino Advanced-N 6205
rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
iwconfig
enp0s25 no wireless extensions.
wlp3s0 IEEE 802.11abgn ESSID:"The Way 5GHz"
Mode:Managed Frequency:5.18 GHz Access Point: 00:26:F2:F2:E7:D5
Bit Rate=65 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=54/70 Signal level=-56 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:230 Invalid misc:113 Missed beacon:0
lo no wireless extensions.
journalctl -u NetworkManager --since=today
-- Reboot --
May 04 14:04:19 arch systemd[1]: Starting Network Manager...
May 04 14:04:20 arch NetworkManager[284]: <info> NetworkManager (version 0.9.8.0) is starting...
May 04 14:04:20 arch NetworkManager[284]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
May 04 14:04:20 arch NetworkManager[284]: <info> WEXT support is enabled
May 04 14:04:21 arch NetworkManager[284]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager ma
May 04 14:04:21 arch NetworkManager[284]: keyfile: parsing Auto The Way 5GHz ...
May 04 14:04:21 arch NetworkManager[284]: keyfile: read connection 'Auto The Way 5GHz'
May 04 14:04:21 arch NetworkManager[284]: <info> monitoring kernel firmware directory '/lib/firmware'.
May 04 14:04:21 arch NetworkManager[284]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi hardware radio set enabled
May 04 14:04:21 arch systemd[1]: Started Network Manager.
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WWAN enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WiMAX enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> Networking is enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <warn> failed to allocate link cache: (-10) Operation not supported
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): carrier is OFF
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): new Ethernet device (driver: 'e1000e' ifindex: 3)
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): exported as /org/freedesktop/NetworkManager/Devices/0
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/enp0
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): using nl80211 for WiFi device control
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): driver supports Access Point (AP) mode
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> error poking ModemManager: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop
May 04 14:04:21 arch NetworkManager[284]: <info> wpa_supplicant started
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:21 arch NetworkManager[284]: <warn> Trying to remove a non-existant call id.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: starting -> ready
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
May 04 14:04:25 arch NetworkManager[284]: <info> Auto-activating connection 'Auto The Way 5GHz'.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) starting connection 'Auto The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless): connection 'Auto The Way 5GHz' has security, and secrets exist. No new
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'ssid' value 'The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'scan_ssid' value '1'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'auth_alg' value 'OPEN'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'psk' value '<omitted>'
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Config: set interface ap_scan to 1
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: inactive -> scanning
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: scanning -> authenticating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associating -> associated
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associated -> completed
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless netwo
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 04 14:04:28 arch NetworkManager[284]: <info> dhcpcd started with pid 447
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning IP6 addrconf.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
May 04 14:04:28 arch dhcpcd[447]: version 5.6.8 starting
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:28 arch dhcpcd[447]: [color=#FF0000]wlp3s0: sendmsg: Cannot assign requested address[/color]
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: rebinding lease of 192.168.10.59
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: acknowledged 192.168.10.59 from 192.168.10.1
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: checking for 192.168.10.59
May 04 14:04:32 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:33 arch dhcpcd[447]: wlp3s0: leased 192.168.10.59 for 86400 seconds
May 04 14:04:33 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed preinit -> bound
May 04 14:04:33 arch NetworkManager[284]: <info> address 192.168.10.59
May 04 14:04:33 arch NetworkManager[284]: <info> prefix 24 (255.255.255.0)
May 04 14:04:33 arch NetworkManager[284]: <info> gateway 192.168.10.1
May 04 14:04:33 arch NetworkManager[284]: <info> nameserver '192.168.10.1'
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Policy set 'Auto The Way 5GHz' (wlp3s0) as default for IPv4 routing and DNS.
May 04 14:04:34 arch NetworkManager[284]: <info> Writing DNS information to /usr/sbin/resolvconf
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): roamed from BSSID 90:27:E4:5E:98:24 (The Way 5GHz) to 00:26:F2:F2:E7:D5 (The Way 5GHz)
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) successful, device activated.
May 04 14:04:36 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: no IPv6 Routers available
May 04 21:04:49 arch NetworkManager[284]: <info> (wlp3s0): IP6 addrconf timed out or failed.
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 04 21:04:50 arch systemd[1]: NetworkManager.service: main process exited, code=dumped, status=6/ABRT
May 04 21:04:50 arch systemd[1]: MESSAGE=Unit NetworkManager.service entered failed state.
May 04 21:04:50 arch systemd-coredump[1036]: [color=#FF0000]Process 284 (NetworkManager) dumped core.[/color]
journalctl -u wpa_supplicant --since=today
-- Reboot --
May 04 14:04:21 arch systemd[1]: Starting WPA supplicant...
See dmesg at Pastebin
[edited May 7, 2013]
I'm marking this topic SOLVED, though more accurately, I should say that I've worked around the problem.
I achieved a stable wireless connection by changing APs, which leads me to believe that the underlying problem is upstream. Specifically, the problem is most likely that NetworkManager is not compatible with all APs. In my case, when I connect to a Netgear NDR3700v1 running dd-wrt, NetworkManager and nn-applet crashed randomly and frequently. However, after changing to an Apple Airport AP, I achieved a stable connection without crashes.
Bottomline: if you experience wireless connection troubles with NetworkManager and nm-applet, the problem may be that NetworkManager is not "compatible" with your AP hardware.
Last edited by hcra (2013-05-07 20:50:36)

b1tgl0w wrote:Is it normal for crond to run as the root user?
Completely normal. I'd be asking the question "was I hacked" if I found cron NOT running as root.
I'd say your computer just crashed.

[SOLVED] Ardour - could not reconnect to audio/MIDI engine

I have a problem with Ardour:
when I am tryng to create a session it is telling me that it "could not reconnect to audio/MIDI engine.
I don't really know where to go from here.. Can anyone please help me with this?
Let me know if there is any information I should post to help solving this?
Thanks in advance!
Last edited by AlexanderHolmgaard (2015-02-07 16:29:56)

Have you add your user to audio group?

[SOLVED] Headphone keep producing noises after update

I executed "pacman -Syu" yesterday. And after update my headphone isn't turned on automatically. I had install alsamixer and unmute it manually, but the problem is the headphone keeps producing annoying noises. It never happened before the update. I have win***s installed and got no problem with it.
Don't know what to do here. I've been using linux (mandriva, opensuse, fedora, slackware, and mostly ubuntu) for 5 years, but haven't been working with arch until a month ago, so you probably underestand my situation.
Thank for the cooperation..
Last edited by amuroray (2011-05-29 00:53:01)

yeah it was the kernel, nvidia driver, and others
core/grep core/mkinitcpio
core/cryptsetup
core/kbd
core/attr
core/gcc
core/xz
core/file
core/initscripts
core/acl
core/lzo2
core/util-linux
core/kernel26
core/linux-firmware
core/gmp
core/udev
core/gcc-libs
core/sqlite3
core/device-mapper
core/lvm2
core/binutils
core/glib2
extra/kdelibs
extra/p7zip
extra/akonadi
extra/kdeedu-marble
extra/udisks extra/poppler-qt
extra/gstreamer0.10-ugly-plugins
extra/gstreamer0.10-ugly extra/acpid
extra/boost-libs extra/gstreamer0.10
extra/kdebase-workspace
extra/poppler
extra/wvdial
extra/gstreamer0.10-base
extra/kdeplasma-applets-networkmanagement
extra/libftdi
extra/parted
extra/gstreamer0.10-base-plugins
extra/git
extra/liblqr
extra/upower
extra/libssh2
extra/nvidia-utils
extra/chromium
extra/partitionmanager
extra/curl
extra/gnutls
extra/nvidia
extra/neon
extra/libjpeg-turbo
community/packagekit-qt community/opera community/packagekit
and one more thing, when booting up i noticed that when udev was starting, there was a slight click sound coming from my headphones twice. I assume that was a sign that the headphone was turned on and turned off again when udev was starting, so maybe it was udev problem, i think.

[Solved] NetworkManager, DHCPC, LIBNL : NoIP error ?

Since few, I have problems getting IP adress with NetworkManager, so I switch to WiCD which works well.
I found this error with journalctl :
avril 10 09:37:01 x200 NetworkManager[537]: <error> [1397115421.4269] [nm-system.c:287] sync_addresses(): (enp0s25): error -7 returned from rtnl_addr_add():
Does anybody know how to solve this issue ? I need to switch back to NM because it allows me to manage a 3G/UMTS connection.
[EDIT]
it looks quite similar to this bug :
https://bugzilla.redhat.com/show_bug.cgi?id=1063885
Last edited by dR0o7 (2014-04-15 07:55:35)

Doing a fresh re-install of the package seems to have solved the problem
Using wicd as connection manager
sudo pacman -Rnsc networkmanager
reboot then
sudo pacman -Sy networkmanager network-manager-applet
with all the systemctl enable/disable needed
networkmanager also seems to use dhcpcd to get ip now instead of dhclient
dr0o7@x200 ~% sudo journalctl -n 2000 | grep dhc
avril 15 09:49:21 x200 NetworkManager[506]: <info> dhcpcd started with pid 2135
avril 15 09:49:21 x200 dhcpcd[2135]: version 6.3.2 starting
avril 15 09:49:21 x200 dhcpcd[2135]: DUID 00:01:00:01:1a:cf:ca:8c:00:1f:16:1a:f3:70
avril 15 09:49:21 x200 dhcpcd[2135]: enp0s25: IAID 16:1a:f3:70
avril 15 09:49:21 x200 dhcpcd[2135]: enp0s25: soliciting an IPv6 router
avril 15 09:49:21 x200 dhcpcd[2135]: enp0s25: rebinding lease of 10.219.5.11
avril 15 09:49:26 x200 dhcpcd[2135]: enp0s25: leased 10.219.5.11 for 691200 seconds
avril 15 09:49:26 x200 dhcpcd[2135]: enp0s25: adding route to 10.219.5.0/24
avril 15 09:49:27 x200 dhcpcd[2135]: enp0s25: removing route to 10.219.5.0/24
avril 15 09:49:33 x200 dhcpcd[2135]: enp0s25: no IPv6 Routers available

[solved] networkmanager-vpnc

Hello everyone,
I added a vpnc using networkmanager-vpnc but when i try to activate it i get the following message:
Jun 27 19:35:55 himmel NetworkManager[333]: <warn> connection /org/freedesktop/NetworkManager/Settings/2 failed to activate: (2) The VPN service 'org.freedesktop.NetworkManager.vpnc' was not installed.
i checked the boards but couldn't find anything to help me solve this issue, has anyone encountered this before?
Thanks in advanced for your time and assistance.
Zerosoul.
Last edited by zerosoul13 (2012-06-29 03:52:41)

this is odd, seems that those packages were already installed on the machine
[angel@himmel ~]$ sudo pacman -S networkmanager-vpnc vpnc
warning: networkmanager-vpnc-0.9.4.0-1 is up to date -- reinstalling
warning: vpnc-0.5.3.svn516-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (2): networkmanager-vpnc-0.9.4.0-1 vpnc-0.5.3.svn516-2
Total Installed Size: 0.80 MiB
Net Upgrade Size: 0.00 MiB
Proceed with installation? [Y/n] Y
(2/2) checking package integrity [--------------------------------------------------------] 100%
(2/2) loading package files [--------------------------------------------------------] 100%
(2/2) checking for file conflicts [--------------------------------------------------------] 100%
(2/2) checking available disk space [--------------------------------------------------------] 100%
(1/2) upgrading vpnc [--------------------------------------------------------] 100%
(2/2) upgrading networkmanager-vpnc [--------------------------------------------------------] 100%
[angel@himmel ~]$ sudo /etc/rc.d/networkmanager restart
:: Stopping NetworkManager [DONE]
:: Starting NetworkManager
After this, i was able to connect to VPN, ill do a reboot and see if it works without having to restart the networkmanager daemon.
# Issue solved.
Last edited by zerosoul13 (2012-06-29 03:52:02)

[SOLVED] NetworkManager and UMTS/3G

I have a problem with NetworkManager and its Applet (the GNOME one)
In Ubuntu 10.04 it works fine with NM and in Archlinux it works flawless with wvdial but not with NetworkManager
It just tells me that i dont have any UMTS/3G devices (which is just nonsense)
Is that a bug in NetworkManager or am i doing something wrong?
//Edit: Oh damm i just forget the optional dependency "modemmanager"... solved
Last edited by Vamp898 (2010-06-14 00:43:24)

Your edit got me one step further, now I see that device also in networkmanager here finally. Thank you!
If someone tries to click onto "configure" for "mobile broadband" and its greyed out: Click "configure" for wired, leave that window open and just click "configure" in the main networkmanager window again. Then the network connections box from gnome 2 comes up and allows to configure 3G entries. (not a gnome bug, but a feature;)

[SOLVED] Networkmanager - Network Managment Disabled

I had a bad resume from suspend and had to restart computer, After that my networkmanager cant connect and KDE icon says viz subject. Trying to find some solution here I used google to find this : http://osdir.com/ml/debian-bugs-dist/20 … 07864.html
Stopping networkmanager daemon, rm /var/lib/NetworkManager/NetworkManager.state and starting again solved this problem.
However, this behavior looks very bad for me. If every daemon works like this, after bad resume u can throw the computer from window... And BTW I think this should be at wiki in Troubleshooting 'cause this can happen to everyone
Last edited by LukynZ (2010-02-22 20:29:35)

I fix it myself by adding rm line to /etc/rc.d/networkmanager where start script is, now its fixed automatically
PID=`pidof -o %PPID $NETWORKMANAGER_BIN`
case "$1" in
start)
rm /var/lib/NetworkManager/NetworkManager.state
stat_busy "Starting NetworkManager"
if [ -z "$PID" ]; then
$NETWORKMANAGER_BIN
fi
if [ ! -z "$PID" -o $? -gt 0 ]; then
stat_fail
else
add_daemon networkmanager
stat_done
fi
stop)
I am not sure how much is this solution clear, but it works and thats all I need

[SOLVED] NetworkManager and DNS

Hello,
Is there any way to set and make permanent DNS adress with NetworkManager? I'd like to use OpenDNS so I edited /etc/resolv.conf and it works till next system restart. What am I supposed to do to make DNS adress permanent?:/
EDIT: Something gone wrong.
EDIT: Solved, it's new NetworkManager 0.7.
Last edited by MilosC (2009-03-08 02:10:32)

My all time favorite way to do this is to put your isp (or OpenDNS addresses, etc) into your router via it's own configuration page. I've never had to mess around with resolv.conf, dhclient etc this way for over 5 years and let the box pick it up from your router.
After making the change in the router, restart networking, or reboot.

[Solved] NetworkManager deauthenticating?

NetworkManager is not connecting, however I connect fine with
sudo ip link set wlp6s7 up && sudo wifi-menu
dmesg after trying to connect a few times:
156.025351] wlp6s7: authenticate with 00:0f:b3:48:5a:57
[ 156.030144] wlp6s7: send auth to 00:0f:b3:48:5a:57 (try 1/3)
[ 156.031577] wlp6s7: authenticated
[ 156.031786] rt2800pci 0000:06:07.0 wlp6s7: disabling HT/VHT due to WEP/TKIP use
[ 156.031794] rt2800pci 0000:06:07.0 wlp6s7: disabling HT as WMM/QoS is not supported by the AP
[ 156.031802] rt2800pci 0000:06:07.0 wlp6s7: disabling VHT as WMM/QoS is not supported by the AP
[ 156.034511] wlp6s7: associate with 00:0f:b3:48:5a:57 (try 1/3)
[ 156.036589] wlp6s7: RX AssocResp from 00:0f:b3:48:5a:57 (capab=0x471 status=0 aid=2)
[ 156.036943] wlp6s7: associated
[ 156.040422] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s7: link becomes ready
[ 156.079170] wlp6s7: deauthenticating from 00:0f:b3:48:5a:57 by local choice (reason=3)
[ 156.095143] cfg80211: Calling CRDA to update world regulatory domain
[ 159.411994] wlp6s7: authenticate with 00:0f:b3:48:5a:57
[ 159.416800] wlp6s7: send auth to 00:0f:b3:48:5a:57 (try 1/3)
[ 159.418114] wlp6s7: authenticated
[ 159.418314] rt2800pci 0000:06:07.0 wlp6s7: disabling HT/VHT due to WEP/TKIP use
[ 159.418321] rt2800pci 0000:06:07.0 wlp6s7: disabling HT as WMM/QoS is not supported by the AP
[ 159.418325] rt2800pci 0000:06:07.0 wlp6s7: disabling VHT as WMM/QoS is not supported by the AP
[ 159.420990] wlp6s7: associate with 00:0f:b3:48:5a:57 (try 1/3)
[ 159.422759] wlp6s7: RX AssocResp from 00:0f:b3:48:5a:57 (capab=0x471 status=0 aid=2)
[ 159.423087] wlp6s7: associated
[ 159.467443] wlp6s7: deauthenticating from 00:0f:b3:48:5a:57 by local choice (reason=3)
Anyone know what might be causing this? (or how to fix it?)
Last edited by gandalf3 (2013-06-02 21:28:40)

Nothing I have found so far has worked.
I don't have wicd or netcfg installed, and I don't think it's a drivers issue as I can connect with wifi-menu..
I'll keep searching..
Last edited by gandalf3 (2013-05-21 19:06:48)

[SOLVED] NetworkManager will not connect to Mobile Broadband (o2)

I cannot get Networkmanager to connect to mobile broadband (o2).
Everything works fine if I open a terminal, do "sudo wvdial o2", minimize it, and then open Firefox.
Networkmanager (nm-applet) shows the connection to o2, but if I select it, it just instantly responds with "Network Disconnected". I have checked the settings for the mobile broadband connection, and they are the same as in wvdial.
I have also tried logging in as root, and tried from there, but I still get the same resuilt.
I would be very grateful for any help with this problem.
Last edited by myrlin (2011-03-17 20:00:29)

As if by magic, the latest updates have solved the problem. I've no idea how, but everything is now working perfectly.
Thanks to everyone who has taken the time to think about this problem for me.

[SOLVED] NetworkManager does not connect to WiFi networks

I'm using `networkmanager` to connect WiFi.
I have selected WiFi Name through `networkmanager`.
Next, enter WiFi Password.
But the problem is, `networkmanager` asks me about password again and again and over again and does not connect to WiFi never !!!!
I'm sure WiFi password that I entered is correct.
Last edited by kamrava (2014-02-22 05:46:37)

orschiro wrote:Maybe not satisfying, but can you instead use Wicd?
My problem was solved. `wicd` was not installed on my system.
My Problem solved through :
I have Installed `wicd` and then NetworkManager works like a charm now
$ sudo pacman -S wicd wicd-gtk
Thank you all.
Last edited by kamrava (2014-02-21 11:29:17)

[SOLVED] NetworkManager keeps on reconnecting

Similar Messages

Maybe you are looking for