© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I think there are actually two separate issues here.
If an old version of an application is still running, then the package is upgraded, and then it crashes. The crash file is about the new version of the application even though the old binary is running. In this case _MarkForUpload is True and there is no UnreportableReason. This problem has probably always existed.
The other issue is the one I describe in the description where a .crash file is created, data collection is not done (for whatever reason) until after the package has been upgraded, and when it is collected UnreportableReason contains information about the program changing. In this case _MarkForUpload should be False and I'll test that again.