FS#21064 - [wicd] breaks with current testing

Attached to Project: Arch Linux
Opened by Andreas (misc) - Monday, 04 October 2010, 18:19 GMT
Last edited by Allan McRae (Allan) - Saturday, 09 October 2010, 10:34 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Isenmann Daniel (ise)
Rémy Oudompheng (remyoudompheng)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After updating to current testing, wicd stopped working. Upon starting the window manager it asks for the root password to communicate with the hardware (something it never did before), then apparently fails.

The daemon itself appears to start fine (or so its boot message suggests). It doesn't connect to my wi-fi though; that is, I can't connect to the internet with current Arch Linux (Windows works fine).

Additional info:
* package versions: current testing, i. e. wicd-1.7.0-5-any, python-3.1.2-2-x86_64, python2...
* some logs when trying to start wicd tools from the console


Steps to reproduce:
Update, restart...
   log (2.9 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 09 October 2010, 10:34 GMT
Reason for closing:  Fixed
Comment by Ionut Biru (wonder) - Monday, 04 October 2010, 18:38 GMT
seems that wicd-daemon doesn't want to start
Comment by Andreas (misc) - Monday, 04 October 2010, 18:48 GMT
Here's wicd.log (the error message was there repeatedly) and the output of pacman -Q, if it helps.
   wicd.log (2.3 KiB)
   pacmanQ (22.1 KiB)
Comment by Ionut Biru (wonder) - Monday, 04 October 2010, 18:52 GMT
this is a bug in wicd:

https://bugs.launchpad.net/wicd/+bug/602825
Comment by Guillermo Garcia (ahioros) - Tuesday, 05 October 2010, 18:58 GMT
it's true wicd doesnt start!
Comment by Rémy Oudompheng (remyoudompheng) - Tuesday, 05 October 2010, 20:20 GMT
A tentative patch, I don't have an account on Launchpad.
   wicd-no-deepcopy.patch (1.9 KiB)
Comment by Andreas (misc) - Wednesday, 06 October 2010, 11:12 GMT
Doesn't work for me, I'm afraid.

Upon first starting the patched wicd wicd-client actually opened, but appeared stuck at "closing open connections" (although none were open).

Then I uninstalled wicd, rebooted and reinstalled it. Now it asks for the root password like before the patch and wicd-client again refuses to start.

wicd-client console output and the contents of wicd.log are attached.
   console-wicdlog (3.3 KiB)
Comment by Chris (greyhat.goon) - Thursday, 07 October 2010, 04:06 GMT
Seems like wicd is not really starting.

[campbell@sherpa ~]$ sudo /etc/rc.d/wicd restart
:: Stopping wicd Daemon [DONE]
:: Starting wicd Daemon [DONE]
[campbell@sherpa ~]$ ps -elf | grep wicd
0 S campbell 7946 7037 0 80 0 - 2031 pipe_w 20:59 pts/1 00:00:00 grep wicd
[campbell@sherpa ~]$ wicd-client
Has notifications support True
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Wicd daemon is shutting down!
displaytray True
Done loading.
Comment by Allan McRae (Allan) - Thursday, 07 October 2010, 06:09 GMT
Report of patch working in gentoo tracker: http://bugs.gentoo.org/show_bug.cgi?id=333001#c3 :

> but I needed to change the line 38 of wicd/configmanager.py to
> read:
> RawConfigParser.__init__(self, allow_no_value=True)
> allow_no_value parameter was only added on Python 2.7
Comment by Allan McRae (Allan) - Thursday, 07 October 2010, 06:13 GMT
And another patch that reported fixes the issue...

pld-devel-pl@lists.pld-linux.org/msg26678.html"> http://www.mail-archive.com/pld-devel-pl@lists.pld-linux.org/msg26678.html

Although that is ugly!
Comment by Rémy Oudompheng (remyoudompheng) - Friday, 08 October 2010, 11:39 GMT
A patched package was created, with version number 1.7.0-6, which should solve most of the problems.
Comment by Isenmann Daniel (ise) - Friday, 08 October 2010, 11:52 GMT
Thanks Rémy for doing this, didn't have the time to investigate the bug and the solution at the moment.
Comment by Allan McRae (Allan) - Saturday, 09 October 2010, 04:01 GMT
Can we have confirmation of the fix from any of the people who reported the issue?
Comment by Chris (greyhat.goon) - Saturday, 09 October 2010, 04:19 GMT
It's working for me now.
Comment by Thomas (Halcyon22) - Saturday, 09 October 2010, 10:29 GMT
The new wicd works for me too.

Loading...