This bug was fixed in the package apport - 2.0.1-0ubuntu11
---------------
apport (2.0.1-0ubuntu11) precise-proposed; urgency=low
* data/package-hooks/source_linux.py: If we report against an -lts-quantal
source package, move the source to "linux" and add a qa-kernel-lts-testing
tag, as per kernel team request in LP: #1004101 . Add source package hook
symlinks for source_linux-{,meta-}lts-quantal.py to source_linux.py.
* data/apport: apport: Also treat a binary as modified if the /proc/pid/exe
symlink does not point to an existing file any more. Backported from trunk
r2406. (LP: #984944)
apport (2.0.1-0ubuntu10) precise-proposed; urgency=low
* debian/apport.install: Actually ship the native-origins.d directory, so
that the previous bug fix for LP: #1004101 actually works.
apport (2.0.1-0ubuntu9) precise-proposed; urgency=low
[ Martin Pitt ]
* data/apport: Ignore a crash if the executable was modified after the
process started. This often happens if the package is upgraded and a
long-running process is not stopped before. Patch cherry-picked from trunk
r2296. (LP: #984944)
* Add etc/apport/native-origins.d/lts-q-backports: Accept
ppa:ubuntu-x-swat/q-lts-backport as official Ubuntu package repository, so
that users can report bugs and crashes against the backported kernel and
X.org stack. (LP: #1004101)
* data/general-hooks/ubuntu.py: Do not assume that all reports have a
ProblemType field. This will not be the case for updating a bug with
"apport-collect". (LP: #1004029)
* report.py: Do not change the SourcePackage: field if the binary package is
not installed and does not exist. This fixes source package hooks to
actually work in some cases where source and binary package names overlap.
Patch cherry-picked from trunk r2332. (part of LP: #993810)
* apport-gtk, apport-kde: Avoid collecting information twice in "bug update"
mode. This caused a crash in cases where the source package in a bug
report does not correspond to an installed binary package. Patch
cherry-picked from trunk r2334. (LP: #993810)
[ Brian Murray ]
* data/general-hooks/ubuntu.py: block reporting of package install failures
with error regarding 'not a debian format archive'. (LP: #1002535)
-- Martin Pitt <[email protected]> Thu, 28 Jun 2012 09:01:41 +0200
** Changed in: apport (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/984944
Title:
Reject crashes that happen right after upgrade
Status in “apport” package in Ubuntu:
Fix Released
Status in “apport” source package in Precise:
Fix Released
Bug description:
According to Sebastian we often get crash reports for packages which
just have been upgraded, but the old version of the executable is
still running. (e. g. bug 983697). Apport already prevents filing a
report when the executable changed between the time the crash happens
and the time the user reports the bug, but this is not sufficient
here: In that example, evince crashed right _after_ installing the new
version (the running process got confused about the new data on disk
presumably), so that check doesn't help.
We need to check if the binary was modified after the process started.
FIX: http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/2296
SRU TEST CASE:
- Install an older version of shotwell, e. g. the version from precise final.
- Start "shotwell &" in a terminal (or any other program, really)
- upgrade shotwell to precise-updates.
- Let it crash with "killall -SEGV shotwell"
- In the precise version, apport either displays the bug, or
/var/log/apport.log gets an exception about self['ExecutablePath'] not existing
any more.
- In this fixed version, apport.log just gets "executable was modified after
program start, ignoring" and does not produce a report in /var/crash/.
- Without upgrading the package in between, the proposed version continues
to generate a proper crash report.
REGRESSION POTENTIAL: Low, the change has been tested in quantal for a
while already, is covered by a test case, and the other dozens of test
cases cover the "normal" case when a binary is older than the process
start time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/984944/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
