The main use case for showing old user (not system) related crashes
after login are crashes from cron, screen, and remote sessions. However,
the are certainly a corner case, and for stable releases I'd go as far
as ignoring them entirely. This would be a simple and safe SRUable
change. Telling them apart from legitimate crashes from
remote/noninteractive sessions is a lot more difficult, and I don't have
a good off-hand idea how to do that.
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
** Changed in: apport (Ubuntu)
Status: New => Triaged
** Also affects: apport (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu Precise)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: apport (Ubuntu)
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/1033932
Title:
Error alerts appear on login for problems in previous session
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1033932/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
