[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

Similar Messages

  • [SOLVED]No Network Manager Icon in system tray

    Hi, the network manager doesnt appear on my notification area, I can see the process is running (Im typing this from arch) and everything works fine, but I dont have the icon to create new connections or see Ip address, gateways and stuff.
    The applet appears loaded at startup like so:
    Any help?
    Last edited by 655321 (2010-06-14 22:07:20)

    will do and come back with results
    Back, Ok that was very helpfull, as soon as I see the last post I realized that indeed I DONT have network manager listed on my daemons, and thats why there is no icon, and the fact that I still have Internet and stuff its because im using the old configuration (the one from the beginners guide).
    Im pretty sure thats the reason so I will go ahead and test it and come back with hopefully good results.
    DONE
    Problem was exactly that, you have to disable "network" daemon from rc.conf and put "networkmanager" there.
    cheers and thanks for the help.
    Last edited by 655321 (2010-06-14 22:02:57)

  • [SOLVED] Gnome3 - Network Manager Missing?

    I recently upgraded to Gnome3, and I'm still adjusting to it, but something doesn't seem quite right. I was expecting the network manager to show up in the notification area, but it does not appear to be there. I've also looked in the application area to look for it, and, for some reason, there are two network entries ("Network" and "Network Connections"). How can I bring up the network manager? Any assistance would be appreciated.
    Last edited by Nikorasu (2011-05-06 16:49:24)

    Nevermind: The issue seems to have resolved itself, perhaps as part of an update or system restart.

  • [SOLVED] No network manager in Gnome 3.8

    I've been looking for this for a few days but the search terms that I'm working with a probably too generic.
    I come from 3.4 on Debian and was always able to connect to wireless networks from a menu in the top right. I could also set proxy settings there and other things.
    Now I'm connecting to my wifi with wifi-menu and changing the proxy when needed by using the export command, which is working nicely, but I'm looking for more comfort now.
    Where it should be: http://snag.gy/1W9vD.jpg
    What I'm looking for: http://doc.opensuse.org/documentation/h … etwork.png
    I was looking in the direction of nm-applet and NetworkManager, but after installing these I still don't see it coming up in Gnome. Anybody who can point me in the right direction?
    edit: I do get these
    ** (nm-applet:3032): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
    ** (nm-applet:3032): WARNING **: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.ModemManager1.service' for details.
    ** Message: applet now removed from the notification area
    ** Message: applet now embedded in the notification area
    ** (nm-applet:3032): WARNING **: fetch_connections_done: error fetching connections: (32) Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details..
    ** (nm-applet:3032): WARNING **: Failed to register as an agent: (32) Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
    Last edited by InFerYes (2013-09-25 23:18:19)

    Ok, pretty typical, after looking for a while and asking for help you usually find the solution yourself, as did I.
    Make sure NetworkManager is started:
    systemctl status NetworkManager
    If not, start it
    systemctl start NetworkManager
    But also bring down the currently link that you've made "manually":
    ip link set wlp11s0 down
    The applet is visible and I'm connecting to networks.
    Thanks for reading, issue resolved.

  • [SOLVED][GNOME 3] After install - no Network Manager?

    Installed Arch for the first time yesterday, so I put GNOME 2 on it first to make sure everything worked before moving onto the unstable stuff. Installed GNOME 3, installed Gnome Shell, bootup, everything seems perfect, except that I have no Network Manager. No applet in the top-right corner. Clicking on the Network application under activities did nothing and neither did trying to access it from System Settings. I did a little Googling, figured that I needed to actually install networkmanager and network-manager-applet. So I did so from pacman:
    pacman -S networkmanager network-manager-applet
    and now I can get into the application but I'm getting an error, "The system network services are not compatible with this version," which gives me a minimal-use window with a network proxy entry and the ability to add a VPN entry.
    I know my WiFi works (Intel Wireless-N 1000) because it shows up as wlan0 in iwconfig and I can connect to an unsecured network with wicd. Anyone know how I can get Gnome's Network Manager back?
    Last edited by solatic (2011-04-10 20:49:41)

    solatic wrote:
    ah, the stupid daemon. Of course. /knockheadonwood. Might be good to link that kind of stuff to the GNOME 3 wiki entry.
    Thanks for your time!
    Um, did Wonder help you solve the problem ?  If so, please add [SOLVED] to the thread title by editing the original post.
    As to the wiki links, feel free

  • [SOLVED] Network Manager confusion on reading WiKi

    I have installed KDE DE...I am unable to start the network through NM...
    On going thru Arch Wiki , https://wiki.archlinux.org/index.php/NetworkManager
    I understand that there are 2 NMs available..One is for GNOME but works in all DE (backend), Other is "Knetworkmanager" which is for KDE.(backend)...
    The frontend GUI is Gnome- applet and KDEplasme-applet
    It is stated under KDE 3.5 , that Knetworkmanager is not supported but available in AUR...
    My doubt is as follows
    1. What should I install for KDE backend? --- Gnome Networkmanager or Knetworkmanager (Is the version for 4.4 & above supported?, wiki is silent on this)?
    2. For Frontend should I install the Plasma widget or the GNOME applet?
    3. If backend is GNOME network manager will it work with KDE plasma widget (front end) ?
    4. In /etc/rc.conf , in "DAEMONS = " should I give "knetworkmanager" or "networkmanager" If I install the KDE version?
    I had installed WIcd to test my settings...It was working initially after typing
    modprobe b43 <for bcm chipset>
    /etc/rc.d/network start
    /etc/rc.d/dbus restart
    /etc/rc.d/wicd start
    ifconfig wlan0 up
    dhcpcd wlan0
    wicd-curses
    Then I typed the network pwd and booted my interface.
    i wanted to go in for network manager as it would save me the typing time..(Currently I installed pacman -S networkmanager (GNOME version) and KDE plasma "the one with the icon similar to "m")But on selecting the interface it goes thru Activating Interface and then says "Network Connection failed"
    Now I am also not able to get wicd up
    Any pointers?
    EDIT ---The title says Graphical Front end managers, So I guess there is only one backend....In that case , why is my Network not working??All the wireless are detected ,so there is no problem with firmware....I have also enabled dhcpc (automatic)...So it shld fetch an IP address....dunno what the problem is..
    Last edited by vikrang (2011-04-29 10:11:02)

    vikrang wrote:1. What should I install for KDE backend? --- Gnome Networkmanager or Knetworkmanager (Is the version for 4.4 & above supported?, wiki is silent on this)?
    2. For Frontend should I install the Plasma widget or the GNOME applet?
    3. If backend is GNOME network manager will it work with KDE plasma widget (front end) ?
    4. In /etc/rc.conf , in "DAEMONS = " should I give "knetworkmanager" or "networkmanager" If I install the KDE version?
    1. there is just one, networkmanager. network-manager-applet and kdeplasma-applets-networkmanagement are just front-ends to networkmanager.
    2. https://wiki.archlinux.org/index.php/Ne … nager#KDE4 , but https://wiki.archlinux.org/index.php/Ne … ager#GNOME will work too. I use network-manager-applet on KDE 'cause the KDE front-end can't set a system connection.
    3. I won't even bother to answer to this.
    4. networkmanager!!!
    vikrang wrote:I have also enabled dhcpc (automatic)...So it shld fetch an IP address....dunno what the problem is..
    if you are using networkmanager you must the networkmanager daemon, not network. replace network with networkmanager in rc.conf in DAEMONS array.
    Last edited by JokerBoy (2011-04-27 08:59:42)

  • [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 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.

  • Nmcli (Network manager) not working after upgrade

    It seems there is a bug in the command line tool "nmcli" after a recent upgrade ..
    The GUI applet still works, but I can no longer start/stop connections with nmcli ..
    The error when using nmcli con ... is:
    Stopping Mobile Broadband Connection.
    Error: Can't obtain connections: settings service is not running.
    I had a script using nmcli to start stop my 3G connection .. it no longer works.
    If I downgrade networkmanager network-manager-applet and any dependancies, I don't get the error above, but I still can't stop/start the interface
    Anyone have a solution?
    EDIT: Looks like I have struck the bug reported here: https://bbs.archlinux.org/viewtopic.php?id=141379
    Last edited by bmentink (2012-06-11 04:47:40)

    Did you resolve this? I've just been hit with the same after upgrading to Server 3.2.2.

  • [SOLVED] Network Manager not working after disabling GDM daemon

    Morning All,
      1st post so go easy on me.
    I have recently setup Arch on a Samsung Q320 notebook, using GNOME DE and enabling gdm. Everything is working fine installed network manager no probs it connects to wireless network each time I login, really impressed with the distro. However I have been playing around with it a bit and when a disable the 'gdm' daemon by prefixing it with '!' in /etc/rc.conf, then reboot then login in with username & pw,  and 'startx'  GNOME DE starts fine however network manager fails to start, it is still located in the preferences menu I can open it and see the networks I have created previously however cannot join any of them. Can shed any light on the situation.
    Cheers
    Chris
    Last edited by phatrat (2010-03-12 21:24:49)

    just add in ~/.xinitrc
    exec ck-launch-session gnome-session

  • No interfaces shown in network manager [SOLVED]

    Hi All,
    I have just done a fresh install of Arch on my new Sony Vaio VGN-FW53GF, all goes well, except for Network Manager.
    I can use my wired connection ok as eth0 shows up as active when I hover over the kde applet in the task bar. However when I go to "Manage Connections"
    I do not see any Wireless networks or even my "working" wired connection in any list.
    Wireless seems to be working as iwconfig shows an interface.
    wlan0 IEEE 802.11abgn ESSID:""
    Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
    Tx-Power=0 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Encryption key:off
    Power Management:off
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    But a scan gives this:
    iwlist wlan0 scan
    wlan0 Interface doesn't support scanning : Network is down
    This machine is using the Intel driver "iwlagn" supplied by the kernel (2.6.31).
    My /etc/rc.conf is:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="UTC"
    USEDIRECTISA="no"
    TIMEZONE="Pacific/Auckland"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=()
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="Laptop2"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    eth0="dhcp"
    wlan0="dhcp"
    INTERFACES=(!eth0 !wlan0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng !network hal networkmanager netfs crond)
    Can anyone offer some suggestion on how to get network manager going, I would like to use it. In the past
    I have used Wicd, but it has some limitations.
    Cheers,
    Bernie
    Last edited by bmentink (2009-12-24 04:19:49)

    bmentink wrote:
    Ok, I found the issue. I was missing the firmware for the card. I downloaded firmware from the intel site as per the wiki on wireless and
    my interface comes up (shown with ifconfig) and I can see all the networks.
    However, I cannot seem to connect to my network with WPA. When I go to connect I get network manager thinking the access point is WEP and asking for pass phrase.
    If I select WPA(personal) and fill in a password, nothing happens .... just says unavailable.
    Can anyone give some idea's here. I have not used network manager before for WPA.
    Cheers,
    Bernie
    I use WPA2 with network manager without a problem.  It should "just work", im not sure why you have issues, can you switch your router to a different security protocol to test?

  • Xfce4 and gnome-network-manager [solved]

    I just made a clean install of archlinux. installed xorg and Xfce4, xfce-goodies, gnome-panel, gnome-desktop and gnome-network-manager. also I enabled GNOME services in startup and sessions. how do I start that network manager now? is nowhere in the settings, nor there is icon to add to the taskbar (i got xfapplets installed too)
    Last edited by anarxi (2009-01-14 00:22:42)

    quoted from a previous thread
    I solved it by uncommenting my <locale><charset> in /etc/locale.gen.
    First you have to enable the locales you want being supported by your system. To enable or disable them, the file /etc/locale.gen is used. It contains every locale you can enable, and you have just to uncomment lines you want to do so.
    As we want to setup an english UTF-8 conform system, we want to enable en_US.UTF-8. But for compatibility to programs that don't support UTF-8 yet, it's recommended to support any other locale, prefixed with en_US as well. Having this in mind, we enable this set of locales:
    en_US.UTF8 UTF-8
    en_US ISO-8859-1
    After you've enabled the necessary locales, you have to run locale-gen as root to update them:
    # sudo locale-gen
    Generating locales...
    en_US.UTF-8... done
    en_US.ISO-8859-1... done
    Generation complete.

  • [SOLVED]Network Manager dispatcher unexpected unmounting davfs folders

    I have used Network Manager dispatcher to configure automatic mount of cloud storage using  webdav. i have used davfs2 to perform mounting and wrote a script for NM dispatcher.
    If i run /etc/NetworkManager/dispatcher.d/10-YandexDisk.sh manualy all works perfect.
    If this script will be executed by NM-dispatcher all will fine(YandexDisk mounts successfully, sycronization - successfully), but after ~10 seconds mount.davfs gets signal 15.
    sudo systemctl status NetworkManager-dispatcher
    NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
    Active: inactive (dead) since Wed 2013-07-31 23:12:55 EEST; 11s ago
    Process: 12132 ExecStart=/usr/lib/networkmanager/nm-dispatcher.action (code=exited, status=0/SUCCESS)
    Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: --- yandex.ru ping statistics ---
    Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
    Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: rtt min/avg/max/mdev = 36.570/37.776/38.983/1.222 ms
    Jul 31 23:12:44 DellLaptop mount.davfs[12138]: davfs2 1.4.7
    Jul 31 23:12:44 DellLaptop mount.davfs[12138]: mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=users,_netdev,rw,uid=lexa https://webdav.yandex.ru/ /home/lexa/.../YandexDisk
    Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >mounted https://webdav.yandex.ru/ to /home/lexa/Data/YandexDisk
    Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >exiting!!
    Jul 31 23:12:55 DellLaptop mount.davfs[12140]: pid 12140, got signal 15
    Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting /home/lexa/Data/YandexDisk
    Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting failed
    Why does this happen? Who send this signal ?
    /etc/NetworkManager/dispatcher.d/10-YandexDisk.sh
    #!/bin/bash
    #this script will mount WebDav folder
    # by pirat9600q
    #given arguments are
    #$1 is interface name
    #$2 is state "up" or "down"
    eth="enp7s0" #ethernet interface
    wlan="wlp8s0" #wireless interface
    ignore_connections="Pirat9600q" #WiFi SSIDs that must be ignored
    mount_dir="/home/lexa/Data/YandexDisk" #mount point directory
    remote_server="https://webdav.yandex.ru/" #server address
    #local acces options
    local_user="lexa" #files owner user
    local_group="users" #files owner group
    echo "<<<started with '$1' and '$2' arguments>>>"
    echo "> our mount dir is '$mount_dir'"
    echo "> and remote server is '$remote_server'"
    case "$2" in
    up)
    #first of all we need to check internet connection
    if (ping -c 2 -q yandex.ru); then
    #we are online
    if [ "$1" = "$wlan" ]; then
    #Does this network is ignored ?
    SSID=$(iwgetid -r)
    for x in $ignore_connections; do
    if [ "$x" = "$SSID" ]; then
    echo "> WiFi SSID '$SSID' is in ignore list, exiting"
    exit
    fi
    done
    fi
    if [ ! -d "$mount_dir" ]; then
    fusermount -u "$mount_dir"
    fi
    if(mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=$local_group,_netdev,rw,uid=$local_user "$remote_server" "$mount_dir"); then
    echo ">mounted $remote_server to $mount_dir"
    echo ">invoking syncronization script"
    /home/lexa/.scripts/SyncYandexDisk.sh
    else
    echo ">error mounting $remote_server to $mount_dir !!!"
    fi
    else
    echo ">network down";
    exit
    fi;;
    down)
    echo ">unmounting '$mount_dir'"
    fusermount -u "$mount_dir"
    echo ">removing $mount_dir"
    rmdir $mount_dir
    echo ">finished";;
    esac
    echo ">exiting!!"
    exit
    /home/lexa/.scripts/SyncYandexDisk.sh
    #!/bin/bash
    #this script will synchronize local storage
    #with mounted Yandex Disk folder
    # by pirat9600q
    source_dir="/home/lexa/Data/YandexDisk/" #mount point directory
    dest_dir="/home/lexa/Data/ARC/CloudSync/" #local storage location
    echo "<<<started with:"
    echo " source folder '$source_dir'"
    echo " and destination folder '$dest_dir'"
    if [ ! -L ${source_dir}Foto ]; then #if not link
    echo ">invoking syncronization from '$source_dir' to '$dest_dir'"
    echo ">syncronizing 'Foto' folder"
    if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Foto/ ${dest_dir}Foto/); then
    echo ">>error"
    else
    echo ">>success"
    fi
    echo ">syncronizing 'Documents' folder"
    if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Documents/ ${dest_dir}Documents/); then
    echo ">>error"
    else
    echo ">>success"
    fi
    else
    echo ">syncronization will not be made, because source is fake"
    fi
    echo ">exiting"
    exit 0
    P.S. sorry for my English
    Last edited by pirat9600q (2013-08-02 08:14:44)

    I solved the problem. Here is a little explanation.
    After NetworkManager establishes network connection, NetworkManager-dispatcher service is started( for ~10 seconds). This service execute /usr/lib/networkmanager/nm-dispatcher.action, which execute scripts in /etc/NetworkManager/dispatcher.d. After exiting nm-dispatcher.action mount.davfs process appears in NetworkManager-dispatcher`s CGroup. By default all processes in CGroup must be killed when service stops. To change this behavior I have added KillMode=process to [Service] section of NetworkManager-dispatcher.service file.
    sudo nano /usr/lib/systemd/system/NetworkManager-dispatcher.service
    Here is it`s code now.
    [Unit]
    Description=Network Manager Script Dispatcher Service
    [Service]
    Type=dbus
    BusName=org.freedesktop.nm_dispatcher
    ExecStart=/usr/lib/networkmanager/nm-dispatcher.action
    KillMode=process
    [Install]
    WantedBy=multi-user.target
    Alias=dbus-org.freedesktop.nm-dispatcher.service

  • [Solved] Can't get gnome network manager running

    Alright this one is a head scratcher.  I've folowed the wiki for network manager to a T except I can't get the network manager icon to show up (I have notification addon already running).  I don't have any network loss though.
    Here's my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="localtime"
    USEDIRECTISA="no"
    TIMEZONE="Canada/Pacific"
    KEYMAP="dvorak/dvorak"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(powernow-k8 cpufreq_ondemand cpufreq_powersave forcedeth snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="myhost"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    eth0="dhcp"
    INTERFACES=(lo !eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng !network netfs crond laptop-mode dhcdbd networkmanager @alsa @hal @fam @gdm)
    Last edited by dr/owned (2009-01-09 05:16:43)

    I assume you're running nm-applet --sm-disable once you get a window manager session up?
    Try starting networkmanager after hal. From the wiki:
    You must also "disable" the default network daemon, and add the hal, dhcdbd and networkmanager daemons in this order:
    DAEMONS=( ... !network hal dhcdbd networkmanager ... )

  • [SOLVED] Network Manager cannot connect to wifi after suspend

    Hi,
    There appears to be similar threads recently, but they relate to no wifi at all. I did some updates today, and now if I suspend or hibernate, network manager cannot reconnect to my wifi. It will (after a while) ask me to authenticate, but still fails. Nothing works except a reboot where it connects without issue.
    It was fine yesterday, has only started today. Here is my pacman log for today's updates:
    [2012-04-11 17:13] upgraded libpciaccess (0.13-1 -> 0.13.1-1)
    [2012-04-11 17:13] upgraded lib32-libpciaccess (0.13-1 -> 0.13.1-1)
    [2012-04-11 17:13] upgraded mpd (0.16.7-3 -> 0.16.8-2)
    [2012-04-11 17:13] upgraded xorg-server-common (1.12.0.901-1 -> 1.12.0.902-1)
    [2012-04-11 17:13] upgraded xorg-server (1.12.0.901-1 -> 1.12.0.902-1)
    [2012-04-11 17:13] upgraded xorg-server-devel (1.12.0.901-1 -> 1.12.0.902-1)
    [2012-04-11 17:13] upgraded xorg-server-xephyr (1.12.0.901-1 -> 1.12.0.902-1)
    Here is my messages log:
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Auto-activating connection 'Padfoot'.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) starting connection 'Padfoot'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0/wireless): connection 'Padfoot' has security, and secrets exist. No new secrets needed.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'ssid' value 'Padfoot'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'scan_ssid' value '1'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'psk' value '<omitted>'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: set interface ap_scan to 1
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: disconnected -> scanning
    Apr 11 18:38:29 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: scanning -> authenticating
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): association took too long.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): asking for new secrets
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> No agents were available for this request.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed for access point (Padfoot)
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> Marking connection 'Padfoot' invalid.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): deactivating device (reason 'none') [0]
    Last edited by Padfoot (2012-04-13 23:47:55)

    heiko wrote:linux-3.3.2 is released on www.kernel.org and reverts the patch that introduced this problem.
    For those using the arch repo kernel the next release will solve this issue. So I suggest waiting for this (no more than a few days) and use the LTS kernel in the meantime (or using a fixed ath9k module if already built).
    Thanks for that heiko. I thought that would be the case, hence I just waited.
    Will mark this as solved.
    Cheers.

