desktop-packages team mailing list archive

[Tony Espy <1480877@xxxxxxxxxxxxxxxxxx>]

@Andrea

As mentioned on IRC, we still need more information in order to
determine what the real problem(s) are.

I did a little more investigation regarding the DBus events you're
seeing on the session bus.  By default, an upstart bridge is started on
the session bus which forwards all signals from the system bus to the
session bus.   See /usr/share/upstart/sessions/upstart-dbus-system-
bridge.conf for details of this job.

Problem 1:

 * We need some way to quantify "many access points".   Does "many" mean
more than five?  ten?  Again, without a reproducible scenario, we can't
begin to narrow this down...   Taking a look at your first pastebin in
your description, I only see ~40 access points involved which doesn't
seem to be all that many.  I routinely see ~25 in my home office.

 * Do you have a location where this problem always occur?   Does the
problem happen every time you're in this location?  Does the condition
persist until you leave this location?   What happens if you reboot
while at the location?  What happens if you disable Wi-Fi while at this
location?

 * I will attach a script which will dump some information out about
NM's Wi-Fi device, including the number of access points that are
currently visible to NM.   The next time the problem manifests, can you
please run the script and add the output to a comment?

 * This next step may break other things on your system, but it's worth
a try...  If you can reliably reproduce the problem, before entering the
area with the excess of APs, please run the following command as the
phablet user on the phone:

% stop upstart-dbus-system-bridge

 * When you're done testing, please remember to start the bridge (
replace "stop" with "start" ), or reboot the device.

 * Please note the times when the problem occurs and make sure to attach
your syslog.  This will allow me to look at what NM was doing at the
time the problem happened.  If you want, you can reduce the size of the
log by using the following command:

$ grep "NetworkManager" syslog > nm.out

...and attach just the nm.out file.

 * Looking at your syslog from comment #6, I see a couple of notable
things:

   - at some point, you appear to be connecting to a Wi-Fi WPA-
Enterprise network ( eduroam ).  Does this correlate to when you see the
problem?

   - I also note that around 11:24 on Aug 6, your device appears to have
rapidly roamed between a couple of the office APs in Bluefin.   This
could also be a potential source of the problem.

 * Finally, before doing any re-test, can you ensure you have the latest
updates installed?  We just released a new version of NM which fixes a
problem with scanning.  It's probably not related, but you never know...

Problem 2:

Please try to reproduce and file a separate bug for the issue where NM
gets stuck trying to connect to the Windows8.1 AP.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1480877/+subscriptions