|SOLVED] nm-applet can't connect to wireless network (nothing happens)

Lowra · 2011-11-06 13:36:21

Hi,

I'm running Arch without a DE, I'm using openbox, tint2, and I switched to networkmanager for my internet connexions.
Wired network works fine, but when I try to connect to a wireless network, nothing happens. A box doesn't appear to ask me the WEP/WPA key, and it does not connect either if the AP is without security key.

Here is my rc.conf:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
#   LANG in /etc/locale.conf takes precedence
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged, using "" makes hwclock fall back
#   to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
#   Note: if unset, the value in /etc/localtime is used unchanged
# 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.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Paris"
KEYMAP="fr-latin9"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=(vboxdrv)

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# 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="laptop"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
#   - broadcast: broadcast address (ignored for DHCP) (optional)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
broadcast=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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 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
#
# If you are sure nothing else touches your hardware clock (such as ntpd or
# a dual-boot), you might want to enable 'hwclock'. Note that this will only
# make a difference if the hwclock program has been calibrated correctly.
#
# If you use a network filesystem you should enable 'netfs'.
#
DAEMONS=(@slim @preload dbus @networkmanager @alsa)

Here is my iwconfig:

lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=14 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

Here is my openbox's autostart:

#
# These things are run when an Openbox X Session is started.
# You may place a similar script in $HOME/.config/openbox/autostart
# to run user-specific things.
#

setxkbmap fr &
nitrogen --restore &
tint2 &
(sleep 3 && /usr/bin/nm-applet --sm-disable) &

Thank you !

EDIT: SOLVED thanks to this part of the wiki

Last edited by Lowra (2011-11-06 14:06:05)

karol · 2011-11-06 14:04:34

Lowra, please edit your post.
When pasting code, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode

like this

It makes the code more readable and more convenient to scroll through.

Lowra · 2011-11-06 14:06:38

Done karol, sorry

& Topic SOLVED thanks to the Wiki

wonder · 2011-11-06 14:27:02

Lowra wrote:

Done karol, sorry
& Topic SOLVED thanks to the Wiki

if you applied that workaround it means that you are not starting your graphical interface in the right way.

gozes · 2012-01-04 02:36:59

hello I'm having the same issue even after being part of the wheel grope and run consolekit on my openbox session any ideas?

Last edited by gozes (2012-01-04 02:38:16)

7h3kk1d · 2012-12-22 18:00:57

I'm having this same problem using awesome. I can connect if I pretend it's a hidden netwkr and type the ssid but no configuration window ever comes up

Arch Linux

#1 2011-11-06 13:36:21

|SOLVED] nm-applet can't connect to wireless network (nothing happens)

#2 2011-11-06 14:04:34

Re: |SOLVED] nm-applet can't connect to wireless network (nothing happens)

#3 2011-11-06 14:06:38

Re: |SOLVED] nm-applet can't connect to wireless network (nothing happens)

#4 2011-11-06 14:27:02

Re: |SOLVED] nm-applet can't connect to wireless network (nothing happens)

#5 2012-01-04 02:36:59

Re: |SOLVED] nm-applet can't connect to wireless network (nothing happens)

#6 2012-12-22 18:00:57

Re: |SOLVED] nm-applet can't connect to wireless network (nothing happens)

Board footer