Bug#642546: wicd-curses: wired autoconnect doesn't work

2011-11-07 Thread Ian Zimmerman

David Does it happen if you run the client as non-root?

No, it works now.  I don't know if it is the non-root or something else
I changed, but it connects automatically now as expected.

Sorry it took me so lang to get back to this issue.

-- 
Ian Zimmerman
gpg public key: 1024D/C6FF61AD
fingerprint: 66DC D68F 5C1B 4D71 2EE5  BD03 8A00 786C C6FF 61AD
Rule 420: All persons more than eight miles high to leave the court.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642546: wicd-curses: wired autoconnect doesn't work

2011-09-24 Thread David Paleino
On Fri, 23 Sep 2011 13:38:56 -0700, Ian Zimmerman wrote:

 David Do you have the chance to test the graphical client (wicd-gtk)?
 David So that we can exclude a problem in wicd-curses itself.
 
 Hmm .. I'm not into running graphical apps as root.  I'll try the
 command line client, though.

No need to run that as root -- nor wicd-curses. They use dbus and allow users
from the netdev group to connect.

Does it happen if you run the client as non-root?

David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 | http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174


signature.asc
Description: PGP signature


Bug#642546: wicd-curses: wired autoconnect doesn't work

2011-09-23 Thread Ian Zimmerman
Package: wicd-curses
Version: 1.7.0+ds1-6
Severity: normal

Dear Maintainer,

In the wicd-curses interface, I went to the Prefs panel (by hitting
P) and selected the option Always switch to wired connection when
available.  I saved the prefs (with F10), exited wicd-curses, shut
down the computer, connected the ethernet cable, and booted back up.

Result: no network connection.  Moreover, when I start wicd-curses,
before the interface is displayed, I get a brief message Rename
failed.  Connection still down when wicd-curses interface comes up.
But manually selecting the wired connection in the list and hitting
C to connect does work.

Note that when I don't connect the ehternet cable, the computer
connects automatically to my home WiFi upon boot, as expected.