Maybe you are looking for

  • Copying music b/w 2 iPods on 1 Computer

    I would like to copy music from my iPod to another iPod on a different computer using a different iTunes account. When I hook up my iPod on the other computer, I can see my music, however, I can't just click and drag the music to the other iPod when

  • Taxes for Movement type 201

    Hi, How can I configure  / develop abap code in userexits/badis to force the system to calculate taxes for movement type 201? When Creating the GI using MB1A for movement type 201, The accounting documents created donot have tax calculated( From vert

  • TabIndex not working in 2004 Pro

    Hi, I'm trying to get my tabIndex set up to tab through a series of buttons within a movie clip on my _root timeline. I have a movie clip called "menuoptions" on the _root then within that I have a number of buttons called "menu1" etc. I have tried t

  • Iphone4S email attachment and jpeg problem - Cant open

    Hello, I hope someone can help me as I'm a bit rubbish and the problem is driving me nuts!  I've tried searching the support forums but I can't find an answer. For some reason, I'm unable to open email attachments or RTF files and even Jpegs that are

  • HOW TO GET A CLI WITH DISCOVER

    taxi818 wrote: sylviagarcia wrote: Taxi818; Sorry you kind of lost me there...  What I am understanding is: "IF" I want to request a CLI I have to wait 90 days.. from the day I opened the account... right?  BUT, you are saying that they will auto CLI