mark as fix release since no activity for long.
** Changed in: savilerow
Status: New = Fix Released
** Changed in: savilerow
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
documenting the landing
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Importance: Undecided = Critical
** Changed in: canonical-devices-system-image
Milestone: None = ww51-2014
** Changed in:
This bug was fixed in the package qtbase-opensource-src - 5.3.0+dfsg-
2ubuntu10~vrtm~5
---
qtbase-opensource-src (5.3.0+dfsg-2ubuntu10~vrtm~5) 14.09; urgency=medium
* Pick up the Qt 5.4 network-manager bearer fixes (LP: #1357321)
-
Start InternetCheckercmd with wifi enabled, with the known wifi router
unpowered or out of range, while connected to mobile data. (will not
work like this when manually enabling/disabling wifi)
It will return something like this:
phablet@ubuntu-phablet:~$ InternetCheckercmd/InternetCheckercmd
This bug was fixed in the package qtbase-opensource-src - 5.3.2+dfsg-
4ubuntu5
---
qtbase-opensource-src (5.3.2+dfsg-4ubuntu5) vivid; urgency=medium
* Rename qt5-qmake-cross-armhf to qt5-qmake-arm-linux-gnueabihf
-- Zoltan Balogh zol...@bakter.hu Thu, 20 Nov 2014 10:33:16 +
So this was also included in the fixing upload:
* Pick up the Qt 5.4 network-manager bearer fixes (LP: #1357321)
- debian/patches/disable-generic-plugin-when-others-available.patch
+ not merged upstream, would need better runtime detection mechanism
-
** Tags removed: lt-blocker lt-category-visible
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager doesn't support roaming on Ubuntu
To manage notifications about
it is tagged ota-1, so it will land, just not in one of the next two
promoted images, which just delays it by two weeks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
@lorn - per ogra's comment, it's still a top-blocker in spirit (folks
were using the title for some reporting visibility)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
Removed from topblocker list
** Summary changed:
- [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
+ QNetworkAccessManager doesn't support roaming on Ubuntu
** Tags removed: touch-2014-11-06
** Tags added: ota-1
--
You received this bug notification because you are a
Has that network-manager fix hit ubuntu-rtm/devel yet? Because without
these qtbearer/qnam patches, I'm still seeing images loading issues.
The problem is not manually disabling the AP, but when moving (roaming)
from one to another, i.e. moving from wlan coverage to 3g coverage, or
from 3g to
I did more testing of the generic plugin, and it's not as bad as I
thought, in that it does signal when interfaces become the default
route.
But my comment still stands that without these patches (in the least,
the patch to QNAM itself is especially needed) the defaultConfiguration
internal to
The last patch is big and seems to fail quite largely on top of 5.3.0 +
the other patches. I haven't tried to look it hard yet to see how much
work the rebasing would be, but if in the end we will want that patch to
fix this bug, rebasing needs to be done for it too.
If interested, I've pushed a
Here'a yet another one. Hopefully only small bug fixes are needed after this.
https://codereview.qt-project.org/#/c/98547/
This one makes mobile data detection really works and uses property
cache instead of making blocking calls for every property call.
The 3 other reviews do not need to be
Unfortunately, QtBearer cannot be totally asynchronous, as QNAM is a
synchronous API.
It does need optimization in regards to amount of blocking calls it
does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just pushed updated build ~test4, refreshing/rebasing from the 5.4
patches and adding Reset-QNAM-s-NetworkConfiguration-when-state-
changes.patch. The patches included currently are:
disable-generic-plugin-when-others-available.patch
Add-better-mobile-connections-to-QtBearer-NetworkMan.patch
This patch https://codereview.qt-project.org/#/c/98115/
and bug bugreports.qt-project.org/browse/QTBUG-40234
will probably effect/fix this bug as well as those other previous fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Forgot to mention, all these patches will go into upstream 5.4, but will
also cleanly apply to 5.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager doesn't support
I now have a mako to test on.
As far as I can tell, those patches did not fix this. At leastnow the
bearer backend is mostly working.
Tested with the soundcloud scope tutorial app :) and one I made testing
QNAM/QNetworkConfiguration and friends.
I think the problem is the bearer backend does
@Timo, did that change in the ppa fix the issue ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager doesn't support roaming on Ubuntu
To manage notifications about
@Omer: At the moment I'd need someone to test the PPA. I may be able to
test it later today myself, but not next week where I don't have a HSDPA
that I could reasonably use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also needed is the update to the networkmanager API version patch.
https://codereview.qt-project.org/#/c/96332/
That patch is now targeted for 5.4, but it is needed for the
networkmanager bearer plugin to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Added that one too. I needed to rebase it for 5.3.0, but it didn't seem
too scary.
So, ~test3 pushed to the PPA. Let's see how the unit tests go (they are
executed as part of the build) as upstream MP has some issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
PPA has now finished building updated 5.3.0+dfsg-2ubuntu10~utopic1~test2
package, please test!
It includes both updated Add-better-mobile-connections-to-QtBearer-
NetworkMan.patch and one-liner patch as copy-pasted from QTBUG-41866.
--
You received this bug notification because you are a member
Just pushed another revision to the first upstream change review. This
fixes the plugin on a desktop using ethernet and/or wifi connections.
As for #2. I can make QtNetwork ignore the generic plugin when others are
present and usable. It is a one line fix.
See
Hey, I noticed this bug on my bug filtering. Test build for the quoted patch
pushed to:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-022/+packages
- armhf build will take around 3h.
apt line on device: deb http://ppa.launchpad.net/ci-train-ppa-
It has built, I'm not sure how useful it is without a fix for 2). Maybe
one could additionally remove
/usr/lib/*/qt5/plugins/bearer/libqgenericbearer.so for testing?
For 2), we should generally not deviate from upstream as a rule and also
because Ubuntu has other Qt 5 users like KDE. So we need
So there are two things that effect this bug.
1) NetworkManager backend is not working with current NetworkManager on
any platform.
The previously mentioned patches fix this. Mostly API changes in
NetworkManager from when I last worked on this bearer plugin.
2) Having the generic backend
I have no way to test this currently, but this change may also help.
The NM backend was missing some mobile connection functionality.
https://codereview.qt-project.org/#/c/96501/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is the generic bearer plugin also being installed? What happens when
that is removed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager doesn't support roaming on
I forgot to mention I noticed this weekend the NetworkManager plugin is not
exactly working well. There is a MR fixing this
https://codereview.qt-project.org/#/c/96332/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looked into the code, it appears that when they were porting the NM
backend to qt5, they never hooked up anything to the StateChanged
signal. ;/ (I originally wrote the NM backend, but was not on the team
that ported it.)
--
You received this bug notification because you are a member of Ubuntu
Great, thanks for looking into it. I'm not very familiar with Qt code,
so I didn't get that far yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager doesn't
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: qtbase (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager doesn't support roaming on Ubuntu
To
Lorn, if you're working on this, could you please assign the bug to
yourself for the qtbase-opensource-src task?
** Package changed: qtbase (Ubuntu) = qtbase-opensource-src (Ubuntu)
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New = Triaged
** Changed in: qtbase-opensource-src
Not sure if I reassigned this properly, but qtubuntu/platform-api
probably should use connectivity-api if that's possible, to know whether
they are online or not. Any other information might need to be added to
the connectivity api.
--
You received this bug notification because you are a member
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) = Lorn Potter (lorn-potter)
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: qtubuntu (Ubuntu)
** Tags removed: touch-2014-10-09
** Tags added: touch-2014-10-23
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I haven't been able to build qtbase with some extra debugging just yet,
it fails to build (segfaults) in sbuild and/or in a PPA; I'm still
waiting for the results of building on my phone. From there, I'll be
able to move forward to figure out why QNetworkAccessManager doesn't
seem to be using the
** Changed in: qtubuntu (Ubuntu)
Status: Confirmed = In Progress
** Changed in: platform-api
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Just ping me if you need anything added to the connectivity-service.
The security team has made it clear that they don't want to allow broad access
to the NM D-Bus API for confined apps. So, the way we do this is by relaying
any necessary information through the properly confined
** Changed in: qtubuntu (Ubuntu)
Assignee: Michael Frey (mfrey) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: platform-api
Assignee: Ricardo Mendoza (ricmm) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: platform-api
Status: New = Confirmed
** Changed in:
changing tag to 10/9, altho from the write above sounds like a longer
term proposition
** Tags removed: touch-2014-10-9
** Tags added: touch-2014-10-09
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@chicken - hope you don't mind me putting back to you, networking not
exactly in our wheelhouse.
** Changed in: qtubuntu (Ubuntu)
Assignee: Michael Zanetti (mzanetti) = Michael Frey (mfrey)
** Tags removed: touch-2014-09-25
** Tags added: touch-2014-10-9
--
You received this bug
Looks to me like QNetworkAccessManager doesn't support roaming, either
because it was built without it being enabled or it's disabled because
it's not detected as being supported; but I can see
QNetworkConfigurationManager doesn't report roaming to be supported as
per the QNetworkAccessManager
** Changed in: qtubuntu (Ubuntu)
Assignee: Michael Zanetti (mzanetti) = Mathieu Trudel-Lapierre
(mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager
** Summary changed:
- scope images do not load in HSDPA or 3G
+ QNetworkAccessManager doesn't support roaming on Ubuntu
** No longer affects: unity8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
if the scopes are confined then we need to change the QPA plugin to use
connectivity-service instead of NM to get the networking status changes.
Well, this doesn't only affect scopes. It also affects apps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
49 matches
Mail list logo
