Cannot create an Ad-Hoc network in 1.6.1

Bug #392352 reported by Andrew Psaltis
This bug report is a duplicate of:  Bug #387246: ad-hoc window does not close. Edit Remove
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wicd
Confirmed
Undecided
Unassigned
wicd (Suse)
New
Undecided
Unassigned

Bug Description

Attempting to create an ad-hoc network, using the default settings used by both wicd-curses and wicd-client results in an exception, the traceback of which is as follows:

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 280, in create_adhoc_network
    False) #chkbox_use_ics.get_active())
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.AttributeError: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/wicd/wicd-daemon.py", line 1039, in CreateAdHocNetwork
    self.wifi.CreateAdHocNetwork(essid, channel, ip, enctype, key, encused)
  File "/usr/lib/python2.6/site-packages/wicd/networking.py", line 722, in CreateAdHocNetwork
    BACKEND.ReleaseDHCP()
AttributeError: 'module' object has no attribute 'ReleaseDHCP'

I am running slackware-current, using rworkman's wicd-1.6.1-i486-2_rlw.txz package.

Revision history for this message
Kai (vovan) wrote :

fixed in 1.6.2

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.