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

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)

Gnome3 - Network Manager Settings - Authentication

Hi guys,
I've had a problem that started recently (not sure exactly when) with network manager.
When i try to change my network settings for a wireless connection to "available to all users" and click save,
the gnome (policykit?) authentication dialogue pops up requiring root password, but then almost instantaneously disappears again, so im unable to change/save the settings.
This could have possibly started after the upgrade to 3.2, but can't be sure about that.
I've tried deleting (moving temporarily to a backup location) the .config/dconf and .gconf/apps/nm-applet directories, but this doesn't appear to have any effect on nm-applet (wireless settings/passwords are still saved).
If i go into gnome-control-center and try editing something else which requires unlocking, then the dialogue box appears without issue, this only seems to happen for the nm-applet.
Are there any other files/directories which i should be looking at?
Cheers
Kane

Had a similar problem when trying to set up Network Manager. It turned out for me that I wasn't part of the Network group.
Try:
gpasswd -a <username> network
It has to be done as root or sudo if you're in the sudoer's list.

[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] 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] Gnome3 - installation issues (missing lib / missing bin)

Hi everyone,
i tried to install Gnome 3 from testing.
However i ran into some problems.
Problem 1:
While installing I get some "gtk-update-icon-cache: command not found" errors. They come from install scripts that are executed while upgrading.
I am 100% sure that the gtk-update-icon-cache binary is present in /usr/lib before executing pacman -Syu.
After pacman the binary is gone, reinstalling the package helps. So it seems some package breaks something here. (Don't know exactly which though, because there are plenty installed when upgrading)
Problem 2:
Just for the records: I'm using arch x86_64 and my repo order is
- testing
- multilib-testing
- community-testing
- core
- extra
- community
nothing else.
Upgrading itself works fine. Gnome 3 starts and fallback mode (gnome-panel) works from what I can see. (starting programs, including nautlilus, works well)
But when I try to start gnome-shell (with or without the --replace option) I get an "error while loading shared libraries: libgtk-x11-3.0.so.0: cannot open shared object file: No such file or directory".
Sometimes it is libgdk instead of gtk.
Additional information:
Using an Lenovo x200 with intel graphics. intel-dri is installed.
I used compiz in gnome2, could that arise some problems?
It does not work with a new user account also.
If you need any further information to help me, feel free to ask. I tried the search engine but couldn't find any results regarding gtk-update-icon-cache or libgtk-x11. (Searching the packages via google seems to show that no package contains these files?!)
Thank you very much
David
Last edited by deekay (2011-04-13 21:35:41)

thanks for your help, but unfortunately nothing changed!
[root@x200 deekay]# pacman -Sy gtk-update-icon-cache gtk3
:: Synchronising package databases...
testing is up to date
multilib-testing is up to date
community-testing is up to date
core is up to date
extra is up to date
community is up to date
multilib is up to date
warning: gtk-update-icon-cache-2.24.4-1 is up to date -- reinstalling
warning: gtk3-3.0.8-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (2): gtk-update-icon-cache-2.24.4-1 gtk3-3.0.8-1
Total Download Size: 0.00 MB
Total Installed Size: 31.75 MB
Proceed with installation? [Y/n]
(2/2) checking package integrity [######################] 100%
(2/2) checking for file conflicts [######################] 100%
(1/2) upgrading gtk-update-icon-cache [######################] 100%
(2/2) upgrading gtk3 [######################] 100%
[root@x200 deekay]# pacman -Qm
acct 6.5.5-1
android-sdk r10-2
anyremote-j2me-client-bin 4.18-1
archlinux-themes-gdm 1.4-1
autoconf-compat 2.13-2
bootchart 0.9-9
clutter-imcontext 0.1.4-1
ddcxinfo-arch 0.8-2
dropbox-experimental 1.1.7-1
gdm-old 2.20.11-1
gdm-themes 2.4-5
gedit-latex-plugin 0.2-3
gnomebaker 0.6.4-2
gtkam 0.1.17-1
hal-cups-utils 0.6.19-3
hibernate-script 2.0-6
hwd 5.5.2-1
keepass 2.14-2
lib32-dbus-glib 0.92-2
lib32-libidl2 0.8.14-2
lib32-libsasl 2.1.23-4
libcanberra-gtk3 0.26-1
libdownload 1.3-3
libexif-gtk 0.3.5-9
libpng12 1.2.44-1
mozplugger 1.14.3-1
nautilus-share 0.7.2-5
package-query 0.7-1
python-pyalsaaudio 0.6-2
songbird-bin 1.8.0-1
ssh2 2.0.13-6
teamviewer 6.0.9224-4
texmakerx 2.1-1
tpb 0.6.4-2
tpfan-admin 0.95-4
tpfand 0.94-7
tpfand-profiles 20090309-1
tp_smapi 0.40-4
ttf-ms-fonts 2.0-7
ttf-vista-fonts 1-3
ultrastardx 1.1-1
violet 0.21.1-2
virtualbox_bin 4.0.4-3
wlan-ng26-utils 0.2.9-1
wqy-microhei 0.2.0_beta-2
yaourt 0.10.1-2
yed 3.6.1.1-2
Last edited by deekay (2011-04-13 21:18:08)

Network Management Category?

Network Management missing from Product Category.
Trying to find bugs for Ciscoworks LMS.

Hi
We have identified the root cause for the issue of Product series or category missing from Bug Toolkit.
The issue was that in our upstream process was pulling/reading product information before second process completed its
writing operation which results into incomplete mapping and resulting into product & category getting lost.
The reason for the cause was change in the timing when two operations were scheduled to performed which resulted in the overlap.
We are working on fixing the issue so it will not re-occur in the future, but in the meantime we have found an interim solution
and as you see below, you can now search on "Network Management" product category again.
One change to observe is that now Product Category is renamed to "Network Management & Automation", will get back to you on the reason for the change, but you should be able to see "Ciscoworks LMS" under "Network Management & Automation".
Please let me know if this is product you were attempting to search for bugs and if it is working fine now.
Thanks
Arun

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 only works as root

Hello everyone,
I am brand new to arch and have been quite impressed over the past few days over all it has to offer. Everything has been running quite smoothly and I am now in the process of setting up wireless. I installed network manager and was able to connect to a wireless network as root. For my regular user, however, I am running into some issues. First one was that the nm-applet could not be opened in fluxbox. I received the following error:
** (nm-applet:1576): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
Error: (9) Connection ":1.27" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file
I "fixed" this by adding the following to /etc/dbus-1/system.d/nm-applet.conf. Original credit goes to the user in this thread (I only slightly modified his code): https://bbs.archlinux.org/viewtopic.php?id=63576

<policy user="myusername">
<allow own="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_destination="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_interface="org.freedesktop.NetworkManagerUserSettings"/>
<deny send_interface="org.freedesktop.NetworkManagerSetting.Secrets"/>
</policy>

Now the applet shows up for my regular user, the problem being that it doesn't connect to the wireless networks (only wired). Whenever I try to connect to wireless, nothing happens (the symbol doesn't change in any way, i.e. the green spheres should start circling); I am still able to succesfully connect to wireless using root. Does anyone know what the source of this issue may be? Thank you very much in advance.
Last edited by Ipozya (2011-01-20 04:49:55)

Solved: Had to install consolekit and add "ck-launch-session" to my .xinitrc file when starting fluxbox.
Edit: Please note that this also allowed me to remove the previous change to nm-applet.conf (no longer necessary)!
Last edited by Ipozya (2011-01-20 04:54:20)

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

[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]Modem-manager won't start with Network manager

Hi,
I have a problem with getting modem-manager work under gnome. After first Arch install to this laptop, Network manager didn't show my 3G-modem, so I installed modem-manager and usb_modeswitch. Modem is Huawei E367 and it works well with wvdial. Only problem is to get it working with Network manager.
From output of dmesg I see that there is an error, when Network manager is trying to start modem-manager:
[ 3224.705193] do_trap: 322 callbacks suppressed
[ 3224.705198] modem-manager[3112] trap int3 ip:7ff7baab4143 sp:7fff996e62b0 error:0
[ 3224.719275] modem-manager[3114] trap int3 ip:7f58f4c5e143 sp:7fffc82b2400 error:0
[ 3224.733880] modem-manager[3116] trap int3 ip:7f579dda4143 sp:7fff77910850 error:0
[ 3224.748789] modem-manager[3118] trap int3 ip:7ff752c6f143 sp:7fff8ae42e20 error:0
[ 3224.763501] modem-manager[3120] trap int3 ip:7fb4db83f143 sp:7fff3023cbf0 error:0
[ 3224.777865] modem-manager[3122] trap int3 ip:7fa17a33a143 sp:7fffc1628260 error:0
[ 3224.792165] modem-manager[3124] trap int3 ip:7f00a39fb143 sp:7fff075a0fb0 error:0
[ 3224.806603] modem-manager[3126] trap int3 ip:7f9a62e23143 sp:7fffc2ccfed0 error:0
[ 3224.820736] modem-manager[3128] trap int3 ip:7f3d2994d143 sp:7ffff2581340 error:0
[ 3224.834985] modem-manager[3130] trap int3 ip:7f5adda9a143 sp:7fff8a70a4a0 error:0
From /var/log/messages.log I found also something:
Apr 14 16:02:14 localhost NetworkManager[713]: <info> trying to start the modem manager...
Apr 14 16:02:14 localhost dbus[651]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Apr 14 16:02:14 localhost dbus[651]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Apr 14 16:02:14 localhost NetworkManager[713]: <info> modem-manager is now available
Apr 14 16:02:14 localhost modem-manager: libhal_ctx_init() failed: (null)
Apr 14 16:02:14 localhost NetworkManager[713]: <info> the modem manager disappeared
If I try to run modem-manager manually with debug:
$ sudo modem-manager --debug
** ERROR **: libhal_ctx_init() failed: (null)
Make sure the hal daemon is running?
So it seems to be because of hal isn't running, if I try to start hal daemon it fails:
$ sudo /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
I also tried to start hal at boot by putting it to DAEMONS in rc.conf. but didn't start either.
The laptop is Asus X61SL with x86_64 version of ArchLinux.
Kernel: 3.3.1-1-ARCH
Would be cool if anyone can solve this.
Last edited by Jompu (2012-04-14 20:42:20)

Thanks for your quick reply Strike0!
I ran lsusb and usb_modeswitch as you instructed:
[louis@Louis-Laptop ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
Bus 002 Device 002: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Bus 003 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 001 Device 006: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
[louis@Louis-Laptop ~]$ sudo usb_modeswitch -v 12d1 -p 1506 -M '55534243123456780000000000000011062000000100000000000000000000'
Password:
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 006 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x82 (in)
Not a storage device, skipping SCSI inquiry
USB description data (for identification)
Manufacturer: Huawei Technologies
Product: HUAWEI Mobile
Serial No.: not provided
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x82
Resetting message endpoint 0x01
-> Run lsusb to note any changes. Bye.
It didn't help. Network manager doesn't show anything related 3G.
I don't think it's usb_modeswitch since 3G stick works great with wvdial on same system. Could it be a bug on modem-manager?
I start only the Network manager on boot, but while Network manager tries to start modem-manager, it throws error continuously in dmesg. Error is the same as in first post.

[solved] Network manager error

I installed network manager as the wiki says, added myself to the network group and added the policy kit file. When I did this process on my main box, it worked perfectly, but on my laptop running largely the same things (except 32 bit not 64) I'm getting a little authentication box whenever my network interface comes up, asking for root's password. I put it in, and it instantly says it disconnected. If I run nm-applet from a terminal, I get this error after typing in root's password:
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
I'm using xfce if that makes any difference. Anyone got anything I can try?
Oh and the only reason I'm using NM is because I'm sick of wicd deciding HERP DERP IMA DISCONNECT RIGHT NOW and then not connecting again afterwards. Though since NM isn't working I have to use wpa_supplicant and dhcpcd directly myself.
EDIT: Ooops, this is the wrong section Could a mod please move it to Networking?
Last edited by biltong (2011-09-12 12:58:28)

Now I find gnome-keyring is not installed. That should be made a dependancy for network manager. I also (thanks to that thread) double checked I had the file the wiki said I needed to create, and it turns out I made a typo with my extension. It had .plka instead of .pkla XD Mah bad! So now I just need to get wpa_supplicant to connect one more time and I should be good to go

[SOLVED] Gnome3 - Network Manager Missing?

Similar Messages

Maybe you are looking for