touch-packages team mailing list archive

[Michał Sawicz <michal.sawicz@xxxxxxxxxxxxx>]

Yeah, we've used an updated set of plugins from a PPA for testing,
didn't clean the cache and unity8 as crashing some 30% of the time on
startup...

Disabling cache altogether when image writable would be good enough for
our case. But then it would mean we're not testing the real thing and
could miss issues that would only crop up once cache is enabled again?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1444937

Title:
  QML cache gets stale too easily

Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  It's happened many times now that after looking for an issue the
  source of it ended up to be stale QML cache.

  We need the cache to be cleared more aggressively, likely on any QML-
  related package installation. App-specific cache should be (if it's
  not) cleared on install (or maybe better - removal) and upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libqt5qml5 5.4.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  ApportVersion: 2.17.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 16 12:25:21 2015
  SourcePackage: qtdeclarative-opensource-src
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions