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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bu
** Project changed: unity8 => unity8 (Ubuntu)
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
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:
Acc
** Tags added: nm-touch
--
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
** 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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChange
** 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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChange
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChanged" db
** 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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Proper
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesCha
@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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access
@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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/b
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Propertie
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
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ß
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
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesC
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww50-2015
--
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' "PropertiesCha
@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 Desktop
Packages, which is subscribed to network-manager in
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesCha
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 Desktop
Packages, which is subscribed to netwo
@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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.
@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
@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 Desktop
Packages, which is subscribed to n
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 Deskto
@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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/14
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 Desktop
Packages, which i
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 Desktop
Packages, which is subscribed to network-mana
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 Desktop
Packages, which is subscr
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
We need only a subset of the NM bearer features so it would be ok to
replace or patch to limit its behavior.
What we need is existing QNAM instances to not fall dead if user is on
3G + wifi and then disables wifi, or alternatively if on 3G and wifi
gets enabled the connections should migrate to wi
That's right, any time QNAM is used it uses the Qt Bearer backend
(unless Qt is configure without bearer). In the case of the network-
manager backend, it calls the blocking dbus calls to get list of
services, and then for every service to get that services properties.
Even for local file:// access
re comment #68 and maliit access networking, from Albert on bug #1515712
> We should figure out why we are even doing any network stuff at all,
as we probably shouldn't be.
It comes from the fact that QtMultimedia uses network transparent
methods to load urls used for audio playing, so even if i
@Lorn
I don't think the blocking DBus calls are the culprit per se, although I
did see a few while looking at the NM backend. The simple issue is
that NM removes AccessPoint DBus objects on a regular basis, the the
signal watches for these objects are not being released...
I'd see your new plug
You might be running into those dbus blocking calls in the network-manager
bearer backend.
The networkmanager bearer plugin currently is using a few blocking dbus calls
to get properties and such.
see this abandoned change here:
https://codereview.qt-project.org/#/c/98090/
This change was abando
The attachment "Initial attempt to patch QNetworkSession to fix match
rules leak" seems to be a patch. If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message per
Here's a first attempt at a patch, which unfortunately doesn't seem to
work...
The general idea is when an AccessPointRemoved signal is received, we
need to ensure that the associated DBus watch is removed. According to
the QDbus documentation, DBusConnection::disconnect() should do this. I
unfo
@Timo
Thanks for the update. I commented on bug #1404188 regarding this bug.
I agree with you that moving to a new backend for the vivid-overlay PPA
is risky. That said, if we keep the networkmanager bug backend, this
bug really needs to be fixed.
What you say about the networkmanager backend i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.l
In parallel there has been some discussions on bug #1404188 about
dropping the usage of network manager backend, even though unlikely in
vivid-overlay unless seen as a bullet proof option.
If you want to try out how that would look like, install the silo 032 on
rc-proposed but _without_ upgrading
** Package changed: unity8 (Ubuntu RTM) => qtbase-opensource-src
(Ubuntu)
** Also affects: unity8
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.l
** Changed in: location-service (Ubuntu RTM)
Status: New => Triaged
--
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" dbu
I just added tasks for the packages mentioned in comment #65.
Some things learned today:
- the sub-component of QNetwork that's most likely the cause is called
Bearer Management. One of it's classes, QNetworkSession includes a
plugin for NetworkManager which creates listeners for new AccessPoin
** Also affects: buteo-syncfw (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: buteo-syncfw (Ubuntu)
** Also affects: buteo-syncfw (Ubuntu RTM)
Importance: Undecided
Status: New
** Also affects: unity8 (Ubuntu RTM)
Importance: Undecided
Status: New
Here's a script that calls dbus-monitor with the correct match rules in
order to catch AccessPointAdded and Removed signals, as well as
PropertiesChanged signals for the Device.Wireless 'AccessPoints'
property.
** Attachment added: "monitor-aps.sh"
https://bugs.launchpad.net/ubuntu-rtm/+source
@taiebot65
I don't think this is related to bug #1462664. This is specifically
related to the number of processes watching individual network-manager
access point objects, and the fact that these processes leak match
rules, so they continue to add match rules to dbus for new access
points, but n
@Pat
We might want to hotfix this once we come to fully understand it( and I
think we're getting close ).
While working with tvoss a fixes to location-services, we realized that
by default, the get-all-match.py script only outputs warnings. While
reviewing a test run from tvoss, I didn't see an
** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => ww02-2016
--
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' "PropertiesCha
Here my feedback from installing silo 10 as per bug #1462664. I have
been walking to town today and did not notice any lag for the time i was
in town. Normally i am experiencing some hangs of more than 1 min before
i can get a working phone. Today i checked repeatedly my phone and it
did wake up li
If it is linked to #1462664 Looks like it could be fixed I will try
upgrading my system following the fix proposed in the bug and see if it
solves the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
htt
@Michael
Thanks again for your help with testing this.
1) When the phone disconnects from an AP, the scan interval drops to
it's lowest possible interval ( 20s ), as the goal is re-connecting as
quick as possible. It'll eventually drift back to ~60s.
2) I also get the very brief <= 1s stutter w
** Changed in: location-service (Ubuntu RTM)
Assignee: (unassigned) => Scott Sweeny (ssweeny)
** Changed in: location-service (Ubuntu RTM)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-mana
Here's some test results from me. tl;dr stopping location services
helps a lot, but still tiny UI stuttering.
My routine is to leave my apartment and walk down the street. This
means I go from wifi to 3G. What happens on current images is:
1) As my phone notices that I'm out of wifi range, it
@awe: great progress! well done! :)
I took a few videos to demonstrate the problem on my device
KRILLIN, RC-PROPOSED, R163
network-manager 0.9.10.0-4ubuntu15.1.8
wpa-supplicant
It was really easy to shoot videos at the right time because the problem
happens exactly every 2 mins (which is the sca
Re: the xenial version of dbus, you need to be careful as although I was
able to get it to run on a krillin, it prevented the UI from coming up
on mako. This is why I backported the changes and pushed to my PPA (
1.8.12-1ubuntu5~awe3 ).
https://launchpad.net/~awe/+archive/ubuntu/ppa
@Andrea
I'
> I also began to see the Shutdown menu displayed every so often when
> I let the screen go off, and then woke via the power button.
That specific behavior is bug 1508563, whose fix just landed and will be
in the next rc-proposed. It happened if unity8 was too being too slow
(because the system w
So re-testing with krillin ( rc-proposed, #162 ).
Confirmed that using a patched version of dbus 1.8, the match rule
limits aren't enforced, so each of the loc processes slowly grows its
number of match rules till they cap out at 5000 each.
So, WiFi enabled & connected, with the HERE app running
FYI, to prevent those three processes from respawning, do:
sudo stop ubuntu-location-provider-here-slpgwd
sudo stop ubuntu-location-provider-here-posclientd
sudo stop ubuntu-location-service
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
** Also affects: location-service (Ubuntu RTM)
Importance: Undecided
Status: New
--
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' "Proper
Forgot to add the output of the system match rules for mako. Note at
the time this was run both slpgwd and posclientd both have 616 match
rules. It looks like stopping the location service ( via upstart or the
indicator ) may have cleared the rules for ubuntu-location-servicesd.
** Attachment ad
This script queries GetAllMatchRules and generates output including
warnings about less-optimal DBus match rules.
** Attachment added: "example DBus script for GetAllMatchRules usage"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+attachment/4512384/+files/get-all-matc
One of the frustrating parts about this bug is the incomplete
description, and the fact that it's been nigh impossible to nail down a
set of concrete steps to reproduce...
Also, the bug description contends that NM 'PropertiesChanged' signals
are causing the UI freezes, however we have no idea why
Here's the two patches necessary to enable the GetAllMatchRules method,
as well as the patch that bumped the match rules limit to 5000 (
20_system_conf_limit.patch ).
** Attachment added: "Dbus patches"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+attachment/4512383/
** Changed in: network-manager (Ubuntu RTM)
Status: Fix Released => Incomplete
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubunt
1 - 100 of 166 matches
Mail list logo