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

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] 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]GNOME "oh no!" message after installing network manager

I have recently installed arch on my laptop and sucessfully installed gnome but as soon as I installed networkmanager or wicd when I reboot and "startx" I get oh no! something has gone wrong. It was all working fine until I installed network manager, after removing network manager and gnome worked again I decided to install wicd, but now I have uninstalled the lot it still doesnt work.
Last edited by JKAD (2014-09-03 23:51:05)

https://bbs.archlinux.org/viewtopic.php?id=143753
https://bbs.archlinux.org/viewtopic.php?pid=1270468
https://bbs.archlinux.org/viewtopic.php?id=161310
https://bbs.archlinux.org/viewtopic.php?id=184369
https://bbs.archlinux.org/viewtopic.php?id=152810
https://bbs.archlinux.org/viewtopic.php?id=167732
https://bbs.archlinux.org/viewtopic.php?id=185346
https://bbs.archlinux.org/viewtopic.php?id=152408
You get the idea...

Gnome-network-manager shouldn't require Gnome?

According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
Maybe it would be a good idea to include a version that isn't compiled for Gnome in Extra, so that people using E17 or XFCE or whatever can easily use networkmanager? If people think this is practical I'll file a feature request...

Gullible Jones wrote:According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
It does need gnome deps. Requires libgnomegui and gnome-keyring... in turn it also uses gconf and other things. These can't be disabled.
James

Network Manager (GNOME 3.8.x) disconnecting

Hi,
I have a problem with the Network Manager for Gnome 3.8.2 on my laptop - I've tried to have it connect to my network broadband but the problem is it keeps disconnecting - even the ethernet cable on the laptop. Is the Network Manager for gnome at it's latest version if not could it be updated! Is anyone else having the same problem?

I'm also traped in this trouble. Did you resolve this problem?
I've noticed that this annoying error started after I've installed the network manager and network manager applet in gnome.
And I cannot remove network manage and the applet cause gnome now depends on it. What a stupid error.
Thanks in advance.
Last edited by victordfb (2013-10-29 12:20:21)

[Solved] netcfg Network Unavailable.

Hi,
When trying to connect to a wireless network with netcfg it always fails with 'Network Unavailable'. Everything used to work with network-manager under Gnome. Lsmod says the iwl3945 module is loaded and iwconfig says;
wlan0 IEEE 802.11g ESSID:"@Home94004"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
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
iwlist doesn't give any scan results but the XP laptop 10cm away can find the network. Network-manager also used to find the network.
this is my profile;
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="@Home94004"
KEY="*********"
IP="dhcp"
TIMEOUT=30
I'd appreciate some pointers on what to check next.
Thanks.
Last edited by captainm (2008-08-18 18:53:18)

Is this a new problem? If so, look through these threads:
http://bbs.archlinux.org/viewtopic.php?id=53654
http://bbs.archlinux.org/viewtopic.php?id=53565

Network Manager & Keyring password

This question has probably been asked "ad nauseam" but I'm trying to get Network Manager (in GNOME) to stop asking me for my keyring password. I searched in the forums and I found out there used to be a pam_keyring package that took care of this but it's not available anymore. Strangely this can be done with other distros so surely, it is also doable in Arch, right? TIA.

Allan wrote:Is this possible without logging in using gdm? I use networkmanager in XFCE with slim login manager and can't manage to get this to work.
I was able to disable the annoying 'feature' whereby the Gnome Keyring keeps asking for a password at login by editing /etc/pam.d/login in addition to the other edits suggested to /etc/pam.d/gdm (http://wiki.archlinux.org/index.php/Net … Kit_issues). I also deleted ~/.gnome2/keyrings. This is especially useful since I don't use gdm to login, rather loggin straight from the shell. YMMV if you use kde or another DE.

Network-manager not working

I tried to install network-manager and gnome-network-manager and it was sucessfully installed since the dependency problem was fixed but after adding the dhcdpd and networkmanager daemon's to my rc.conf and removing all network interfaces, (except for lo) it cannot find some resouces it says it "cannot continue." Here is the error when I run "nm-applet" from a console:
** (nm-applet:2456): WARNING **: Icon nm-no-connection missing: Icon 'nm-no-connection' not present in theme
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2456): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

I'd say it has to do with the gnome applet and not the networkmanager daemon itself. I think there's some secret code somewhere hidden in Arch that prevents handy graphical apps from running, because I'm having problems with knetworkmanager too. Eventually, everything GUI will be so buggy that we'll all be forced to Openbox. BWHAHAA!
Errr, I'll let you know if I find a decent frontend that works with Arch.

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

Gnome shell network manager issues

I'm running nm-applet on Gnome Shell. A recent update solved my problems of clicks not registering in nm-applet.
However, there are still some issues which means I'm still using 'nmcli' to connect to networks:
1/ The list of connections is not scrollable. At home, even though my wireless network has the strongest signal, it's not listed near the top. In fact, it's listed below the bottom of the screen (there are a lot of wireless networks) and there's no way to get to it!
2/ It doesn't accurately show available networks. This maybe a "Suspend" issue, but the list of networks that nm-applet shows is not up to date. It shows my home network when I'm at work and random networks which are currently not in range too.
Is there some open bug report about this or is this something I've done?
Also, 'nmcli con list' seems to list saved networks and not available networks. Is that the intended behavior?
EDIT: The man page for nmcli does say this is the intended behavior and 'nmcli dev wifi list' is what I was looking for...
Last edited by pritamps (2011-03-30 20:34:48)

BUMP..
The above behavior hasn't changed even after a few updates. Is anybody else experiencing these issues?
Will it help if I delete all the network manager config files? I'm thinking it might be some conflict of config files between nmcli and nm-applet...

[SOLVED] No network manager in Gnome 3.8

Similar Messages

Maybe you are looking for