touch-packages team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

It's clear the current Qt 5.4.1 has bugs related to this, but it's not
clear how to fix those without causing regressions. It should be useful
to experiment with the PPA https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-032/ and try how things work with that.
After upgrading with 'citrain device-upgrade 32 0000', double-check that
especially 'dpkg -s libqt5network5' shows the version number '5.4.1
+dfsg-2ubuntu11~vivid1~test1'.

That PPA now has commits that have been all merged in upstream Qt 5.5
branch, but the problem is that if you check up Weather app it reports
connection not available. I didn't find another app that would have the
same behaviour, and it might be just Weather app doing something weird
regarding its network usage. But the silo can't be landed to vivid as
long as there are regressions.

If 032 would resolve also this bug in addition to the 1470700, without
seeing regressions elsewhere, then we really should find out what's
wrong with the Weather app.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1502282

Title:
  "unknown" connectivity status problematic

Status in The Savilerow project:
  New
Status in unity-scopes-api package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  metadata provides a scope a network connectivity status enum with three possible states:
  * connected
  * disconnected
  * unknown

  Sometimes unknown is the current state. This is quite problematic
  because in general a scopes that queries the network (that is, most
  scopes) need to know whether there is network or is not network and
  depending on this either make the network queries or display an error
  message.

  A status of unknown connectivity leaves the scope with no valid option:
  * the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily
  *  the scope could assume the network is up, but this is dangerous if it is not up

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions