Gnome Network Manager Isues

Hi Guys,
I have some weird issues with Gnome Network manager when I first boot up. I seem to have 2 profiles for my network connection enp3s0. I have a static IP for my PC, xxx.xxx.xxx.66, as I share music and photo's with a media centre PC in another room. But when I boot up or reboot the PC, it defaults to what appears to be another static IP address, xxx.xxx.xxx.109, that was used during the installation of Arch. I have disabled dhcpcd via
systemctl disable dhcpcd.service
but I can't seem to find where this weird IP is coming from.
If I open a command prompt at first login, and I issue ifconfig, my PC has the 109 IP address. If I expand on the Wired icon in Gnome's top right panel, I can see the two profiles, the incorrect one has a small dot next to it, to indicate its active. If I click on it, it disappears and my network becomes disconnected. When I reconnect, I get the correct profile with the correct IP address of 66, the 109 profile has gone.
If I go into the Weird Settings just after login, without clicking on any profiles, I have 2 settings in the box, the top one has a tick next to it and ther bottom one hasn't. If I click on the cog for the first profile, I can see it has a static of 109. Under identity, I remove the ticks for connect automatically and make available to ther users and apply. I reboot and the 109 profile is still there.
Cheers

yes, I have done it, and nothing happen
edit : I have reinstall the software, and now it is OK, tks for the help
Last edited by serafimsaudade (2007-05-20 17:34:56)

Similar Messages

Gnome-network-manager

