Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12223 - wicd-1.5.4-2 update breaks wireless networking

Attached to Project: Arch Linux
Opened by James Munro (xen) - Monday, 24 November 2008, 10:08 GMT
Last edited by Eduardo Romero (kensai) - Friday, 26 December 2008, 02:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eduardo Romero (kensai)
Architecture All
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description: This bug effects both i686 and x86_64. Upon updating to this new version of wicd I am no longer able to connect to wireless networks. It also seems that the file 'networking.py' that should be located in /usr/lib/wicd/ is missing from the package.

Reverting to the previous available version fixes these problems.

The bug seems to be related to this: https://bugs.launchpad.net/wicd/+bug/264447

However, this file quoted above doesn't exist in the 1.5.4-2 package, so I'm unable to test the fix (which is already sorted, as far as I know).
This task depends upon

Closed by  Eduardo Romero (kensai)
Friday, 26 December 2008, 02:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  The original bug is fixed, the reopening bug is not the same as the original, please before asking to reopen make sure it is the same bug.
Comment by Emanuele Rampichini (lele85) - Monday, 24 November 2008, 10:48 GMT
I've the same issue here, solved reverting to the previous version.

Wicd-client with 1.5.4-2 doesn't work anymore.

Here the traceback:

lele85@lele-box ~ $ wicd-client
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 2006, in <module>
setup_dbus()
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 174, in setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files
Comment by Blazej (blasse) - Monday, 24 November 2008, 11:48 GMT
Works fine for me.
Comment by James Munro (xen) - Monday, 24 November 2008, 12:21 GMT
What is your wireless encryption configuration? I have only been able to test on a WPA2 network, as its all I have access to.
Comment by name withheld (Gullible Jones) - Monday, 24 November 2008, 18:53 GMT
Doesn't work fine for me, wicd-client doesn't even start:

Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 2006, in <module>
setup_dbus()
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 174, in setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files
Comment by Christian Galander (igprolin) - Monday, 24 November 2008, 19:41 GMT
Works fine for mee too on my IBM Thinkpad T23 with Gnome 2.24.x
Comment by Archgrue (Archgrue) - Monday, 24 November 2008, 19:48 GMT
I'd like to add, that installation of this latest wicd, on my laptop with previous version running and connected, crashed my system, I was unable to reboot, not even with SysRQ rseiub sequence. Subsequent attempt to install with wifi turned off also crashed the system, but this time I was able to reboot. It seems wicd was installed after all, but does not connect as reported up above.
Comment by Olivier Duclos (oliwer) - Monday, 24 November 2008, 20:30 GMT
I am also unable to connect anymore to my wifi WPA2 network, but I don't see any error message. Switching back to 1.5.3.
Comment by Eduardo Romero (kensai) - Monday, 24 November 2008, 20:47 GMT
Sorry guys for this, I upgraded the package, it should be fixed now, if not report back. Make sure you have eth0 or any network interface commented out in rc.conf before running the wicd daemon.
Comment by Cervesato Andrea (Sawk) - Tuesday, 25 November 2008, 20:58 GMT
delete all wicd's directory and reinstall the package

this solution works for me
Comment by James Munro (xen) - Tuesday, 25 November 2008, 21:17 GMT
The problem is now fixed for me with the updated package, thanks for this! Anyone else?
Comment by James Munro (xen) - Wednesday, 26 November 2008, 11:23 GMT
Actually, it isn't fixed. Problem still exists on 2 machines for me.
Comment by Emanuele Rampichini (lele85) - Wednesday, 26 November 2008, 12:07 GMT
Fixed for me! thanks.
Comment by Eduardo Romero (kensai) - Wednesday, 26 November 2008, 15:50 GMT
Well, the majority said its been fied, xen, can you do what Sawk said? and then report back. Be sure you are following the correct procedure for using wicd.
Comment by Tom (reztho) - Wednesday, 26 November 2008, 18:58 GMT
Check you have this dir:
/usr/lib/python2.5/site-packages/wicd

If you have it, the wicd daemon will not run, so that's why your wicd client refuse to run.
Comment by James Munro (xen) - Monday, 01 December 2008, 20:25 GMT
  • Field changed: Percent Complete (100% → 0%)
