The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: apport (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
> A crash on logout could involve an app failing to save a document or
settings as it exits.
That should already happen before. gnome-session causes applications to
ask for saving files etc. before it actually tears down the session.
It's only crashes that happen during that teardown that are bei
If this change is a good idea, then backporting it to 12.04 is fine by
me. I'm still skeptical, though. A crash on logout could involve an app
failing to save a document or settings as it exits. If so, that's
something developers should discover and fix just as much as any other
error.
As a compar
Matthew Paul Thomas [2014-01-10 11:19 -]:
> This is the sort of thing that the "(by 12.04 standards)" line exists
> for on the graph. But that works only for expanding the scope of error
> reporting, not reducing it -- unless we updated 12.04 to continue
> reporting, but start distinguishing, e
Martin, if we're just dropping the errors altogether, rather than
aggregating them with the next interrupt-worthy error, that will reduce
the reported error rate on errors.ubuntu.com. That is, it will make it
look as if Ubuntu has become more reliable when it hasn't.
This is the sort of thing that
This bug was fixed in the package apport - 2.13.1-0ubuntu1
---
apport (2.13.1-0ubuntu1) trusty; urgency=medium
* New upstream release:
- Fix report.test_get_timestamp test for running in other time zones.
- Fix erroneous "gdb-multiarch not installed" warnings in ui tests.
trunk r2746 now does not produce popups any more at the start of the
desktop session which concern crashes from ealier sessions. You can
still manually report them by double-clicking on the .crash, or running
apport-{cli,gtk,kde} on the .crash file, but they won't pop up
automatically any more. Tha
** Changed in: apport
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 noti
** Changed in: apport (Ubuntu)
Status: In Progress => Triaged
--
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 ma
Unless I'm mistaken (which is possible), this bug is affecting many,
many users who are being greeted at login with a rather nasty looking
alert for myriad small errors caught at logout or shutdown (e.g. Google
Chrome not exiting correctly - a common occurrence).
This massively impacts the perceiv
** Changed in: apport
Importance: Undecided => Medium
** Changed in: apport
Status: New => Triaged
--
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 logi
** Also affects: apport
Importance: Undecided
Status: New
--
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 man
** Tags added: whoopsie-daisy
--
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
> Actually, I just realized it's very simple. We can keep crashes from
remote/non-graphical sessions and alert about them, but ignore crashes
which happened in a previous graphical user session.
Not that simple after all. We cannot rely on $DISPLAY for e. g. unity
and other d-bus services that wer
> Telling them apart from legitimate crashes from remote/noninteractive
sessions is a lot more difficult,
Actually, I just realized it's very simple. We can keep crashes from
remote/non-graphical sessions and alert about them, but ignore crashes
which happened in a previous graphical user session.
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
16 matches
Mail list logo