I expected that it would work with similar ease for the wired
connection.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (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/dash

Versions of packages wicd-curses depends on:
ii  python2.6.7-3
ii  python-urwid  0.9.9.2-1  
ii  wicd-daemon   1.7.0+ds1-6

Versions of packages wicd-curses recommends:
pn  sudo  none

wicd-curses suggests no packages.

Versions of packages wicd-cli depends on:
ii  wicd-daemon  1.7.0+ds1-6

Versions of packages wicd-cli recommends:
pn  sudo  none

Versions of packages wicd-daemon depends on:
ii  adduser 3.113  
ii  dbus1.4.14-1   
ii  debconf [debconf-2.0]   1.5.40 
ii  iproute 20110629-1 
ii  iputils-ping3:20101006-1+b1
ii  isc-dhcp-client [dhcp3-client]  4.1.1-P1-17
ii  lsb-base3.2-28 
ii  net-tools   1.60-24.1  
ii  psmisc  22.13-1
ii  python  2.6.7-3
ii  python-dbus 0.84.0-2   
ii  python-gobject  2.28.6-4   
ii  python-wicd 1.7.0+ds1-6
ii  wireless-tools  30~pre9-5  
ii  wpasupplicant   0.7.3-3

wicd-daemon recommends no packages.

Versions of packages wicd-daemon suggests:
ii  pm-utils  1.4.1-8

Versions of packages python-wicd depends on:
ii  python  2.6.7-3
ii  python-support  1.0.14 

-- debconf information:
* wicd/users:



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642546: wicd-curses: wired autoconnect doesn't work

2011-09-23 Thread David Paleino
Hello Ian,

On Fri, 23 Sep 2011 11:21:36 -0700, Ian Zimmerman wrote:

 In the wicd-curses interface, I went to the Prefs panel (by hitting
 P) and selected the option Always switch to wired connection when
 available.  I saved the prefs (with F10), exited wicd-curses, shut
 down the computer, connected the ethernet cable, and booted back up.
 
 Result: no network connection.  Moreover, when I start wicd-curses,
 before the interface is displayed, I get a brief message Rename
 failed.  Connection still down when wicd-curses interface comes up.
 But manually selecting the wired connection in the list and hitting
 C to connect does work.

I got that reported in the upstream IRC channel as well. However, that rename
failed is because it couldn't rename the process from python to something
more sensible. I don't think it's related to the connection at all.

Would you please attach relevant parts of /var/log/wicd/wicd.log ? Also with
debugging information enabled could be useful, thanks.

Do you have the chance to test the graphical client (wicd-gtk)? So that we can
exclude a problem in wicd-curses itself.

Thanks,
David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 | http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174


signature.asc
Description: PGP signature


Bug#642546: wicd-curses: wired autoconnect doesn't work

2011-09-23 Thread Ian Zimmerman

David I got that reported in the upstream IRC channel as well. However,
David that rename failed is because it couldn't rename the process
David from python to something more sensible. I don't think it's
David related to the connection at all.

Ok, makes sense.

David Would you please attach relevant parts of /var/log/wicd/wicd.log
David ? Also with debugging information enabled could be useful,
David thanks.

It must be sanitized, since it contains the WPA preshared key.  (Which
is pretty scary in itself, I think).  So it will take a while.

David Do you have the chance to test the graphical client (wicd-gtk)?
David So that we can exclude a problem in wicd-curses itself.

Hmm .. I'm not into running graphical apps as root.  I'll try the
command line client, though.

BTW, I lied: it behaves the same for the wireless connection now.  It
definitely used to autoconnect to that, though.  So it's a regression
:-P

-- 
Ian Zimmerman
gpg public key: 1024D/C6FF61AD
fingerprint: 66DC D68F 5C1B 4D71 2EE5  BD03 8A00 786C C6FF 61AD
Rule 420: All persons more than eight miles high to leave the court.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642546: wicd-curses: wired autoconnect doesn't work

2011-09-23 Thread Ian Zimmerman

David Would you please attach relevant parts of /var/log/wicd/wicd.log
David ? Also with debugging information enabled could be useful,
David thanks.

Ian It must be sanitized, since it contains the WPA preshared key.
Ian (Which is pretty scary in itself, I think).  So it will take a
Ian while.

Attached.

David Do you have the chance to test the graphical client (wicd-gtk)?
David So that we can exclude a problem in wicd-curses itself.

Ian Hmm .. I'm not into running graphical apps as root.  I'll try the
Ian command line client, though.

Tried wicd-cli.  It works to connect, but after reboot, again no
connection.
2011/09/23 13:30:01 :: Exception KeyError: KeyError(-1220213056,) in module 
'threading' from '/usr/lib/python2.6/threading.pyo' ignored
2011/09/23 20:32:04 :: ---
2011/09/23 20:32:04 :: wicd initializing...
2011/09/23 20:32:04 :: ---
2011/09/23 20:32:04 :: wicd is version 1.7.0 552
2011/09/23 20:32:04 :: setting backend to external
2011/09/23 20:32:04 :: trying to load backend external
2011/09/23 20:32:04 :: successfully loaded backend external
2011/09/23 20:32:04 :: WARNING: No path found for dhcpcd
2011/09/23 20:32:04 :: WARNING: No path found for pump
2011/09/23 20:32:04 :: WARNING: No path found for udhcpc
2011/09/23 20:32:05 :: WARNING: No path found for ethtool
2011/09/23 20:32:05 :: WARNING: No path found for gksudo
2011/09/23 20:32:05 :: WARNING: No path found for kdesu
2011/09/23 20:32:05 :: WARNING: No path found for ktsuss
2011/09/23 20:32:05 :: trying to load backend external
2011/09/23 20:32:05 :: successfully loaded backend external
2011/09/23 20:32:05 :: WARNING: No path found for dhcpcd
2011/09/23 20:32:05 :: WARNING: No path found for pump
2011/09/23 20:32:05 :: WARNING: No path found for udhcpc
2011/09/23 20:32:05 :: WARNING: No path found for ethtool
2011/09/23 20:32:05 :: WARNING: No path found for gksudo
2011/09/23 20:32:05 :: WARNING: No path found for kdesu
2011/09/23 20:32:05 :: WARNING: No path found for ktsuss
2011/09/23 20:32:05 :: Couldn't detect a wireless interface.
2011/09/23 20:32:05 :: setting wireless interface wlan0
2011/09/23 20:32:05 :: automatically detected wired interface eth0
2011/09/23 20:32:05 :: setting wired interface eth0
2011/09/23 20:32:05 :: setting wpa driver wext
2011/09/23 20:32:05 :: setting use global dns to False
2011/09/23 20:32:05 :: setting global dns
2011/09/23 20:32:05 :: global dns servers are None None None
2011/09/23 20:32:05 :: domain is None
2011/09/23 20:32:05 :: search domain is None
2011/09/23 20:32:05 :: setting automatically reconnect when connection drops 
False
2011/09/23 20:32:05 :: found wired_connect_mode in configuration 1
2011/09/23 20:32:05 :: found should_verify_ap in configuration 1
2011/09/23 20:32:05 :: Setting dhcp client to 1
2011/09/23 20:32:05 :: Wireless configuration file found...
2011/09/23 20:32:05 :: Wired configuration file found...
2011/09/23 20:32:05 :: chmoding configuration files 0600...
2011/09/23 20:32:05 :: chowning configuration files root:root...
2011/09/23 20:32:05 :: Using wireless interface...wlan0
2011/09/23 20:32:05 :: Using wired interface...eth0
2011/09/23 20:32:05 :: scanning start
2011/09/23 20:32:05 :: ifconfig wlan0 up
2011/09/23 20:32:05 :: iwlist wlan0 scan
2011/09/23 20:32:07 :: scanning done
2011/09/23 20:32:07 :: found 13 networks:
2011/09/23 20:32:07 :: found afterscript in configuration None
2011/09/23 20:32:07 :: found psk in configuration 
54156e629d07c1d243494e5859e56cd67bccb01a1e90471b5a6c1065dffb6064
2011/09/23 20:32:07 :: found dhcphostname in configuration gatsby
2011/09/23 20:32:07 :: found postdisconnectscript in configuration None
2011/09/23 20:32:07 :: found dns_domain in configuration None
2011/09/23 20:32:07 :: found netmask in configuration None
2011/09/23 20:32:07 :: found key in configuration ThisIsThePresharedWPAKey
2011/09/23 20:32:07 :: found usedhcphostname in configuration 1
2011/09/23 20:32:07 :: found predisconnectscript in configuration None
2011/09/23 20:32:07 :: found gateway in configuration None
2011/09/23 20:32:07 :: found use_global_dns in configuration 0
2011/09/23 20:32:07 :: found dns3 in configuration None
2011/09/23 20:32:07 :: found search_domain in configuration None
2011/09/23 20:32:07 :: found dns2 in configuration None
2011/09/23 20:32:07 :: found use_settings_globally in configuration 0
2011/09/23 20:32:07 :: found use_static_dns in configuration 0
2011/09/23 20:32:07 :: found ip in configuration None
2011/09/23 20:32:07 :: found beforescript in configuration None
2011/09/23 20:32:07 :: found enctype in configuration wpa
2011/09/23 20:32:07 :: found automatic in configuration 1
2011/09/23 20:32:07 :: found dns1 in configuration None
2011/09/23 20:32:11 :: ifconfig eth0
2011/09/23 20:32:11 :: ifconfig wlan0
2011/09/23 20:32:16 :: ifconfig eth0
2011/09/23 20:32:16 :: ifconfig wlan0
2011/09/23 20:32:21 :: ifconfig eth0
2011/09/23 20:32:21 :: ifconfig wlan0
2011/09/23 20:32:26 :: ifconfig eth0