On Mon, May 12, 2014 at 01:44:48PM +0200, Bjoern Michaelsen wrote: > Hi, > > while chasing around bug 1219245 as it showed up so high in errors.ubuntu.com > I > found that: > - that bug exists since at least LibreOffice 4.0.2 (released with Ubuntu > 13.04) > - all of todays reports come from 14.04 exclusively > - the bug wasnt ranked high in errors before 14.04 release > > I vaguely remember seeing that bug peaking up on errors right after 13.10 was > released, just to quickly vanish into irrelevance again (I might be wrong > there, as I cant go back in time on errors.u.c). > > While there is no good reproduction scenario in the bug reports, there is one > report claiming it crahed "while installing a font" and another it crashed > "during an upgrade". This leaves me with the suspicion, that the crash is > actually people leaving LibreOffice running during a release upgrade (which is > brave and a nice vote of confidence, but not really a supported scenario). > > By extension, this leaves me with the suspicion that the nice exponential > drop-off of crash reports for a distro over time is not actually us fixing > stuff via SRUs (which is way to slow for that), but that it is just fewer > people doing upgrades vs. people running it in production and experiencing > some transitional crashes (that do not happen after they use the system 'in > production' afterwards). > > Does errors.ubuntu.com have a way to identify crashers during a release > upgrade > (or maybe even: first-starts after a release update)? Would it be possible to > filter crash reports for that scenario, e.g. trivially: mark crashers 48hours > after the upgrade as 'potentially an upgrade sideeffect' or somesuch?
There is not a way to identify crashers during a release upgrade but apport does include an 'UpgradeStatus' key (which can be wrong about the date[1]) but is correct if no upgrade has occurred. Looking at the first two instances of the crash report to which you are referring: https://errors.ubuntu.com/bucket/?id=/usr/lib/libreoffice/program/soffice.bin%3A11%3AImplDevFontListData%3A%3A~ImplDevFontListData%3AImplDevFontList%3A%3AClear%3AOutputDevice%3A%3AImplUpdateAllFontData%3AImplHandleSalSettings%3AImplWindowFrameProc We can see that the UpgradeStatus is "No upgrade log present", so your initial suspicion about this happening during a release upgrade may be incorrect. I also went ahead and ran a query of 100 of the crash instances for UpgradeStatus and found the following. 100 examined. 39 upgraded. 61 fresh install. If there is any other information I can provide to help track this down please let me know. [1] http://launchpad.net/bugs/1315559 -- Brian Murray
signature.asc
Description: Digital signature
-- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
