Ubuntu
gnome-system-tools package

wifi : no connection with graphical tools

Bug #99915 reported by Clement Quaquin
2
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: gnome-system-tools

In Feisty from scratch with all updates done, it's impossible to connect to my wifi network with the Gnome's graphical tools : neither gnome-system-tools network-admin nor network-manager, see dmesg log :
[ 112.516000] wlan0: changing radio power level to 18 dBm (23)
[ 113.904000] wlan0: changing radio power level to 18 dBm (23)
[ 114.208000] eth0: link down
[ 139.744000] wlan0: changing radio power level to 18 dBm (23)
[ 140.036000] eth0: link down
[ 152.964000] wlan0: changing radio power level to 18 dBm (23)
[ 156.792000] wlan0: tx error 0x20, buf 04! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
[ 181.976000] wlan0: tx error 0x80, buf 07! (DMA error)
[ 194.728000] wlan0: tx error 0x80, buf 08! (DMA error)
[ 239.032000] wlan0: tx error 0x80, buf 07! (DMA error)
[ 248.600000] wlan0: tx error 0x80, buf 15! (DMA error)
[ 261.620000] wlan0: tx error 0x80, buf 07! (DMA error)
[ 264.056000] wlan0: tx error 0x80, buf 15! (DMA error)
[ 307.684000] wlan0: tx error 0x80, buf 08! (DMA error)
[ 443.656000] wlan0: tx error 0x80, buf 15! (DMA error)
[ 701.852000] wlan0: tx error 0x80, buf 15! (DMA error)
[ 831.580000] wlan0: tx error 0x80, buf 07! (DMA error)

However, the connection works fine in command line mode :
sudo ifdown wlan0
sudo ifup wlan0

(sorry for my english and sorry if this bug is already reported, it's my first bug !)

Revision history for this message
Clement Quaquin (clement-quaquin) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

does "sudo /etc/init.d/network restart" work correctly?

Revision history for this message
Clement Quaquin (clement-quaquin) wrote :

It works :
clem@kwaklaptop:~$ sudo /etc/init.d/networking restart
Password:
 * Reconfiguring network interfaces...
There is already a pid file /var/run/dhclient.wlan0.pid with pid 3957
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:11:95:7e:4c:03
Sending on LPF/wlan0/00:11:95:7e:4c:03
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.254 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:11:95:7e:4c:03
Sending on LPF/wlan0/00:11:95:7e:4c:03
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPOFFER from 192.168.0.254
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.254
bound to 192.168.0.11 -- renewal in 359443 seconds.
                                                                         [ OK ]

Revision history for this message
Sebastien Bacher (seb128) wrote :

weird, the graphical tools should do the same, if that happens with network-manager also that's not likely to be a g-s-t bug

Changed in gnome-system-tools:
importance: Undecided → Low
Revision history for this message
Clement Quaquin (clement-quaquin) wrote :

The problem disappeared today with the last update.
The wifi connection starts automatically.
Thank you !

Revision history for this message
Sebastien Bacher (seb128) wrote :

marking fixed then

Changed in gnome-system-tools:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.