[1.463 hangs here



About half the time, mostly with hidden APs NM 1.463 hangs in the same place

_________________________________________
NetworkManagerDbus.c:nm_dbus_get_user_key_for_network

      dev_path = nm_dbus_get_object_path_for_device (dev);
      net_path = nm_dbus_get_object_path_for_network (dev, ap);
      if (dev_path && strlen (dev_path) && net_path && strlen (net_path))
      {
              nm_info ("**** nm_dbus_get_user_key_for_network point 1");
dbus_message_append_args (message, DBUS_TYPE_OBJECT_PATH, &dev_path, DBUS_TYPE_OBJECT_PATH, &net_path, DBUS_TYPE_INT32, &attempt, DBUS_TYPE_BOOLEAN, &new_key, DBUS_TYPE_INVALID); if (dbus_connection_send_with_reply (connection, message, &pcall, INT_MAX) && pcall)
              {
nm_info ("**** nm_dbus_get_user_key_for_network point 2");
                      nm_act_request_ref (req);
nm_act_request_set_stage (req, NM_ACT_STAGE_NEED_USER_KEY); nm_act_request_set_user_key_pending_call (req, pcall); dbus_pending_call_set_notify (pcall, (DBusPendingCallNotifyFunction) nm_dbus_get_user_key_for_network_cb, req, NULL); nm_info ("**** nm_dbus_get_user_key_for_network point 3");
________________________________________
It gets to point 3 but the function nm_dbus_get_user_key_for_network_cb doesn't get called. Mostly NM connects when I boot in range of a broadcasting AP but I have to force just about everything else. When I recompile and restart messagebus, NM, NMD with a script and then start nm-applet from a menu item for convenience. This nolonger works. How to pin down why dbus_pending_call_set_notify is so flacky? My dbus and hal and gtk are up to date with rawhide but I am still running gnome 2.10.

--
Bill Moss
Professor, Mathematical Sciences
Clemson University



--
Bill Moss
Professor, Mathematical Sciences
Clemson University




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]