It seems Today scope sometimes behaves...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1558840
Title:
Update downloads hang when connection changes
Status
Public bug reported:
The accelerometer seems to be running at the fastest rate possible -
200Mhz, and thus effecting battery life when it is not needed.
This rate should only be used for apps and games requiring a high amount of
accel precision.
Normal use for orientation/rotation changes in the
Dug into system-update and it seems it does not use QNetwork to
download, but some python script (system-image)
com.canonical.SystemImage so resuming the download may or may not work.
IN my testing it seems to work sometimes, but other times, it will stop
with an installation error.
--
You recei
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Lorn Potter (lorn-potter)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1545
Does not need to be wrong password, it gives that 'Network error -
please retry' and then shows the 2 step verification entry, when giving
correct password.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntuone-credentials
I made a simple test app that uses QNetworkRequest, and I am not seeing
duplicated finished signals being called when there are no errors.
If I use a non existent url, I am seeing duplicated
QNetworkAccessManager::finished signals being called, but no duplicated
signals from QNetworkReply.
--
Yo
ok. it seems the last qnam patch does this. Need to remember why I added that
one offending line.
Will test against the bug at #1552546
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://
Patch for fixing this.
Partially reverts qnam-ubuntu-fix6.patch
** Patch added: "fix-duplicate-qnam-finished.patch"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1564142/+attachment/4627185/+files/fix-duplicate-qnam-finished.patch
--
You received this bug notification
Patch attached to https://bugs.launchpad.net/bugs/1564142
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntuone-credentials in
Ubuntu.
https://bugs.launchpad.net/bugs/1552546
Title:
Wrong hints showing when signing in U
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1564142
Title:
Multiple calls t
Public bug reported:
Using Nexus 4, Ubuntu 15.04 (r330) (rc-proposed)
The bearer plugin that uses connectivity-api used to work (ubuntu touch) back
in November :
https://codereview.qt-project.org/#/c/140752/
It still compiles, but now I get:
2016-01-06T13:28:29 (unknown:0) - QObject::connect:
Just tried the qml example found here:
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Connectivity.NetworkingStatus/
Main.qml:27:5: QML Connections: Cannot assign to non-existent property
"onStatusChanged"
shows "Not online" when I am connected.
--
You received this bug notification
For at least the c++ example, it seems the example code connect call
should be at least:
QObject::connect(ns.data(),
&NetworkingStatus::statusChanged,
[=](NetworkingStatus::Status value)
--
You received this bug notification because you are a member
Is there any reason to keep both connections active at the same time?
Obviously it needs to be able to connect to mobile data when wifi is
connected for HERE/agps, but I think it just needs to download satellite
data once (I could be wrong it might need to keep downloading this data)
--
You rece
I tested landing-032 and system-settings at least does not hang at
'checking for updates' when on mobile data (it now checks and when it
completes says 'connect to the internet to check for updates')
landing-032 contains needed fixes in QtNetworkAccessManager (including this
bug), and would be p
This seems to be working now as expected (usinglanding-032) without the
'connect to the internet to check for updates'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net
Seems this did not totally fix this, it will still hang at 'checking' if
I switch off wifi and then quickly check for updates, but will work if I
press back and then check again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
ok. I thought it was fixed, but as I have investigated it further in
qnetworkaccessmanager, I was somehow fooled and that landing does not
fix this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubun
I believe I have fixed this against landing-032, patch attached
It needs more testing, including upstream autotests.
** Patch added: "qnam-ubuntu-fix.diff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1528886/+attachment/4548354/+files/qnam-ubuntu-fix.diff
--
You
1) QNAM was only being signalled when the online state of nm changed. Since
mobile data remains online when wifi connects, the online state never changes
when the default route moves to wifi. Thus QNAM/QNetworkRequest was not
following the correct configuration/session. The session would never s
seems #2 in comment #34 still is not fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886
Title:
Checking for updates never finishes
Status in Cano
I'll make a task for myself to upstream that to qtsystems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536669
Title:
"BottomEdge" component does not support automatic mou
-opensource-src (Ubuntu)
Assignee: (unassigned) => Lorn Potter (lorn-potter)
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensour
What are the steps to reproduce this?
I tried several times switching system language English->Spanish (reboot) and
then back to English (reboot) and store scope did the correct thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Also affects: platform-api (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1569619
Title:
Need support for Pres
There can be many ways captive portals work and it is tricky being able
to support the different ways of detecting this.
I've seen some offer redirects, but others offer different status codes
to indicate the captive portal, and not all captive portals act properly
once things get returned.
I wou
LGTM, just a few style changes needed for upstream. Updated upstream
with patchset 24
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536669
Title:
"BottomEdge" component doe
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
There is a manual test app included with qtsysteminfo called sysinfo-
tester. You have to manually build this.
I can go though this on the phone, see what is missing, wrong, etc. and
fix it up.
It tries a variety of ways to determine different values..
--
You received this bug notification beca
Since it takes quite a bit of time to get a satellite fix, but it does
get one eventually (nexus 4 here), we can probably assume that it is
agps that is not working.
In the location log, I can getting errors such as:
E1123 16:30:46.685298 1232 android_hardware_abstraction_layer.cpp:157] Error
do
@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
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
@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
@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
Touch seeded packages, which is subscribed to qtbase
I can confirm on ubuntu touch that FaceUp and FaceDown are not being
handled or signaled when they should be (qtubuntu-sensors orientation
does not even handle it)
As well, there is no implementation for AmbientLight in qtubuntu-
sensors.
--
You received this bug notification because you are a m
quick patch to fix this.
** Patch added: "nmbearer-system-settings-fix.diff"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1523975/+attachment/4531606/+files/nmbearer-system-settings-fix.diff
--
You received this bug notification because you are a member of Ubuntu
Touc
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
@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
fyi: requestUpdate is called by the qnetworkconfigurationmanager, when
updateConfigurations() gets called.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/148087
just a note, some of the missing values in deviceinfo can be gotten from
hybris properties, such as in ubuntu-system-settings
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.lau
There are still a few API changes coming. I will make sure it compiles
with 5.4 as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1525879
Title:
Integrate
I don't agree that it makes sense to disable one input method if another
is available. Make it a user configurable option to use one or the
other, but do not disable using both.
I have a touchscreen desktop with second screen. I want both mouse and
touchscreen available. I use both at the same tim
In that case, yes I agree.
If it means I can only use one or the other then no.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1525979
Title:
Touchscreen in
I tried a working connectivity-api bearer plugin (verified with
unconfined test app) with the attached example app, and I still got app
armor errors:
Syslog> Jan 21 06:55:34 ubuntu-phablet dbus[1809]: apparmor="DENIED"
operation="dbus_method_call" bus="session"
path="/com/ubuntu/connectivity1/Net
After adding 'connectivity' to the manifest, it is working with
connectivity-api plugin
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1404188
Title:
QNet
2nd patch here that I am fairly certain fixes this in QNAM as well as in
the nm bearer plugin (making the defaultConfiguration switch when
default connection actually changes). It also optimizes the bearer
plugin a bit.
I have an auto test to be run on a phone to test for this, but I haven't
put i
Just tested fix2 package, does not seem to be working entirely correct yet.
Maybe I missed something in that patch.
It seems to report isOnline is false, quickly followed by true, which seems to
confuse things...
--
You received this bug notification because you are a member of Ubuntu
Touch see
alright, attached is yet another fixup. I used quilt this time, so it
should be about good to go.
The only thing I have not really tested is when only connected to mobile data,
and the connection is bad or weak, and it keeps disconnecting and disconnects
in the middle of an update request.
It se
grrr... At least I can reliably reproduce this:
Start with wifi off and system settings open.
have adb shell or ssh into device.
check for updates
quickly run the command: nmcli radio wifi on
Update should either complete or have an error and should not get stuck
at "checking for updates..."
--
another note to self: /etc/machine-info
** Changed in: qtsystems-opensource-src (Ubuntu)
Assignee: (unassigned) => Lorn Potter (lorn-potter)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
I updated this patch today.
https://codereview.qt-project.org/#/c/121724/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1470700
Title:
QNetworkAccessManager
hmm. might take yet another.. momentarily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1470700
Title:
QNetworkAccessManager hangs when in flight mode
Stat
You do realize this means QNetworkAccessManager most likely will not
work as well.
Any network request, GET, etc... done with Qt runs though
QNetworkConfiguration, which uses the same backend plugin for accessing
network-manager. In which case Qt should probably be configured with the
-no-feature-
Moving this to upstream bug, so I can do the work there.
https://bugreports.qt.io/browse/QTBUG-47482
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1470700
Ti
additional patch:
https://codereview.qt-project.org/#/c/122382/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1470700
Title:
QNetworkAccessManager hangs wh
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 https://bugreports.qt-project.org/br
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
Touch seeded
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
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title
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 not
QNAM uses QtBearer, which means those are handled by the NetworkManager
backend, which I am currently trying to fix up.
There are two ways of diserning online status with QtNetwork.
1) QNetworkConfigurationManager has isOnline() method, this can be done
on the defaultConfiguration().
2) QNetwork
After initial testing, it looks like something like this needs to get used:
url.setPath(path,QUrl::DecodedMode);
As the default mode, QUrl::TolerantMode as well as QUrl::StrictMode
result in the '%3D' getting mangled.
--
You received this bug notification because you are a member of Ubuntu
T
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
Touch seeded packages, which is subscribe
I get his log when running it with Qt 5.3:
type=AVC msg=audit(1414555047.145:83): apparmor="DENIED" operation="create"
profile="com.ubuntu.developer.jdstrand.permy_permy_0.7" pid=3682
comm="qmlscene" family="netlink" sock_type="raw" protocol=0
type=AVC msg=audit(1414555047.155:84): apparmor="DEN
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
Touch seeded packages, which is subscribed to qtbase-opensource
QNAM does indeed block at startup. Unfortunately, the QtBearer backend
needs to perform synchronously in order for QNAM to perform correctly.
Under heavy cpu load, I have seen dbus get quite sluggish.
There is room for optimization in the NetworkManager backend so it uses
property cache with one b
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
Touch seeded packages, which is subscribed to qtubuntu
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
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager
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
To
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
Touch seeded packages, which is subscribed t
This might be similar to this bug
https://bugreports.qt-project.org/browse/QTBUG-39905
which has this fix patch
https://codereview.qt-project.org/#/c/88823/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-openso
The dummy sensor plugin is useless by design, and emulates what an
accelerometer would be like in a desktop computer.
Noted from source code:
// Your average desktop computer doesn't move :)
It could probably be changed to provide some easy sine wave data, but I
am not sure it's worth it.
Als
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 pl
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 incl
I found this which might be the problem:
QUrl AalMediaPlayerControl::unescape(const QMediaContent &media) const
{
if (media.isNull())
return QUrl();
return QUrl::fromPercentEncoding(media.canonicalUrl().toString().toUtf8());
}
I tested this with a small commandline thing, and fro
Public bug reported:
Currently, the networkmanager plugin assumes one modem.
It needs to support dual sim properly.
** Affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Assignee: Lorn Potter (lorn-potter)
Status: New
** Changed in: qtbase-opensource-src (Ubuntu
https://codereview.qt-project.org/98774
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1389084
Title:
networkmanager QtBearer backend does not support dual s
The public API between 5.3 and 5.4 has not changed, so using the 5.4 backend
code in 5.3 will work. It's how I am testing/developing it.
Sorry if this is a mess, the nm backend code was basically never totally
finished and untouched for a long time, except for the port to qt5 (which I had
nothi
This is really odd.
Digging into this, it appears that something in the system other than QtBearer
backend is causing this.
Attached is a dbus-monitor log. The connection never gets fully activated,
which goes along with the log:
Nov 7 16:45:37 ubuntu-phablet NetworkManager[1333]: DNS: plugin d
>From that syslog:
Nov 7 16:02:32 ubuntu-phablet NetworkManager[1371]: Activation (/ril_0)
starting connection '/310410528924256/context1'
Nov 7 16:02:32 ubuntu-phablet NetworkManager[1371]: (/ril_0): device
state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 7 16:02:32 ubun
Attached ofonod log when this happens, from just before disconnect through the
reconnect.
I think the new bearer backend is exposing a bug elsewhere, as this
happens even when there no QNetworkSession opened (which calls to
activate whatever configuration).
Whether it is in NetworkManager, ofono
Using only the generic plugin: rmnet_usb0 seems to be having issues.
(repeated ad-infinitum)
(NetworkConfig::configurationChanged:202) - < default config
>>
(NetworkConfig::configurationChanged:183) - "Unknown" "312537797" "rmnet_usb0"
"UnknownPurpose" "Defined " "Bea
@kgunn72 I think we certainly have moved on to a different bug.
Originally, QNAM was not considering mobile data connection at all,
because the QtBearer was only using generic plug (which does not know
the difference between mobile data and other network interfaces and is
not really usable anyway).
This fix for this bug is part of the patch for
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1357321
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchp
syslog with networkmanager debug.
Starts with being connected. double spaced when it reached disconnection, and
ends with reconnection.
** Attachment added: "nm debug syslog"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1357321/+attachment/4258799/+files/syslog.log
--
As for the original comment. If I delete the cache and reboot,
icons/images do not show up like normal if I start up with 3g
connection.
Looking at the syslog, I noticed the disconnection always starts with
the line:
NetworkManager[1439]: [1415764765.680476] [nm-modem.c:533]
nm_modem_check_conne
weird. I just downloaded/installed the package again, and I can no
longer see that disconnect/reconnect loop.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Well, I did delete the contents of ~/.cache and reboot. But now I do not
have the apps grid.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
[TOPBLOC
According to dbus-monitor, the mode interface keeps failing:
signal sender=:1.8 -> dest=(null destination) serial=1635
path=/org/freedesktop/NetworkManager/Devices/1;
interface=org.freedesktop.NetworkManager.Device; member=StateChanged
uint32 120
uint32 40
uint32 0
signal sender=:1.8 ->
modem interface...
Is there anyway to edit comments?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
[TOPBLOCKER] QNetworkAccessManager doesn't supp
When I use dbus-monitor on NetworkManager, I get this:
signal sender=:1.8 -> dest=(null destination) serial=2845
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager;
member=StateChanged
uint32 20
signal sender=:1.8 -> dest=(null destination) serial=2852
path=/org/f
Ok, I think I see the light now. This is an odd one.
There seems to be two connection settings (within networkmanager) for
the same connection context (even in mako), one being the nm settings
configuration that is actually connected (settings/2), and the other
that is not flagged as active (setti
This fixes that last reconnection issue. There might be a better way,
but with this, the connection is stable again.
https://codereview.qt-project.org/#/c/99818/
But the question remains why NetworkManager has more than one
configuration for a context
--
You received this bug notification b
When I run that test on the phone, it does not crash and passes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
[TOPBLOCKER] QNetworkAccessManager d
Updated upstream. https://codereview.qt-project.org/#/c/99818/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
[TOPBLOCKER] QNetworkAccessManager doe
Here's a patch to skip some of the tests that are failing due to no
valid configurations on the test machines.
** Patch added: "skip failing network tests"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1357321/+attachment/4262629/+files/0001-skip-QtBearer-autotests-when
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 wlan
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 QNA
101 - 197 of 197 matches
Mail list logo
