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, package hooks can invent arbitrary conditions
and reasons. Second, the _point_ of "unreportable reason" is to, well,
_not_ get reported, as the error happened because of conditions that are
not the fault of the distro. I still take this stance, but if you are
really keen on getting all of those to errors.u.c., then my suggestion
is that for _this_ particular error (executable changed on disk since
crash happened), apport adds a new tag ("binary-updated-after-crash") or
field to the report which whoopsie can check for and ignore?
--
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 kernel crashes)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1039220/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
