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
ERROR: apport (pid 4123) Mon Jul 16 17:37:12 2012: called for pid 3742, signal
11
ERROR: apport (pid 4123) Mon Jul 16 17:37:12 2012: executable was modified
after program start, ignoring
Looks good, verification-done
** Tags removed: verification-needed
** Tags added: verification-done
--
Yo
** Branch linked: lp:ubuntu/precise-proposed/apport
** Branch linked: lp:ubuntu/apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984944
Title:
Reject crashes that happen right after upgrade
To
I uploaded 2.0.1-0ubuntu11 to the precise-proposed unapproved queue now
which fixes this in a cleaner way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984944
Title:
Reject crashes that happen rig
** Description changed:
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 h
I just realized that gnomine is a hard example, as it forks, and thus
killall will kill both processes. So you either manage to kill the right
one, or apport will race with itself, and you might catch the wrong
process first.
So you get the exception because in this case the symlink shows "...
(de
I still can't verify that, testing with the package udpate steps I still
get
Traceback (most recent call last):
File "/usr/share/apport/apport", line 290, in
info.add_proc_info(pid)
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 439, in
add_proc_info
assert os.path.ex
Indeed, a mere touch would not actually change the executable; a package
upgrade would change the inode, so they don't test the same thing.
** Description changed:
According to Sebastian we often get crash reports for packages which
just have been upgraded, but the old version of the executab
That's actually not expected. While the exception certainly helps to
prevent the bug filing (see the test case description), it's supposed to
not even get that far, as the mtime comparison happens earlier. So I
guess that test case is wrong, we probably need one which actually
involves upgrading a
using the testcase the log get those:
"ERROR: apport (pid 9970) Tue Jun 12 12:50:37 2012: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 290, in
info.add_proc_info(pid)
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 439, in
a
A problem was indicated in installing python-problem-
report_2.0.1-0ubuntu9_all.deb at http://askubuntu.com/questions/148383
/how-to-resolve-dpkg-error-processing-var-cache-apt-archives-python-
apport-2-0/148393#148393. I believe that is this SRU.
Of course this could simply have been a user erro
Hello Martin, or anyone else affected,
Accepted apport into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Description changed:
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 h
Hi! This bug needs a test case and regression potential before we accept
the upload to precise-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984944
Title:
Reject crashes that happen right
** Changed in: apport (Ubuntu Precise)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984944
Title:
Reject crashes that happen right after upgrade
To mana
** Also affects: apport (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu Precise)
Status: New => In Progress
** Changed in: apport (Ubuntu Precise)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: apport (Ubuntu Precise)
Import
This bug was fixed in the package apport - 2.1-0ubuntu1
---
apport (2.1-0ubuntu1) quantal; urgency=low
* New upstream release:
- packaging.py, install_packages(): Add permanent_rootdir flag and if set,
only unpack newly downloaded packages. Implement it for the apt/dpkg
Fixed in trunk r2296.
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984944
Title:
Reject crashes that happen right after upgra
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984944
Title:
Reject crashes that happen right after upgrade
To manage notifications about this bug go to:
https://bugs.lau
/proc/pid/status does not have an obvious start time, but we can look at
the mtime of the /proc/pid/exe symlink and compare it with the mtime of
the symlink target.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
20 matches
Mail list logo
