"Couldn't load weather data, please try later again!" with Qt 5.5.1

[Timo Jyrinki]

The weather data cannot be seemingly loaded with Qt 5.5.1.

More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting

[Andrew Hayzen (ahayzen)]

This could be due to OpenWeatherMap now requiring an API key as well as TheWeatherChannel. Could you confirm which provider you are using and if you have a click from the store or if you have run from source?

[Timo Jyrinki (timo-jyrinki)]

Hey Andrew! Weather app works just fine normally, this is a Qt change (somewhere) that's causing this. It may be Weather app would need to change the way it uses the network, or it may be a bug to be entirely fixed on Qt side. It's probably not due to provider/API being used but the Qt functions being used.

Other apps haven't so far showed networking problems, so it will be useful to know what weather app does differently and if there's something that could commonly affect other apps too.

I haven't been able to look at this much yet, but I wanted to file it so that it shows at https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.5

We're trying to land Qt 5.5.1 to wily+1 (xenial, as given a name today) during November.

[Timo Jyrinki (timo-jyrinki)]

This also happens with the weather app reboot. So the networkError gets raised when WeatherApi is used.

The reboot weather app's log is informative, and it states it gets error code 0: qml: wrong response http code, got 0 / http://wxdata.weather.com/wxdata/mobile/mobagg/NLXX0002.js?hours=48&key=b7d7a237-d6df-4157-be64-c39eca403d5b&locale=en_US&units=m

[Timo Jyrinki (timo-jyrinki)]

As another addition, it's _not_ apparmor related, since it happens also with unconfined profile.

[Timo Jyrinki (timo-jyrinki)]

This affects also Shorts app.

The common thing between them is using XMLHttpRequest. The attached QML (a modified simple QML app in SDK) always returns 0 on the patched vivid overlay Qt (silo 032) or Qt 5.5.1 (silo 012), on the phone (not on desktop).

However, even though I said it wouldn't be apparmor related, I do not get the problem with this test app if running the Main.qml from the command line. I do get when running it via SDK (which installs the .click). So maybe it's confinement related after all. I do get apparmor warnings both with or without the PPA.

[Timo Jyrinki (timo-jyrinki)]

Applying my patch https://launchpadlibrarian.net/219307454/apparmor_allow_qnetworksession_isopen.patch from bug #1404188 to the test app would fix the issue, if allowed in. It seems with Qt 5.5 it'd now be a requirement.

And true, now that I tested it again, the same applies to weather app. So my previous attempt at running weather app unconfined was not actually successful.

[Lorn Potter (lorn-potter)]

Might try using bearer plugin based on connectivity-api

https://codereview.qt-project.org/#/c/140752/

[Launchpad Janitor (janitor)]

This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-6ubuntu4

---------------
qtbase-opensource-src (5.5.1+dfsg-6ubuntu4) xenial; urgency=medium

  * Update symbols for s390x.

 -- Timo Jyrinki <email address hidden> Tue, 08 Dec 2015 13:35:46 +0000

[Timo Jyrinki (timo-jyrinki)]

qtbase-opensource-src (5.5.1+dfsg-6ubuntu3) xenial; urgency=medium

  * debian/patches/enable-tests.patch:
    - Replace the non-DFSG-free RFC files with public domain content.
    - Adjust tests to the new files.
    (LP: #1522442)
  * debian/copyright: mention the replacement.
  * Switch to opt-in for architectures to run tests on.

 -- Timo Jyrinki <email address hidden> Mon, 07 Dec 2015 14:02:11 +0000

qtbase-opensource-src (5.5.1+dfsg-6ubuntu2) xenial; urgency=high

  * Skip largefile test on s390x too, in addition to amd64.
  * Make tests to keep going till the end with -k.

 -- Dimitri John Ledkov <email address hidden> Fri, 04 Dec 2015 16:54:28 +0000

qtbase-opensource-src (5.5.1+dfsg-6ubuntu1) xenial; urgency=medium

  * New upstream release. (LP: #1437206) (LP: #1450137) (LP: #1474313)
    (LP: #1470700) (LP: #1504631) (LP: #1423659) (LP: #1474775) (LP: #1508945)
  * Replace load_testability_from_env_var.patch with upstreamed
    Add-environment-variable-support-for-testability-lib.patch
  * Drop patches in upstream:
    - Correct-typo-in-the-Gujarati-openType-identififer.patch
  * Rebase enable-tests.patch. Disable one failing QtWidgets test.
  * Build depend on GStreamer 1.0 and add a configure option for it.
  * Update symbols.
  * Mark/unmark private symbols.
  * Replace two Ubuntu patches with upstreamed patches:
    - Drop disable-generic-plugin-when-others-available.patch, replace with
      Add-an-option-to-skip-the-generic-bearer-engine.patch
    - Drop qopenglframebufferobject_powervrworkaround.patch, replace with
      Blacklist-PowerVR-Rogue-G6200-v1.3-from-supporting-B.patch
  * debian/patches/Make-sure-networkAccessibilityChanged-is-emitted.patch:
    - Include a network fix from Qt 5.5 branch (merged after 5.5.1)
      (LP: #1470700)
  * debian/patches/Use-Node-name-if-Node-logicalModuleName-is-empty-for.patch:
    - Fix a qdoc issue (LP: #1447182)
  * Remove disable_overlay_scrollbars.diff as overlay scrollbars were dropped.
  * debian/patches/Prefer-QT_PLUGIN_PATH-over-compiled-in-paths.patch:
    - Backport. Prefer QT_PLUGIN_PATH over compiled-in paths (LP: #1519927)
  * debian/patches/Fix-crash-on-exit-caused-by-QStringLiterals.patch
    - Backport. Fix a crasher on exit (LP: #1436973)
  * Replace our workaround for font rendering with new backported upstream
    patches:
    - Add debian/patches/Fix-falsely-reported-style-for-fallback-font.patch
    - Add debian/patches/Remove-historical-4-padding-in-QFontEngine-alphaMapF.patch
    - Remove debian/patches/enable_fonts_always_smoothly.patch
      (LP: #1475205)

 -- Timo Jyrinki <email address hidden> Tue, 01 Dec 2015 06:16:35 +0000