Your message dated Tue, 16 Jun 2009 09:52:42 +0200
with message-id <20090616095242.11906...@moocca>
and subject line Re: Bug#533277: wicd: unable to disconnect from wireless when
it's not there
has caused the Debian Bug report #533277,
regarding wicd: unable to disconnect from wireless when it's not there
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
533277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533277
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wicd
Version: 1.5.9-5
Severity: normal
Hi!
wicd-client only displays available wireless networks. So far, so bad.
If one is connected to a wireless network, leaves the place in e.g.
connected suspend, brings it up at some other spot, wicd still is in the
impression to be connected to the same network. Given that it doesn't
get displayed one can't hit the disconnect button.
I guess this should rather be worked around by just connecting to the
newly wanted network and that it will automatically disconnect from the
old, but I'm often using public transports where there is no new network
I would connect to, rather would like to have my laptop to know that it
can't route anything instead of running into timeouts when trying to do
DNS lookups or trying to get responses from the default route.
Quick workaround is hitting connect on the wired network and then
hitting abort, but I don't believe that that is the way it should have
to be - it's like hitting start to quit. ;)
So long!
Rhonda
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.29-2-powerpc
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages wicd depends on:
ii adduser 3.110 add and remove users and groups
ii dhcp3-client 3.1.1-6 DHCP client
ii iproute 20090324-1 networking and traffic control too
ii net-tools 1.60-23 The NET-3 networking toolkit
ii python 2.5.4-2 An interactive high-level object-o
ii python-dbus 0.83.0-1 simple interprocess messaging syst
ii python-glade2 2.14.1-3 GTK+ bindings: Glade support
ii python-gtk2 2.14.1-3 Python bindings for the GTK+ widge
ii python-support 1.0.3 automated rebuilding support for P
ii wireless-tools 29-1.1 Tools for manipulating Linux Wirel
ii wpasupplicant 0.6.9-3 client support for WPA and WPA2 (I
wicd recommends no packages.
Versions of packages wicd suggests:
ii pm-utils 1.2.5-2 utilities and scripts for power ma
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.6.0-1
Hello Rhonda,
(lots of bugs being filed eh! ;) )
On Tue, 16 Jun 2009 08:47:31 +0200, Gerfried Fuchs wrote:
> wicd-client only displays available wireless networks.
Right.
> So far, so bad.
> If one is connected to a wireless network, leaves the place in e.g.
> connected suspend, brings it up at some other spot, wicd still is in the
> impression to be connected to the same network. Given that it doesn't
> get displayed one can't hit the disconnect button.
In 1.6.0 there is a "Disconnect all" button which would fit your situation.
> I guess this should rather be worked around by just connecting to the
> newly wanted network and that it will automatically disconnect from the
> old,
Yes, exactly :)
> but I'm often using public transports where there is no new network
> I would connect to, rather would like to have my laptop to know that it
> can't route anything instead of running into timeouts when trying to do
> DNS lookups or trying to get responses from the default route.
Ok, I believe the "Disconnect all" button is what you're looking for, then.
Closing the bug with Version 1.6.0-1 (quickly passed in experimental).
> Quick workaround is hitting connect on the wired network and then
> hitting abort, but I don't believe that that is the way it should have
> to be - it's like hitting start to quit. ;)
Ahahah :)
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
--- End Message ---