This bug is not fixed, the bug I reported is not the same that people are talking about in the comments.
Comment by Eduardo Romero (kensai) - Monday, 01 December 2008, 20:36 GMT
OK, I added the files which were missing again, so what could have been the problem. Is the 1.5.4 version so bad?
Comment by Eduardo Romero (kensai) - Monday, 01 December 2008, 22:40 GMT
Upgraded to wicd 1.5.5 see if it is fixed. make sure you rm -rf /usr/lib/python2.5/site-packages/wicd and rm -rf /usr/lib/python2.6/site-packages/wicd and then upgrade so that all files are new files, then restart dbus and wicd. Oh, and make sure wireless_tools is installed.
Comment by Eduardo Romero (kensai) - Tuesday, 02 December 2008, 14:33 GMT
Also, make sure you have wpa_supplicant installed, other people are seeing and connecting to wireless networks flawlessly.
Comment by name withheld (Gullible Jones) - Tuesday, 02 December 2008, 17:35 GMT
kensai: so far 1.5.5 is only out for i686, not x86_64...
Comment by Eduardo Romero (kensai) - Wednesday, 03 December 2008, 14:26 GMT
OK, it has hit x86_64, please report back.
Comment by James Munro (xen) - Wednesday, 03 December 2008, 14:33 GMT
My problem *seems* to be fixed now, in light of the recent updates. Thanks for the help guys!
Comment by Jared (nitro) - Thursday, 04 December 2008, 04:35 GMT
  • Field changed: Percent Complete (100% → 0%)
I'm having the same problem, even with the latest version of wicd. This is on a brand new install of Arch Linux (installed on 12/02/08), and I _started_ with this version, so it appears that the problem still exists in the current version rather than being an issue caused by upgrading.

I'm running x86_64, and have wicd 1.5.5-1 installed. I can open a new request if preferred, but I'm getting literally the _exact_ same error message as the original poster.
Comment by Jared (nitro) - Thursday, 04 December 2008, 04:56 GMT
Thanks for reopening. One point of clarification: I have the exact same problem described by first _responder_ (Emanuele Rampichini (lele85)), not the original poster. I was looking in the wrong place when posting my previous comment.

If you need any additional info for troubleshooting, please let me know. Also, in case you're wondering:

1. I have wpa_supplicant and wireless_tools installed
2. I restarted dbus after installing wicd
3. Just to be thorough, I restarted my system, but still get the same issue
Comment by name withheld (Gullible Jones) - Thursday, 04 December 2008, 10:28 GMT
FWIW, the dbus problem seems solvable by removing /var/log/wicd and letting wicd recreate it; perhaps that directory has the wrong permissions in the package?
Comment by Eduardo Romero (kensai) - Thursday, 04 December 2008, 13:56 GMT
Well, As I can see the bug is fixed, you just have the problem that one of the posters had, have you tried what Gullible Jones said?
Comment by Jared (nitro) - Thursday, 04 December 2008, 15:34 GMT
I'm unable to test it right now, but I'll give it a try as soon as I get home tonight. The log directory was about the one thing I didn't check. :-)

Will post back my results. Thanks for the suggestion.
Comment by Jared (nitro) - Friday, 05 December 2008, 01:33 GMT
Success! Gullible Jones' suggestion worked perfectly.

For those interested, here are the original permissions of /var/log/wicd after a fresh install:
drwxr-xr-x 2 root root 6 2008-12-02 18:16 wicd

I stopped wicd, removed the directory, and restarted wicd. It was recreated like this:
d-wxrw--wt 2 root root 21 2008-12-04 19:15 wicd

So, an easy solution would probably be to have the installer package initially create the directory with these permissions. Or, conversely, _don't_ create the directory and let wicd do it on initial start.

Anyway, I'm good now. Thanks a bunch for the suggestion.
Comment by name withheld (Gullible Jones) - Tuesday, 16 December 2008, 21:22 GMT
  • Field changed: Percent Complete (100% → 0%)
It's back as of version 1.5.6:

$ wicd-client
\Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 2006, in <module>
setup_dbus()
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 174, in setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files

This time, removing /var/log/wicd does not work. :(
Comment by Eduardo Romero (kensai) - Wednesday, 17 December 2008, 02:19 GMT
Please, don't reopen this again, if the problem is not the one as reported in the bug, the problem he is having is unrelated to this bug, and happens in very rare occasions and gets fixed in occasions as well. I have given up the package, because I realized it is too much of a hassle, and I don't have the possibility to test it to full capacity anymore.

Loading...