** Changed in: canonical-devices-system-image
Milestone: 12 => backlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
Title:
Corrupt QML cache - Apps Fail to start
To manage notification
Thinking about this more, we can get the status code that is returned by
the utility. If we wanted to return a custom status code for "delete the
QML cache" we could do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Changed in: canonical-devices-system-image
Milestone: None => 12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
Title:
Corrupt QML cache - Apps Fail to start
To manage notifications a
The UAL signal for failing on starting would only be before the process
starts executing. So basically everything up to passing off to the Exec
line in the desktop file. After that we pretty much lose track of the
process. So I don't think that UAL can really be used to tell whether
the app failed
of course!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
Title:
Corrupt QML cache - Apps Fail to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-dev
Sure, I'm not saying there isn't a problem in the cache, just saying the
user doesn't care - and we should do everything in our power to get the
app to start again. IMO that's orthogonal to the fact that we need to
investigate how the QML cache gets corrupted.
--
You received this bug notificatio
My fear is that by cleaning the cache every crash we're just postponing
assigning someone to actually fixing the QML cache problems :/
(of course, as you say, it may be that it's not the QML cache at fault,
but we know that there's something wrong going on there almost for sure,
right? so many bug
That's assuming the QML cache is at fault in the first place - if the
app just crashes on its own accord, clearing the cache or not doesn't
really matter.
Thing is, in case the cache is corrupt, but the app is dynamic - it will
start but then crash after the user opened some new page with a new qm
Well, if we get a report of the crash through errors.u.c, maybe not?
Better for the app to start next time or not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
Title:
Corrupt QML cache - Ap
Wouldn't clearing the cache at every crash just hide the problem under
the carpet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
Title:
Corrupt QML cache - Apps Fail to start
To manage noti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-app-launch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
T
It's also possible that u-a-l doesn't give qtmir notice that the app
indeed failed to start. I don't think we're clearing the cache on *any*
crash, just on startup - maybe we need to be more aggressive with that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: canonical-devices-system-image
Status: Triaged => Confirmed
** Changed in: canonical-devices-system-image
Milestone: 11 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: canonical-devices-system-image
Assignee: kevin gunn (kgunn72) => Michał Sawicz (saviq)
** Changed in: canonical-devices-system-image
Milestone: None => 11
** Changed in: canonical-devices-system-image
Status: Confirmed => Triaged
** Changed in: qtmir (Ubuntu)
** Also affects: ubuntu-app-launch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
Title:
Corrupt QML cache - Apps Fail to start
To manage
I just duped over a number of these reports, clearly we are not properly
removing the cache when the app fails to start.
** No longer affects: ubuntu-app-launch (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
Title:
Corr
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-app-launch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560020
T
QtMir has code that should delete the cache, if the app stops
unexpectedly (i.e. probably crashed).
The QML cache system also does a CRC check on the cache file, to check
it before using it. So the file being munged unexpectedly should not be
a fatal condition.
Instead, if the app is itself corru
I'll make a suggestion here to get some comments, but it seems to me there's 2
threads to chase
1) actually figure out why the cache is getting corrupted
2) create some detection as part of the launch (ual? or qtmir?) to determine if
there are issues and then delete the cache & make a second laun
20 matches
Mail list logo
