Your message dated Tue, 23 Jun 2009 21:54:30 +0200
with message-id <20090623215430.5f4ec...@pingu>
and subject line Re: Bug#525893: wicd: claims to be connected to wired network 
when  actually on wireless
has caused the Debian Bug report #525893,
regarding wicd: claims to be connected to wired network when actually on 
wireless
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.)


-- 
525893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525893
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wicd
Version: 1.5.9-5
Severity: normal

Recently, wicd has started claiming that the active network is wired,
even when it isn't.  It's very obvious - you pick a wireless network,
and it goes through the entire connection sequence correctly, and then
it says "ok! I'm connected to the wired network."  All the user interfaces
are consistent in this error.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wicd depends on:
ii  adduser                     3.110        add and remove users and groups
ii  dhcp3-client                3.1.2-1      DHCP client
ii  ethtool                     6+20090307-1 display or change Ethernet device 
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-2     GTK+ bindings: Glade support
ii  python-gtk2                 2.14.1-2     Python bindings for the GTK+ widge
ii  python-support              1.0.2        automated rebuilding support for P
ii  wireless-tools              29-1.1       Tools for manipulating Linux Wirel
ii  wpasupplicant               0.6.9-2      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 ---
On Tue, 23 Jun 2009 12:53:48 -0700, Zack Weinberg wrote:

> On Tue, Jun 23, 2009 at 12:46 PM, David Paleino<[email protected]> wrote:
> > An update: it appears here indeed, but the code is really looking
> > for /sys/class/net/<iface>/wireless . And I *don't* have that.
> > So my wlan0 should've been recognized as a wired connection: it isn't
> > because I set it as Wireless interface in the Preferences dialog.
> >
> > Would you please check whether setting the Wireless interface to "wlan0"
> > workarounds the bug?
> 
> It was set as Wireless in the client preferences ... but it was *also*
> set as the Wired interface.  Changing that to eth0 does work around
> the bug, and the change seems to stick across a reboot.

Great, closing the bug.

Kindly,
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

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to