← Back to team overview

touch-packages team mailing list archive

[Bug 1528886] Re: Checking for updates never finishes

 

HI Lorn, just noting that scopes *generally receive the network
connectivity status as an enum passed to them from the unity-scopes-
shell as metadata.  The only thing that scope-aggregator does with the
network status is (depending on the scope config), it displays a "Hey,
no network" type message. Beyond this, responding reasonably to no-
network conditions is up to child scopes.

Not sure it is relevant, but I have found an issue with this enum:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-
api/+bug/1502282/comments/24

* I say "generally" because scopes *can* take additional steps.

-- 
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 Canonical System Image:
  In Progress
Status in Today Scope:
  New
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash<QString,
  UpdatePlugin::Update*>&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions