After upgrading to wicd-1.6.0_alpha2 I cannot connect to mi wireless network anymore. Validation of the WAP2 key seems to work, but then it says MY-ESSID: Obtaining IP address... and the progress bar says connecting all the time. As a workaround I can use "dhclient wlan0" in a terminal. I tried setting the dhcp client to dhclient instead of Automatic, but that doesn't make a difference. Reproducible: Always root@thinkpad> paludis --info /home/horn paludis 0.36.1 Paludis build information: Compiler: CXX: x86_64-pc-linux-gnu-g++ 4.3.3 CXXFLAGS: -march=core2 -O2 -pipe LDFLAGS: -Wl,-O1 -Wl,--as-needed DATE: 2009-04-23T23:29:40+0200 Libraries: C++ Library: GNU libstdc++ 20090124 Reduced Privs: reduced_uid: 108 reduced_uid->name: paludisbuild reduced_uid->dir: /var/tmp/paludis reduced_gid: 1009 reduced_gid->name: paludisbuild Paths: DATADIR: /usr/share LIBDIR: /usr/lib64 LIBEXECDIR: /usr/libexec SYSCONFDIR: /etc PYTHONINSTALLDIR: RUBYINSTALLDIR: /usr/lib64/ruby/site_ruby/1.8/x86_64-linux Environment: Format: paludis Config dir: /etc/paludis World file: /var/db/pkg/world
Anything in /var/log/wicd/wicd.log that could help debug this? I solely use dhcpcd and I know that at least one of the upstream devs solely uses dhclient.
Here's everything that is logged in one connection attempt: 2009/04/28 02:02:45 :: Connecting to wireless network tsdhNET 2009/04/28 02:02:46 :: Putting interface down 2009/04/28 02:02:46 :: Releasing DHCP leases... 2009/04/28 02:02:46 :: ERROR:dbus.service:Unable to append ('g\xc6isQ\xffJ\xec)\xcd\xba\xab\xf2\xfb\xe3F|\xc2T\xf8\x1b\xe8\xe7\x8dvZ.c3\x9f\xc9\x9a',) to message with signature (s) (guessed): <type 'exceptions.UnicodeError'>: String parameters to be sent over D-Bus must be valid UTF-8 2009/04/28 02:02:46 :: ERROR:dbus.service:Unable to append ('g\xc6isQ\xffJ\xec)\xcd\xba\xab\xf2\xfb\xe3F|\xc2T\xf8\x1b\xe8\xe7\x8dvZ.c3\x9f\xc9\x9a',) to message with signature (s) (guessed): <type 'exceptions.UnicodeError'>: String parameters to be sent over D-Bus must be valid UTF-8 2009/04/28 02:02:46 :: ERROR:dbus.service:Unable to append ('g\xc6isQ\xffJ\xec)\xcd\xba\xab\xf2\xfb\xe3F|\xc2T\xf8\x1b\xe8\xe7\x8dvZ.c3\x9f\xc9\x9a',) to message with signature (s) (guessed): <type 'exceptions.UnicodeError'>: String parameters to be sent over D-Bus must be valid UTF-8 2009/04/28 02:02:46 :: ERROR:dbus.service:Unable to append ('g\xc6isQ\xffJ\xec)\xcd\xba\xab\xf2\xfb\xe3F|\xc2T\xf8\x1b\xe8\xe7\x8dvZ.c3\x9f\xc9\x9a',) to message with signature (s) (guessed): <type 'exceptions.UnicodeError'>: String parameters to be sent over D-Bus must be valid UTF-8 2009/04/28 02:02:47 :: Setting false IP... 2009/04/28 02:02:47 :: Stopping wpa_supplicant 2009/04/28 02:02:47 :: Flushing the routing table... 2009/04/28 02:02:47 :: Putting interface up... 2009/04/28 02:02:47 :: Generating psk... 2009/04/28 02:02:47 :: Attempting to authenticate... 2009/04/28 02:02:49 :: Running DHCP 2009/04/28 02:02:49 :: Internet Systems Consortium DHCP Client V3.1.1-Gentoo 2009/04/28 02:02:49 :: Copyright 2004-2008 Internet Systems Consortium. 2009/04/28 02:02:49 :: All rights reserved. 2009/04/28 02:02:49 :: For info, please visit http://www.isc.org/sw/dhcp/ 2009/04/28 02:02:49 :: 2009/04/28 02:02:49 :: wmaster0: unknown hardware address type 801
Alright, do you have any non-ASCII characters involved? (essid, passphrase, ?? )
No, both the ESSID and the WPA2 passphrase contains only ascii chars. Same for domain/hostname.
The problem persists with wicd-1.6.0_alpha3.
Still no luck with net-misc/wicd-1.6.0_beta1.
(In reply to comment #6) > Still no luck with net-misc/wicd-1.6.0_beta1. > Thanks for testing. I have poked upstream and they don't know the answer either. There is something different about your environment that we can't (yet) track down.
btw. I got the same problem on any 1.6.0_xxxx.
I worked with the nice ppl from #wicd. If I use dhcpcd instead of dhclient it works (after a custom fix that has been put into the wicd repo) the wicd devs asked me to file a bug about it here.... i will just update the description...
just to clarify... the custom fix is unrelated to this bug, and was regarding bonding_masters in /sys/class/net killing wicd on startup ...
(In reply to comment #9) > If I use dhcpcd instead of dhclient it works (after a custom fix that has been > put into the wicd repo) Tasslo, Does using dhcpcd fix the issues for you too? (Or do we have to wait for the next release? - that is not clear to me)
if Tasslo does not experience that wicd dies on startup (which he probably didn't or can fix it without the patch), the fix put in the next version is of NO consequence to the dhcp-issue. The "next release fix" simply adds more condition checking that prevents wicd from dying because of the bonding_masters file (wicd expected only dirs in /sys/class/net/) ... please note, if both dhclient and dhcpcd is available wicd chooses dhclient on automatic so one has to set it to dhcpcd manually in the preferences in wicd-client.
Hi Svenne & Jeremy, sorry for answering late, but I was on a trip. Anyway, now I've installed dhcpcd and use that for obtaining an IP address. It works just fine. :-)
(In reply to comment #13) > Hi Svenne & Jeremy, sorry for answering late, but I was on a trip. Anyway, now > I've installed dhcpcd and use that for obtaining an IP address. It works just > fine. :-) Ok, thx for testing. I just added beta2, let me know if there is any additional problems by reopening this bug. Thnaks!
Hi Jeremy, I'm sorry, but 1.6.0_beta2 doesn't work for me at all. It finds my wireless network, but when clicking on "Connect" nothing happens. No GUI activity (no progress bar, no update in the status bar telling me that it tries to connect, ... nothing), and the connection isn't initiated either. The log file only states only something like "trying to connect to MY_ESSID..." but nothing more. Another problem I discovered lately with beta1 (using dhcpcd) was that it wouldn't connect to wired networks automatically. And when connecting via wicd-client it said it tries to connect, but while "obtaining IP address" it would hang. Unfortunately, it did get an IP and the wired network works just fine. It's just that wicd didn't notice it... So for now I'm back to 1.5.9 which just works right.
(In reply to comment #15) > Hi Jeremy, > > I'm sorry, but 1.6.0_beta2 doesn't work for me at all. It finds my wireless > network, but when clicking on "Connect" nothing happens. No GUI activity (no > progress bar, no update in the status bar telling me that it tries to connect, > ... nothing), and the connection isn't initiated either. The log file only > states only something like "trying to connect to MY_ESSID..." but nothing more. Works great for me. You restarted dbus, wicd, & wicd-client after upgrading? > > Another problem I discovered lately with beta1 (using dhcpcd) was that it > wouldn't connect to wired networks automatically. And when connecting via > wicd-client it said it tries to connect, but while "obtaining IP address" it > would hang. Unfortunately, it did get an IP and the wired network works just > fine. It's just that wicd didn't notice it... > > So for now I'm back to 1.5.9 which just works right.
(In reply to comment #16) > Works great for me. You restarted dbus, wicd, & wicd-client after upgrading? No, only wicd and wicd-client, I think. I'll try it later, hopefully this evening and report back.
Hi Jeremy, now I tried beta3 and it works for me as far as I can tell. Thanks for you help.
(In reply to comment #18) > Hi Jeremy, now I tried beta3 and it works for me as far as I can tell. Thanks > for you help. > Great. slipped by for now, resolving.
