scopes dont load pictures

Can you please post your ~/.cache/upstart/unity8-dash.log, ideally soon after you see the problem?

Or just upload all ~/.cache/upstart/unity8-dash.log*, we'll try and sift through it.

also note that this does not happens always, and can be reseted by turning airplane mode on and off

Potential source of the issue: bug #1413269.

There are, however, some scary errors in the log, which suggest a Qt potentially different Qt issue:

> QNetworkReplyImpl::_q_startOperation was called more than once
> QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.

Which could result in:
> QML QQuickImage: Error opening http://...

Also interesting in the logs is

file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/CroppedImageMinimumSourceSize.qml:37:5: QML QQuickImage: The specified configuration cannot be used.

that comes from
QString QNetworkSessionPrivateImpl::errorString() const
    case QNetworkSession::InvalidConfigurationError:
        return tr("The specified configuration cannot be used.");

Victor, did you get this only once or have gotten it more often?

Also do you remember if you had been switching networks, toggling the airplane mode or was it on normal usage?

Albert, normal usage - mainly roaming between Wifi and 3g. I do still get it every now and then

Can you list the scopes you have favorited? In which scope particularly you realized images stopped loading?

does this occur on rtm ?

FWIW this should not be a vivid blocker (not that it makes it less important to fix)
<tsdgeos> victorp: can you clarify if it's vivid or rtm you're having this issue with?
<victorp> tsdgeos, rtm

Victor, I have a wild guess that one of the fixes i just did in Qt for a bug Pat was seeing may also fix this one if we're lucky

Could you try to flash
   ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed

If image 257 has been created (does not exist yet as of this writing) then try to reproduce the problem

If you get image 256 (i.e. the one that is available today)
you will need to run
  sudo apt-get update
  sudo apt-get dist-upgrade
and make sure qtdeclarative is at 5.3.0-3ubuntu15~rtm1 by doing
  dpkg -l qml-module-qtquick2
and then try to reproduce the problem.

And with some luck it'll be fixed (cross fingers!)

Hi,

I am in that channel anyway, so I will wait for the next ota with your fix and let you know if I still see the problem. May take a few days to repo

I can confirm that todays images from ubuntu-rtm/14.09-proposed (257 for Krillin and 215 for Mako) contain the maybe fix.

Status changed to 'Confirmed' because the bug affects multiple users.

I am running the latest rtm 216 on mako and looks like the same issue

Note at some point I went from 3G data to wifi
After refreshing the scopes the images were there

Pat, Victor, please run in the phone the script at http://paste.ubuntu.com/10705697/ when you have this problem and attach the resulting forensics_bundle_*.tar.bz2 file here

hope this helps

My comment #23 is probably a red herring, as it looks like in the end all DNS servers are registered in dnsmasq, and it sends queries to all available servers. So I am hiding it.

Seems to happen on hotel networks (and others), where some form of web process needs to be done to be able to get on the Internet.

@Sergio: That we have identified and have an (uncommited) patch that should fix it, but it seems Victor is describing something else?

Reported as occuring on ww13-ota3 image by our OEM QA

This is a regression for me in the OTA that was just released (r21).

I note that some have said that Internet access seems to affect the issue. I don't think this is the case for me. In particular the Apps scope is affected, and those images are loaded locally, right?

I see no images in any scopes with one exception. The icons in Recent Calls and Recent Messages are fine.

On a hunch I did some experimenting. Right now I have two wifi networks. One doesn't work - you can associate, authenticate with WPA, but will not get DHCP as it is not actually connected to anything. The other works as normal. My phone was configured to either.

If my phone boots and chooses to connect to the network that doesn't work, images in scopes will be forever broken, even if I do then switch to the network that does work. So when ogra asked me in IRC if my network was working, I said yes as I had switched to the network that was working.

So, steps to reproduce:

1. Turn off DHCP and remove connectivity from your router.
2. Reboot the phone.

Expected behaviour: apps in the Apps scope have icons, but otherwise Internet scopes are not expected to work.

Actual behaviour: apps in the Apps scope do not have icons.

3. Connect the phone to a wi-fi network that does work.

Expected behaviour: on refresh, all scopes work as normal, and no icons are missing.

Actual behaviour: on refresh, all scopes work as normal but all icons are still missing. Apps scope icons continue to be missing.

Workaround: I "forget" the wi-fi network that doesn't work and reboot. This caused the phone to connect to the working network on boot, and everything worked.

This is with image r21 on an Aquaris.

> My phone was configured to either.

I meant both - my phone was configured for both networks so could use either.

12:49 <rbasak> ogra_: I suspect the issue is that if connectivity is broken at boot, something in the image-loading pipeline gets wedged forever.

So I was able to reproduce this on BQ+rtm as by suggested by Robie on comment #29, so basically just go to my router, disable DHCP and restart the phone.

Nothing that you do after that (reenabling dhcp, connecting to a different network) will make icons come back.

On the other hand this seems to work just fine on BQ+Vivid provided in channel ubuntu-touch/devel-proposed/krillin.en-proposed

As far as I understand the next BQ over the air update will be based on Vivid so I was wondering if it's worth investigating/fixing the problem on current BQ+rtm or just wait for the next OTA since it'll be fixed there anyway.

Saviq? Pat? Victor?

Lets plan to get the fix with vivid provided we are sure it is in fact fixed there

Ok, marking as fixed since the issue i can reproduce in rtm (see comment #32) i can not reproduce anymore on vivid.

Hopefully that is the same thing Victor is seeing and not two different issues that just happen to cause the same symptoms.

The related issue where local content is not provided under these conditions seems a different problem that should not occur. It may be worth investigating how that is tied in here.

> The related issue where local content is not provided under these
> conditions seems a different problem that should not occur. It may be
> worth investigating how that is tied in here.

It is tied in by the fact that Qt has a hard limit as to how many
requests it processes, and if all are busy because of a network issue,
local files won't be loaded.

There's a fix¹ in Qt 5.5 from Albert, but we will probably backport a
bigger patchset² to allow our image providers to implement threading as
they wish. This is tracked by bug #1439263.

¹ https://codereview.qt-project.org/#/c/109756/
² https://codereview.qt-project.org/#/c/108540/