ad-hoc window does not close

Bug #387246 reported by François Rey
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
wicd
Fix Released
Low
Dan O'Reilly

Bug Description

Environment: arch linux 64 bit, kde 4.2.3, package extra/wicd 1.6.0-2

I can't create an ad-how network for the simple reason that the ad-hoc network creation window does not act upon pressing OK. Cancel button works only if pressed first (does not work after pressing OK). The only way to close the window is to press the window X button.

Here's my wicd.log after closing the window twice with the X button.

2009/06/15 11:12:31 :: ---------------------------
2009/06/15 11:12:31 :: wicd initializing...
2009/06/15 11:12:31 :: ---------------------------
2009/06/15 11:12:31 :: wicd is version 1.6.0 410
2009/06/15 11:12:31 :: setting backend to external
2009/06/15 11:12:31 :: trying to load backend external
2009/06/15 11:12:31 :: successfully loaded backend external
2009/06/15 11:12:31 :: trying to load backend external
2009/06/15 11:12:31 :: successfully loaded backend external
2009/06/15 11:12:31 :: Automatically detected wireless interface wlan0
2009/06/15 11:12:31 :: setting wireless interface wlan0
2009/06/15 11:12:31 :: automatically detected wired interface eth0
2009/06/15 11:12:31 :: setting wired interface eth0
2009/06/15 11:12:31 :: setting wpa driver wext
2009/06/15 11:12:31 :: setting use global dns to False
2009/06/15 11:12:31 :: setting global dns
2009/06/15 11:12:31 :: global dns servers are None None None
2009/06/15 11:12:31 :: domain is None
2009/06/15 11:12:31 :: search domain is None
2009/06/15 11:12:31 :: setting automatically reconnect when connection drops True
2009/06/15 11:12:31 :: Setting dhcp client to 0
2009/06/15 11:12:31 :: Wireless configuration file found...
2009/06/15 11:12:31 :: Wired configuration file found...
2009/06/15 11:12:31 :: chmoding configuration files 0600...
2009/06/15 11:12:31 :: chowning configuration files root:root...
2009/06/15 11:12:31 :: Using wireless interface...wlan0
2009/06/15 11:12:31 :: Using wired interface...eth0
2009/06/15 12:35:36 :: Creating ad-hoc network
2009/06/15 12:35:36 :: Stopping dhcp client and wpa_supplicant
2009/06/15 12:38:12 :: Creating ad-hoc network
2009/06/15 12:38:12 :: Stopping dhcp client and wpa_supplicant

I then enabled debug mode in the gui and got the following additional entries:

2009/06/15 12:39:17 :: trying to load backend ioctl
2009/06/15 12:39:17 :: WARNING: python-iwscan not found, falling back to using iwlist scan.
2009/06/15 12:39:17 :: WARNING: python-wpactrl not found, falling back to using wpa_cli.
2009/06/15 12:39:17 :: trying to load backend external
2009/06/15 12:39:26 :: setting use global dns to 0
2009/06/15 12:39:26 :: setting global dns
2009/06/15 12:39:26 :: global dns servers are
2009/06/15 12:39:26 :: domain is
2009/06/15 12:39:26 :: search domain is
2009/06/15 12:39:26 :: setting wireless interface wlan0
2009/06/15 12:39:26 :: setting wired interface eth0
2009/06/15 12:39:26 :: setting wpa driver wext
2009/06/15 12:39:26 :: setting automatically reconnect when connection drops 1
2009/06/15 12:39:26 :: setting backend to external
2009/06/15 12:39:26 :: Setting dhcp client to 0
2009/06/15 12:39:26 :: ifconfig eth0
2009/06/15 12:39:30 :: ifconfig eth0
2009/06/15 12:39:31 :: Creating ad-hoc network
2009/06/15 12:39:31 :: Stopping dhcp client and wpa_supplicant
2009/06/15 12:39:34 :: ifconfig eth0
2009/06/15 12:39:38 :: ifconfig eth0
2009/06/15 12:39:42 :: ifconfig eth0
2009/06/15 12:39:46 :: ifconfig eth0
2009/06/15 12:39:50 :: ifconfig eth0
2009/06/15 12:39:54 :: ifconfig eth0
2009/06/15 12:39:58 :: ifconfig eth0
2009/06/15 12:40:02 :: ifconfig eth0

Revision history for this message
Adam Blackburn (adamblackburn) wrote :

Can you grab the output from wicd-client when this occurs? I suspect that's what's crashing.

Revision history for this message
François Rey (fmjrey) wrote :

There, you can indeed see interesting stuf, although not sure what to do about it:

[francois@mocha wicd]$ python wicd-client.py
Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Connected.
Done loading.
/usr/lib/python2.6/site-packages/wicd/gui.py:151: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  self.wTree = gtk.glade.XML(gladefile)
refreshing...
ESSID : service
ESSID : WANADOO-691A
ESSID : Livebox-3899
ESSID : NEUF_FEDC
Starting the Ad-Hoc Network Creation Process...
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 1033, in CreateAdHocNetwork
    self.wifi.CreateAdHocNetwork(essid, channel, ip, enctype, key, encused)
  File "/usr/lib/python2.6/site-packages/wicd/networking.py", line 705, in CreateAdHocNetwork
    BACKEND.ReleaseDHCP()
AttributeError: 'module' object has no attribute 'ReleaseDHCP'

Revision history for this message
François Rey (fmjrey) wrote :

wicd-curses produce the same error btw, output below. I'm not going to be available for a few days so I hope I gave enough information to get this fixed...

DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
  File "/usr/lib/wicd/wicd-curses.py", line 89, in wrapper
    return func(*args, **kargs)
  File "/usr/lib/wicd/wicd-curses.py", line 928, in update_ui
    self.handle_keys(keys)
  File "/usr/lib/wicd/wicd-curses.py", line 889, in handle_keys
    data[4], False)
  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 1033, in CreateAdHocNetwork
    self.wifi.CreateAdHocNetwork(essid, channel, ip, enctype, key, encused)
  File "/usr/lib/python2.6/site-packages/wicd/networking.py", line 705, in CreateAdHocNetwork
    BACKEND.ReleaseDHCP()
AttributeError: 'module' object has no attribute 'ReleaseDHCP'

Revision history for this message
Adam Blackburn (adamblackburn) wrote :

I can reproduce this.

Changed in wicd:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
François Rey (fmjrey) wrote :

I'm back. Is there any chance you can fix this silly bug? Should be an easy one....

Andrew Psaltis (nacl)
Changed in wicd:
milestone: none → 1.6.2
Dan O'Reilly (oreilldf)
Changed in wicd:
assignee: nobody → Dan O'Reilly (oreilldf)
status: Confirmed → In Progress
Dan O'Reilly (oreilldf)
Changed in wicd:
status: In Progress → Fix Committed
Dan O'Reilly (oreilldf)
Changed in wicd:
status: Fix Committed → Fix Released
Revision history for this message
Praveen Arimbrathodiyil (pravi-a) wrote :

I have hit the same bug. I hope 1.6.2 fixes it. Debian does not have 1.6.2 in its repositories yet. I'm downloading the sources now.

Revision history for this message
Praveen Arimbrathodiyil (pravi-a) wrote :

I built 1.6.2 and this error does not occur anymore. But I don't see the ad-hoc network listed in iwlist scan, may be another bug.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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