This bug was fixed in the package apport - 2.0.1-0ubuntu15
---
apport (2.0.1-0ubuntu15) precise-proposed; urgency=low
* apport/ui.py: create a MarkForUpload field and set that to false for
binaries that changed since the crash happened thereby preventing uploads
to the
Hello Steve, or anyone else affected,
Accepted apport into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/apport/2.0.1-0ubuntu15
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
don't report crashes for programs that don't match the file on disk
(like for
I tested apport version 2.0.1-0ubuntu15 from precise-proposed on a
Xubuntu system and did not see a .upload or .uploaded file in /var/crash
for a crash about a package which I'd modified. Marking as
verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You
This bug was fixed in the package apport - 2.6.1-0ubuntu6
---
apport (2.6.1-0ubuntu6) quantal-proposed; urgency=low
* Do not refer to the current release in the InstallationDate field
(LP: #1070400). We have the installed release version in the
InstallationMedia field.
** Branch linked: lp:ubuntu/quantal-proposed/apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
don't report crashes for programs that don't match the file on disk
(like for
** Changed in: apport (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: apport (Ubuntu Precise)
Assignee: (unassigned) = Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This was fixed in quantal in this upload:
apport (2.6.1-0ubuntu6) quantal-proposed; urgency=low
* Do not refer to the current release in the InstallationDate field
(LP: #1070400). We have the installed release version in the
InstallationMedia field.
-- Evan Dandrea e...@ubuntu.com
Hello Steve, or anyone else affected,
Accepted apport into quantal-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/apport/2.6.1-0ubuntu4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
verified that the crash report is not sent over if there are changes in
the installed package. Note that no warning that this report is
unreportable is now given.
Tagging verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
The unreportable warning does not happen as that appears when post-
processing the crash report before sending it to Launchpad. Since 12.10
is a stable release now the crash reports no longer goto Launchpad.
I've removed that bit from the test case.
** Description changed:
[Impact]
** Description changed:
TEST CASE:
1) sudo vi /etc/default/apport
2) set enabled=1
3) sudo service apport start
4) install lp-grab-attachments
5) lp-grab-attachments 2039920 (should crash with a keyerror)
6) close the apport dialog regarding the application crashing (via the X in
** Branch linked: lp:~ubuntu-core-dev/ubuntu/quantal/apport/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
don't report crashes for programs that don't match the file on disk
I've followed up to this in the merge proposal:
https://code.launchpad.net/~brian-murray/apport/no-unreportable/+merge/126082
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
don't
Brian, what changed your mind in comment 12 as compared to comment 9?
FWIW, I'm fine with Brian's merge proposal as it honors
UnreportableReason as what I intended it to be, but I'd like to get
Evan's consent here as well before I merge it. Has this been discussed
on IRC since the last comments?
Given that whoopsie doesn't currently send the UnreportableReason field
and that the field contains translated data I don't think we should
currently be sending bugs with an UnreportableReason to the crash
database. I've proposed a branch for merging that does the unreportable
reason check
** Branch linked: lp:~brian-murray/apport/no-unreportable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
don't report crashes for programs that don't match the file on disk
(like
** Changed in: apport (Ubuntu Quantal)
Importance: High = Medium
** Changed in: apport (Ubuntu Precise)
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
I agree with Brian on this. We do not at present know how much of a
problem full disks really is.
Martin, what are your thoughts on encoding something akin to
UnreportableReason in a machine parseable, non-translated form? We could
single these out on the server side and start monitoring the
OK, thanks for your feedback. So let's just take out that one particular
error then.
what are your thoughts on encoding something akin to
UnreportableReason in a machine parseable, non-translated form
I'm not too keen on it, to be honest. First, that's not really (only)
under apport's control,
In the original code from Evan this seems to have been done on purpose:
apport.fileutils.mark_report_upload(report_file)
# We check for duplicates and unreportable crashes here, rather
# than before we show the dialog, as we want to submit these to the
Ah, the one notable exception for UnreportableReason that should go to
whoopsie seems to be the You have some obsolete package versions
installed. case. So I think we should treat that specially and allow
that, but ignore all others.
--
You received this bug notification because you are a member
I think only the specific situation where the binary has changed should
not be sent to the crash database. Other unreportable reasons like full
disks may lead us to discover that a lot of people have full seperate
boot partitions and that we should be helping them by offering to remove
kernels
** Changed in: apport (Ubuntu Quantal)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
don't report crashes for programs that don't match the file
** Description changed:
+ TEST CASE:
+
+ 1) sudo vi /etc/default/apport
+ 2) set enabled=1
+ 3) sudo service apport start
+ 4) install lp-grab-attachments
+ 5) lp-grab-attachments 2039920 (should crash with a keyerror)
+ 6) close the apport dialog regarding the application crashing (via the X in
As discussed with Brian in email, whoopsie does indeed purposefully
ignore UnreportableReason reports, as they're often things we really do
want to report (out of date packages, etc). However, in this case we
don't want to continue to confuse developers with inaccurate version
information on the
** Branch linked: lp:~brian-murray/apport/bug-1039220
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039220
Title:
don't report crashes for programs that don't match the file on disk
(like for
** Summary changed:
- don't report python crashes for programs that don't match the file on disk
(like for kernel crashes)
+ don't report crashes for programs that don't match the file on disk (like for
kernel crashes)
--
You received this bug notification because you are a member of Ubuntu
28 matches
Mail list logo