Hi Everybody
I just tried to play a little with gnome-network-manager from AUR, first of all the normal network manager was missing a few files, but I managed to find them(http://aur.archlinux.org/packages/networkmanager/networkmanager/).
But when i start up gnome, it is shown fine in the Status Area, and shows all the networks, but it won't connect to any...
When connecting to an unencrypted network it says it is waiting for the network, when connecting to an encrypted network, it is waiting for the key to be verified.
My assumption is, that it is waiting for DHCP, in both cases.
If I use wifi-radar it gets an IP perfectly, also if I use dhclient or dhpcd it works fine.
Any suggestions?

I tried to use the one from testing, along with the gnome GUI from testing, but with no luck...
As you can see here, it tells me it is waiting fr the key, http://gallery.timmy.dk/Screenshots/gno … anager.png
But in the consle, iwconfig says I'm already connected...
So I'm pretty sure there something wrong with the dhcp

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.

Gnome-network-manager problems

Hello all,
I'm trying to use gnome-network-manager to connect to my wifi as it is WEP enabled and I don't know how to get it working in 'network'.
I followed this tutorial: http://wiki.archlinux.org/index.php/NetworkManager
However, when I reboot under those settings, I can't connect to anything, including ethernet.
Is there a problem in the wiki or is there a workaround that hasn't been posted there yet? I'm utterly confused as to why it will not work.
Also, if you need me to paste any code from any file, can you also tell me an easy way to copy/paste between aterm and Opera as I haven't found a way to do that yet.
Thank you very much for any help.
Matt

[matt@myhost ~]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"3KR98"
Mode:Managed Frequency:2.427 GHz Access Point: 00:18:01:E0:43:1A
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=21/100 Signal level=-72 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:76 Missed beacon:31
[matt@myhost ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:A1:71:02
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fea1:7102/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82717 errors:300 dropped:592 overruns:300 frame:0
TX packets:61302 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:79395572 (75.7 Mb) TX bytes:9179527 (8.7 Mb)
Interrupt:22 Base address:0x6800
eth1 Link encap:Ethernet HWaddr 00:13:CE:6A:FE:C1
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe6a:fec1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:309 errors:0 dropped:76 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2420181 (2.3 Mb) TX bytes:2012 (1.9 Kb)
Interrupt:23 Base address:0x4000 Memory:bc005000-bc005fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20464 (19.9 Kb) TX bytes:20464 (19.9 Kb)
ill post output of disabling gnome-net-manager in a bit (i have to reboot and save it as a file first).
also, im running fluxbox, not gnome, so could that be part of the problem? am i missing something flux specific?

Gnome-network-manager & XFCE 4.4

Hey guys, someone know if gnome-network-manager also run on XFCE 4.4?
It won't run on my XFCE
Solutions to problem?
Bye,
Riccardo

Captain Spaulding wrote:
OK, open NetworkManager.conf and search for the line
<policy at_console="true">
and add this line:
<allow own="org.freedesktop.NetworkManagerInfo"/>
That, at least, should fix your initial issue. I have only just begun to learn more about dbus, so I have no clue about the second problem.
Mmmmm no entries as <policy at_console="true"> in my NetworkManager.conf....
So here we are my NetworkManager.conf:
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<policy user="root">
<allow own="org.freedesktop.NetworkManager"/>
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy group="users">
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy user="hal">
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy context="default">
<deny own="org.freedesktop.NetworkManager"/>
<deny send_destination="org.freedesktop.NetworkManager"/>
<deny send_interface="org.freedesktop.NetworkManager"/>
</policy>
</busconfig>

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

Gnome-network-manager doesn't work at all

Hello, guys!
Gnome-network-manager starts but doesn't show its icon in Notification Area.
ps -A shows that the process is running correctly.
[sergo@myhost ~]$ ps -A |grep nm
4360 pts/2 00:00:00 nm-applet
I carefully studied all solutions listed here. My DAEMONS string is
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs crond alsa sensors portmap fam dbus hal dhcdbd networkmanager networkmanager-dispatcher @cups gdm)
Please help.

yes, I have done it, and nothing happen
edit : I have reinstall the software, and now it is OK, tks for the help
Last edited by serafimsaudade (2007-05-20 17:34:56)

WPA on gnome-network-manager

Hi!
I have a rather small problem. I tried to get a wireless connection by using networkmanager and the gnome-network-manager applet. It all ran fine but when I took a closer look at the applet today I saw that there's only WEP protection showing up. So I googled a little bit and recompiled the nm-applet with wpa_supplicant support. I reinstalled the package but still no WPA shows up. S can anyone help me with this, since I rather don't want to go back using unsecure WEP protection.
Thanks a lot!

gnome-keyring :< it's ugly but now works
And this made me looking like an idiot in my university today ;(
Bluman's plugin for NM isn't working too ;( I even couldn't compile it from abs
checking for a Python interpreter with version >= 2.5... python
checking for python... /usr/bin/python
checking for python version... 3.2
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python3.2/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python3.2/site-packages
checking for headers required to compile python extensions... File "<string>", line 1
import sys; print sys.prefix
^
SyntaxError: invalid syntax
File "<string>", line 1
import sys; print sys.exec_prefix
^
SyntaxError: invalid syntax
not found
configure: error: Could not find Python headers
EDIT: Adding "export PYTHON=/usr/bin/python2" before "./configure" helps
Last edited by swiftgeek (2011-10-03 17:52:24)

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

Gnome Network Manager under Fluxbox

Hello! Im using fluxbox and I had wifi-radar to connect wifi but I missed a lot the gnome networkmanager so I've removed wifi-radar and installed it.
Now Im getting mad because, after following all the steps the networkmanager starts correctly but says there are no network devices and I cant solve this.
Some info
ifconfig:
eth1 Link encap:Ethernet HWaddr 00:13:02:13:BC:DD
inet addr:192.168.1.35 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:2ff:fe13:bcdd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1306 errors:0 dropped:4620 overruns:0 frame:0
TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:871040 (850.6 Kb) TX bytes:258880 (252.8 Kb)
Interrupt:19 Base address:0xc000 Memory:d0100000-d0100fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:400 (400.0 b) TX bytes:400 (400.0 b)
iwconfig:
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"WLAN_0A"
Mode:Managed Frequency:2.462 GHz Access Point: 00:01:38:6C:DA:1D
Bit Rate:54 Mb/s Tx-Power:15 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=86/100 Signal level=-47 dBm Noise level=-47 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:4620 Missed beacon:0
and /etc/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="es_ES.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Madrid"
KEYMAP="es"
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=(b44 mii ipw3945 iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-al
loc 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="Nosferatu"
# 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="dhcp"
INTERFACES=(lo !eth0 !eth1)
# 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 dhcdbd networkmanager netfs crond ipw3945d)
Someone knows what's going on?
Thank You!

wonder wrote:i mean add hal to DAEMON list.
DAEMONS=(syslog-ng !network hal dhcdbd networkmanager netfs crond ipw3945d)
Yeaaaaah! Now its working!!
I added the daemon.
Thank you very much!

Keyring annoyance using gnome network manager, any solutions?

Has anyone figured out how to get rid of the annoying keyring prompt every time you enter a WPA (or any other) when connecting to a WLAN? I see the problem floating around but havent seemed to have come across any solutions.

enrique wrote:
iphitus wrote:pam_keyring, google it.
Does it work for you? pam_keyring allways fails the first time I log in.
Btw there is a pkgbuild for it here: http://aur.archlinux.org/packages.php?d … s=0&SeB=nd
I didnt try on arch, it worked fine for me on Suse Linux Enterprise Desktop using a fedora rpm iirc.
James

Wireless, Network-manager, dbus problem

Hey, I'm trying to connect to wireless network at school using dhcdbd, gnome-network-manager, nm-applet... and it works but get disconnected constantly. Don't know much about networking so could use some help. Here's some output with lots of dbus errors...any ideas? Thanks.
** Message: <information> You are now connected to the wireless network 'XXXXXXXXXXX'.
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'XXXXXXXXXXX' in keyring: 2
** Message: <information> You are now connected to the wireless network 'XXXXXXXXXXX'.
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'XXXXXXXXXXX' in keyring: 2

When I configure a Wep key to my wireless internet
sharing network, my windows installed notebook can't
connect to my iMac. But when I set up it free the
notebook connects easily.
There does seem to be a known issue with a WEP encrypted software base station and Windows clients.
As far as I am aware there is no way to get a Windows client to connect to a WEP encrypted software base station (sharing internet via Airport on a Mac).
I tried both with ASCII and
HEX keys and generated them from:
You could try a ASCII key of
1234567123456
which will be a HEX key of
31323334353637313233343536
However if this doesn't work then nothing will.
I don't know what to do and I don't want to set a
wireless network free for security problems. Does
anyone know a solution?
Yes, get a wireless router and use that, it really is the only suitable solution.
iFelix

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

I need a keyring (that works with network-manager)

Hi there,
I'm new to Arch linux (coming from Ubuntu) and I'm wondering how to set up a keyring that works with that gnome-network-manager applet and ssh(fs). I previously used GNOME and the gnome keyring, and all out of the box.
I couldn't find any manuals on how to set up the gnome-keyring in Arch linux, neither regarding ssh(fs) nor network-manager. I read people are complaining about network-manager asking for the keyring-unlocking-password, but this doesn't happen for me.
How do I set up the gnome-keyring propertly?

siriusb wrote:moljac024:
https://bugs.launchpad.net/wicd/+bug/377471
From this bug page:
The /etc/wicd/wireless-settings.conf file is made root-readable only. This means that any malicious users must have root access or physical access to the machine. In either of these cases, you have far more problems than worrying about the wireless network key.
Please see http://developer.pidgin.im/wiki/PlainTextPasswords for a very good explanation as to why the passwords are not encrypted.
It may be plain text, but only root can read/write.

[xfce4] network-manager-applet not asking for Wifi password

I am running XFCE with the gnome network-manager-applet and kwallet as password storage and I do not want to use the gnome keyring because it is making many problems with my current setup.
There are multiple ways to store passwords in NetworkManager. To save them plain in the config files is not an option for me. So I can put them in a password store or hack them in every time I want to connect.
While the gnome network-manager-applet does not work with kwallet I accepted to do all the hackery every time.
Problem: I even can not hack in the passwords.
If I try to connect the connection is disconnected immediately. The logs say, that "The name org.freedesktop.secrets was not provided by any .service files".
Long story short:
- NetworkManager needs the dbus service "org.freedesktop.secrets" to read passwords (via password store or via prompt)
- kwallet does not announce "org.freedesktop.secrets" - this is done by the nm-plasma applet (which I can not run without hacking XFCE)
- gnome-keyring announces itself as a secret agent but does not work with my setup
Do I need to write my own secret agent which only shows a password prompt and parses the input to NM or is there any option/tool/patch/hack/miracle that I have missed to use kwallet with gnome network-manager-applet or to get a password prompt without installing gnome-keyring?
Thanks in advance
Last edited by frederik (2015-04-14 15:30:24)

add this to your start-up: gnome-keyring-daemon --components=gpg
Edit: and install gnome-keyring ofc
Last edited by MakeTheGOD (2015-04-28 05:24:33)

Gnome Network Manager Isues

Similar Messages

Maybe you are looking for