On Sun, 21 Jun 2009 20:40:20 -0700, Zack Weinberg wrote:
On Wed, Jun 17, 2009 at 2:28 AM, David Paleinod.pale...@gmail.com wrote:
Could you please post:
- /var/log/wicd/wicd.log (enable the debug mode from the GUI first),
- /etc/wicd/*-settings.conf (be sure to remove sensible data),
On Tue, 23 Jun 2009 21:34:55 +0200, David Paleino wrote:
On Sun, 21 Jun 2009 20:40:20 -0700, Zack Weinberg wrote:
On Wed, Jun 17, 2009 at 2:28 AM, David Paleinod.pale...@gmail.com wrote:
Could you please post:
- /var/log/wicd/wicd.log (enable the debug mode from the GUI first),
On Tue, Jun 23, 2009 at 12:46 PM, David Paleinod.pale...@gmail.com 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
On Tue, Jun 23, 2009 at 12:57 PM, Debian Bug Tracking System
ow...@bugs.debian.org wrote:
On Tue, Jun 23, 2009 at 12:46 PM, David Paleinod.pale...@gmail.com 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.
On Tue, 23 Jun 2009 13:43:33 -0700, Zack Weinberg wrote:
On Tue, Jun 23, 2009 at 12:57 PM, Debian Bug Tracking System
ow...@bugs.debian.org wrote:
On Tue, Jun 23, 2009 at 12:46 PM, David Paleinod.pale...@gmail.com
wrote:
Would you please check whether setting the Wireless interface to
On Tue, Jun 23, 2009 at 1:47 PM, David Paleino d.pale...@gmail.com wrote:
On Tue, 23 Jun 2009 13:43:33 -0700, Zack Weinberg wrote:
Should it not rather remain open and be marked as upstream and to be
fixed in 2.0?
Nope. It was using wlan0 as wired because you set it so, or did I
reopen 525893
retitle 525893 please improve wired/wireless hardware detection
severity 525893 minor
thanks
On Tue, 23 Jun 2009 13:58:39 -0700, Zack Weinberg wrote:
On Tue, Jun 23, 2009 at 1:47 PM, David Paleino d.pale...@gmail.com wrote:
Try to leave the fields blank, and see what gets
On Tue, Jun 23, 2009 at 2:05 PM, David Paleinod.pale...@gmail.com wrote:
2009/06/23 13:53:33 :: automatically detected wired interface wlan0
2009/06/23 13:53:33 :: did not find wired_interface in configuration, setting
default wlan0
2009/06/23 13:53:33 :: setting wired interface wlan0
Ok,
On Tue, 16 Jun 2009 14:51:01 -0700, Zack Weinberg wrote:
On Mon, Jun 15, 2009 at 3:26 AM, David Paleinod.pale...@gmail.com wrote:
Would you please test the package from experimental? I didn't see this
behaviour with 1.5.9-5, and am not seeing it in 1.6.0-2~pre1. Maybe
something's wrong
On Mon, Jun 15, 2009 at 3:26 AM, David Paleinod.pale...@gmail.com wrote:
Would you please test the package from experimental? I didn't see this
behaviour with 1.5.9-5, and am not seeing it in 1.6.0-2~pre1. Maybe
something's
wrong in your setup?
Before asking more, please try out the new
Hello Zack,
On Mon, 27 Apr 2009 11:00:26 -0700, Zack Weinberg wrote:
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
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
12 matches
Mail list logo
