[TOPBLOCKER] QML cache not regenerated correctly on image update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
android (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
lxc-android-config (Ubuntu) |
Fix Released
|
Critical
|
Oliver Grawert | ||
lxc-android-config (Ubuntu RTM) |
Fix Released
|
Critical
|
Oliver Grawert |
Bug Description
image rtm-proposed 166
Multiple problems here, due to the fact that oxide was updated (a new release) and webrowser-app was updated
1) webbrowser-app cache was not updated on the image upgrade in .cache/
desktop versions of web pages are displayed until the cache is destroyed or regenerated. Try cnn.com or nytimes.com
2) no webbapps cache is regenerated, so launching of the webapps displays wrong pages (.cache/
Expected Results:
- after image upgrade, either all of the apps should be regenerated smartly, or we should blow away all of the caches to prevent an issue when a library (like oxide) is upgraded and causes an invalid cache.
Changed in android (Ubuntu): | |
importance: | Undecided → Critical |
tags: | added: rtm14 |
tags: | added: lt-blocker lt-category-visible |
below upstart job for lxc-android-config (untested yet) that should be shipped as /etc/init/ boot-hooks/ wipe-qml- cache.conf:
# This allows wiping of the complete QML app cache on OTA upgrades
start on boot-hooks WHEN=new-version
pre-start script /.cache/ QML/Apps/ *
rm -rf /home/*
end script