One other interesting tidbit. On my krillin, on average there are
roughly ~200 processes running. Looks like almost half (87) of them are
connected to the system bus. You can use the following command to see
how many sockets exist for any dbus processes, and then you need to
figure out which one is the system bus daemon ( usually the one with the
lower PID ):
sudo netstat -nap | grep dbus | grep CONNECTED | awk '{print $8}' | sort
| uniq -c
Note, this compares to 55 processes on my desktop connected to the
system bus.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" dbus signals freeze UI on mobile
devices
Status in Canonical System Image:
Confirmed
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/canonical-devices-system-image/+bug/1480877/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
