** Project changed: unity8 => unity8 (Ubuntu)
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Tags added: nm-touch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" dbus signals freeze UI on mobile
devices
To manage noti
** Branch linked: lp:~ci-train-bot/dbus-cpp/dbus-cpp-ubuntu-yakkety-
landing-028
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" d
** Branch linked: lp:~ci-train-bot/dbus-cpp/dbus-cpp-ubuntu-yakkety-
landing-072
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" d
This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-
13ubuntu2
---
qtbase-opensource-src (5.5.1+dfsg-13ubuntu2) xenial; urgency=medium
* Forward-port networking fixes from 5.4 series:
- net-bearer-nm-disconnect-ap-signals7.patch (LP: #1480877)
- qnam-ubuntu-
** Changed in: dbus-cpp (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" dbus s
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Fix Released => Fix Committed
** Also affects: qtbase-opensource-src (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: qtb
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Properties
Patch signals7 (with just the system settings crash fixed) building now
in the PPA.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged
@Selene
Just wanted to confirm that we don't need any more investigation re:
your comment #131 ( I think that may be the largest comment # I've seen
in a LP bug ), as your latest update to bug #1524133 indicated that
you'd isolated the problem to a SIM with an expired data plan?
@Timo
We should
FWIW, I see the weird new behavior on every test with wifi enabled, even
when the screen is on and the phone is actively doing something. For
example, while playing music:
http://people.canonical.com/~platform-qa/power-
results/2015-12-08_09:19:36-krillin-196-power_usage_music/graph.png
... vers
tvoss: The raw data is available. Simply remove "graph.png" from the
URL and it'll give you a directory with all sorts of logs.
The green-shaded section is the active measurement period used for
statistics. The red-shaded portions indicate where USB was connected.
Everything else is unplugged.
fyi: requestUpdate is called by the qnetworkconfigurationmanager, when
updateConfigurations() gets called.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access poi
@Tony
1) requestUpdate() should be left in, as the backend needs to tell other parts
when the update request has been completed. I have tested this, so it does
compile. In further testing, it does not look like any clients are requesting
updates, so the increased power consumption is coming fro
So the latest changes in Lorn's signals6 patch can be summarized as:
1) remove QNetworkManagerEngine::requestUpdate (), which is a public
method which can trigger a WiFi scan request to NM.
This method doesn't appear to be called internally by the bearer plugin,
so if we think extra WiFi scans ar
The interdiff from signals5 to signals6:
http://paste.ubuntu.com/13858649/ - removal of code and one-liner to fix
the system-settings.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/
qtbase 5.4.1+dfsg-2ubuntu11~vivid2 is ready for testing at
https://requests.ci-train.ubuntu.com/#/ticket/761 with Lorn's net-
bearer-nm-disconnect-ap-signals6.patch from bug #1480877 that includes a
fix for both u-s-s crasher bug #1523975 and a potential fix to too many
wifi scanning updates bug #1
Thanks for the graphs. One thing that stands out is the time that the
system stays active when occasionally waking up from deep sleep (right
hand side of the graph).
Do you have the raw data producing those graphs handy?
Thanks,
Thomas
On Wed, Dec 9, 2015 at 1:23 AM, Selene Scriven
wrote:
> I
patch #6 fixes crash in system-settings (#1523975) and removes wifi
scanning updates, which could potentially drain the battery (#1524133)
** Patch added: "net-bearer-nm-disconnect-ap-signals6.patch"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1480877/+attachment/4531735/+f
I created bug 1524133 to track the issues I'm seeing. I don't know if
it's related to this bug, but so far it looks probable.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Is it possible that this fix might cause a phone to wake up more often,
or to stay awake longer? I'm seeing weird idle power behavior ever
since this fix landed in krillin rc-proposed 196.
Before: ~9 mA
http://people.canonical.com/~platform-qa/power-results/2015-12-08_03:19:30-krillin-195-power_u
Just a quick update to mention that the change to the NM bearer plugin
seems to have caused a regression when qtbase is installed from the PPA
onto a desktop ( for UI development work ).
To reproduce, the overlay PPA needs to be added as a software source,
then ubuntu-system-settings installed/upg
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesCha
This bug was fixed in the package dbus-cpp 4.3.0+15.04.20151126-0ubuntu1
in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
phone-overlay
---
dbus-cpp (4.3.0+15.04.20151126-0ubuntu1) vivid; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ Thomas Voß
This bug was fixed in the package location-service
2.1+15.04.20151202.1-0ubuntu1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay
---
location-service (2.1+15.04.20151202.1-0ubuntu1) vivid; urgency=medium
* Ensure that event connections are clean
The associated version for the dbus-cpp in silo-026 is:
4.3.0+15.04.20151126-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChang
The fix has landed in silo-026, as part of location-services version:
2.1+15.04.20151202.1-0ubuntu1
** Changed in: location-service (Ubuntu RTM)
Status: In Progress => Fix Committed
** No longer affects: sync-monitor (Ubuntu RTM)
** No longer affects: maliit-framework (Ubuntu RTM)
** No
The latest version of the patch is now in a silo-026, included as part
of a new qtbase version 5.4.1+dfsg-2ubuntu11~vivid1.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: sync-monitor (Ubuntu RTM)
Status: New => Incomplete
--
You
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww50-2015
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged
@Timo
As previously mentioned, I'd like to get this change out as a hot-fix,
and then do proper evaluation of the new connectivity API based plugin
with the goal to land it as part of OTA9.
@Lorn
I'll take a look at that the line you mentioned, however we need to draw
the line at some point and
Not related to the bug at hand directly, but applying the signals5.patch on top
of Qt 5.5.1 caused a crash to always happen on Unity8 startup:
/usr/bin/unity8:11:/usr/lib/arm-linux-gnueabihf/qt5/plugins/bearer/libqnmbearer.so+7c7c:/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5.5.1+1e4f5a:[stack..341
@Tony I suppose that if statement in
QNetworkManagerEngine::requestUpdate() could also be removed, leaving
the last line only, since we do not do anything with uknown AP's
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubu
Ver 5 in 026 now too (still building), together with the gles
counterpart packagae.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged
Note, I've also pushed a new version based on your latest patch to my
PPA if anyone's interested in testing before it lands in silo-026:
https://launchpad.net/~awe/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to db
@Lorn
Thanks for the update.
I usually do all my testing on rc-proposed, as it's latest and greatest.
I wasn't aware of the "ubuntu-developer" channel. I've tested on rc-
proposed/bq-aquaris.en ( #188 ) with the full set of packages from
silo-026, and everything seemed good to me.
Thar said, I'
@Tony, currently I am on stable/ubuntu-developer. Previously I was
testing on stable/ubuntu. I was on rc-proposed for quite a while, but it
seemed to have only a few scopes, and not the twitter scope which I
wanted to try out.
My updated patch removes actions on device added and removed calls. Mos
The version 4 of the patch (from comment #104) is in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-026
at the moment.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/
@Lorn
Can you add some details regarding what image channel you actually used
and device for testing? rc-proposed is probably the best base for you
to use.
The "GetAll" behavior you're describing is similar to what I was seeing
with the AccessPoint objects. The code would see a "PropertiesChang
I changed my phones image channel, tested (with a few specific test apps
I have for QNAM & friends) that new patch and didn't see any thing too
wrong.
Although I am seeing heaps of GetAll calls that do not need to happen
(even for non nm managed interfaces - rmnet). Attached patch
simplifies/optim
Here's my updated patch, the only difference is that it includes a
DBusConnection disconnect() call in the destructor for
QNetworkManagerInterfaceDeviceModem(), which I'd punted on for
expediency while testing earlier this week.
If doesn't include the IPv6 related fix, as this was fixed in NM
alre
@Tony, small stutters when transitioning from wifi to mobile. I don't
see stutters when scanning anymore. And the stutters I do see when
transitioning from wifi to mobile seem better (presumably because less
dbus signal watchers are registered now for all the traffic that happens
on a switch?).
@Mike
Small stutters when transitioning from mobile to WiFi or visa versa, or
stutters when scanning. The fixes to location-services and Qt both are
applicable to the latter case only...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
Here's a followup on living with silo 26 (pre-comment 97, so an earlier
version, but I doubt it matters for testing?) and Tony's libqt5network5.
I tested this morning (so a full day of the phone living on this code)
and it was slightly worse -- small stutters instead of tiny ones. But
still a vas
@Lorn
Did you see this recently? If so, what device and image?
As I mentioned, the mobile connection on touch doesn't support IPv6
connections.There was a bug in NM that falsely reported that a
default IPv6 route was available, but this was fixed awhile back.
Please see bug #1444162 for deta
@Tony
I noticed this on touch.
The problem was that the ConnectionActive was returning true for mobile data
ipv6 default route when wifi had the actual default route, so it would never
get updated when wifi became default.
--
You received this bug notification because you are a member of Ubuntu
@Lorn
Thanks for the updated patch.
The only significant difference besides the DeviceModem destructor fix
was the change you mentioned about default routes. Is there a touch-
specific bug that this fixes? On our system, the modem connection will
never be IPv6, whereas it is possible to get a
Silo 26 is now complete.
On Mon, Nov 23, 2015 at 4:47 PM, Thomas Voß wrote:
> Quick update on silo 26: I'm rebuilding location-service to account
> for a recent landing.
> The one blocking issue is mediascanner2, which requires a rebuild,
> too. It is however enabled for dual-landing
> to both vi
Quick update on silo 26: I'm rebuilding location-service to account
for a recent landing.
The one blocking issue is mediascanner2, which requires a rebuild,
too. It is however enabled for dual-landing
to both vivid and xenial, and we cannot easily do a vivid+o landing
with it right now. I'm working
I tested silo 26 + libqt5network5 from Tony's PPA and did my normal
routine of walking out of range of my home network.
It seems much better. dbus-daemon CPU usage is down (only ~30% for a
few seconds after initial switch to 3G and ~15% during scans after).
But more importantly, stuttering is mu
I agree, since nothing controls the connections through QtBearer (and
the platform doesn't want that), and AP lists are not allowed in
contained apps, it makes sense to simply remove them.
I've fixed up that patch in regards to d'tor disconnects, removed some
redundant code.
And since it was a sm
Here's a new version of the patch with all the access-point related
signals removed.
It makes no sense for any of this logic to be present in our system, as
none of our code attempts to control the network configuration via
Bearer Mgmt. With this patch, the plugin will never receive any NM
access
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => High
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification
I grabbed your patch and incorporated most of it into my latest patch (
I left out a few of the disconnect calls for some of the other NM
interfaces not directly involved in the match rules problem ), however
it failed to build...
While trying to just pull in the pieces and resolve the conflicts w
Sorry, thought I'd include more.
2nd patch that obsoletes my previous patch includes disconnecting from
system dbus when objects get deleted.
** Patch added: "nmbearer-fix-duplicates2.diff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1480877/+attachment/4521679/+files/nmbea
This patch fixes duplicate entries of access points. Which contributes
to but may not totally fix this bug.
** Patch added: "nmbearer-fix-duplicates.diff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1480877/+attachment/4521638/+files/nmbearer-fix-duplicates.diff
--
You rec
You are correct in that GetAll gets called twice for each accesspoint.
I can see that by adding qDebug's and disable/enable wifi
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/148087
nmRegistered will only get called from the connection signal/slot when
networkmanager daemon if and when gets registered on the dbus. If it is
already registered, it will get called from that invokeMethod.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
Note, QNetworkManagerEngine::setupConfigurations() is also suspect as it
can get called from a couple of places and has a loops over the current
devices and calls deviceAdded().
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp
Some more details:
- the version of the qtbase package in touch atm is: 5.4.1+dfsg-
2ubuntu10
- I checked and didn't see significant differences in the networkmanager
bearer plugin when comparing against 5.5.1, and 5.6.
- That said, there's been quite a few changes in the QDBus code,
specifical
Actually, the only time Qt's QNetworkManagerInterfaceAccessPoint does a
GetAll is in the QNetworkManagerInterfaceAccessPoint c'tor. But that is
in the upstream version.
And the current ubuntu version (at least the one I am seeing) does not
do GetAll at all.
--
You received this bug notification
hmmm... I just noticed/remembered that upstream Qt networkmanager plugin
has been updated, which should perform a bit better as it has had some
refactoring/rewriting done. It is slightly more sane.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8
upstart job, I'm getting a lot more detail without having to further
modify the code.
I'm seeing "Adding rule" log statements produced by
QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so
sounds like my previous
Just a quick update on my debugging.
I've verified that the NM bearer plugin's qnetworkmanagerengine class is
receiving the 'AccessPointRemoved', is matching them correctly in it's
saved list, and is called delete on the
QNetworkManagerInterfaceAccessPoint instance. The associated destructor
is c
I've extracted Lorn's connectivity-api draft commit and made it self-
compiling:
https://code.launchpad.net/~timo-jyrinki/+junk/connectivity-api-bearer
You can either compile it yourself on the device or get this build for
vivid/rc-proposed: https://launchpad.net/~ci-train-ppa-
service/+archive/u
The generic bearer plugin is brain dead, especially when it comes to
knowing when it's actually connected or not.
Although connectivity-api also suffers from blocking dbus calls, I feel
the connectivity-api backend is the right way to go for bearer & QNAM
right now. In the least, it will lessen th
** Changed in: location-service (Ubuntu RTM)
Status: Triaged => In Progress
** Changed in: location-service (Ubuntu RTM)
Assignee: Scott Sweeny (ssweeny) => Thomas Voß (thomas-voss)
** Branch linked: lp:~thomas-voss/location-service/fix-match-rule-leak
** Also affects: dbus-cpp (Ubun
** No longer affects: location-service (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" dbus signals freeze UI on
Unfortunately, the effect on the UI is still the same.
3-4 seconds UI freezes while dbus-daemon is spammed with
PropertiesChanged signals
Network-manager installed:
0.9.10.0-4ubuntu15.1.8
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
This bug was fixed in the package network-manager 0.9.10.0-4ubuntu15.1.8
in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
phone-overlay
---
network-manager (0.9.10.0-4ubuntu15.1.8) vivid; urgency=medium
* d/p/0002-wifi-cull-the-scan-list-before-signalling-Scan
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Pro
** Branch linked: lp:~phablet-team/network-manager/lp1480877-wifi-rm-
dup-scan-signals-vivid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "
This bug was fixed in the package network-manager - 1.0.4-0ubuntu4
---
network-manager (1.0.4-0ubuntu4) wily; urgency=medium
[ Mathieu Trudel-Lapierre ]
* d/p/0001-wwan-add-support-for-using-oFono-as-a-modem-manager.patch:
Pre-initialize reason for ofono state changes to NULL;
** Changed in: network-manager (Ubuntu RTM)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Prope
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Propert
** Tags added: hotfix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" dbus signals freeze UI on mobile
devices
To manag
Thanks for that note,
I was just wondering how it could work with 1-2mins scan interval :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Pr
Note, one other observation noticed this week. If the HERE Maps
application is running and WiFi is enabled, it triggers scans every
4-5s.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchp
I just tried Tony's lp:~phablet-team/network-manager/lp1480877-wifi-rm-
dup-scan-signals branch and did the same thing I've done before to
trigger this bug: walk around my neighborhood with Terminal open,
running top.
To be fair, I was testing rc-proposed tip + Tony's branch, whereas I
previously
** Also affects: indicator-network (Ubuntu RTM)
Importance: Undecided
Status: New
** No longer affects: indicator-network (Ubuntu RTM)
** Also affects: network-manager (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu RTM)
Status: Ne
** Branch linked: lp:~phablet-team/network-manager/lp1480877-wifi-rm-
dup-scan-signals
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Proper
** Also affects: location-service (Ubuntu)
Importance: Undecided
Status: New
** Changed in: location-service (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are
82 matches
Mail list logo
