Thanks for finding and fixing this bug!
Please create a patch for hardy (development) first, then another one for
gutsy-proposed (instead of gutsy).
Also, please look at your debdiff: there appear to be two .project files been
added, which looks like a mistake.
You should also reference the bug
I found mention of the policy behind disabling apport reporting from
update-notifier today. It seems it is a deliberate decision because
data-center infrastructure isn't ready to deal usefully with the
expected volume of apport attachments.
See https://lists.ubuntu.com/archives/ubuntu-
** Also affects: update-notifier (Ubuntu)
Importance: Undecided
Status: New
--
apport stopped working
https://bugs.launchpad.net/bugs/137406
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I've added several duplicates to this bug. It looks as if this is the
earliest of the bunch.
The issue is caused by a change in update-notifier 0.60 where the
default setting of gconf's
apps/update-notifier/show_apport_crashes
was changed to false for the Release Candidate but not changed back
** Attachment added: Enable show_apport_crashes
http://launchpadlibrarian.net/10174867/update-notifier.debdiff
** Changed in: update-notifier (Ubuntu)
Status: Confirmed = Fix Committed
--
apport stopped working
https://bugs.launchpad.net/bugs/137406
You received this bug notification
update-notifier (0.62) gutsy; urgency=low
* data/update-notifier.schemas.in:
- Re-enable apport (disabled in 0.60)
-- TJ [EMAIL PROTECTED] Fri, 26 Oct 2007 03:30:00 +
--
apport stopped working
https://bugs.launchpad.net/bugs/137406
You received this bug notification because you
Same problem here on AMD64 and i386 with Gutsy. Tried on two different
machines that were installed with the Gutsy Tribe 5 Live CD.
update-notifier is running and apport is enabled in /etc/default/apport.
/var/crash is not empty, and apport-cli works if started manually.
However starting
