[Bug 59993] Re: apport stuck in loop
Needs Info -Fix Released ** Changed in: apport (Ubuntu) Status: Needs Info = Fix Released -- apport stuck in loop https://launchpad.net/bugs/59993 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59993] Re: apport stuck in loop
Confirmed fixed. -- apport stuck in loop https://launchpad.net/bugs/59993 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59993] Re: apport stuck in loop
If you already want to test the fixed-harder packages: deb http://people.ubuntu.com/~pitti/packages/apport/ ./ How do I get a pending crash log to occur at login? I could reliably test a couple other bugs if I could do that... This is a fast and convenient way that doesn't even require you to restart your session: 1. killall update-notifier 2. bash 3. kill -SEGV $$ 4. Press Alt+F2 and start 'update-notifier' -- apport stuck in loop https://launchpad.net/bugs/59993 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59993] Re: apport stuck in loop
This should fix the exception: apport (0.21) edgy; urgency=low . * apport: Keep a partially written report with '000' permissions, and only chmod it to 0600 when it is fully written. This stops update-notifier from picking up half-written reports and get activated several times. Closes: LP#59988 * apport: Add the executable path to the first line of logging. * apport: Run the complete code under control of the general exception fallback handler. * debian/apport.default: Increase maximum core size to 200 MB, to also catch Firefox and Evolution core dumps. * apport_utils.py, find_file_package(): Before searching the dpkg database (which is expensive), check if the executable path matches a whitelist of path prefixes. This replaces the weaker blacklist (/tmp and /home) in apport itself. * gtk/apport-gtk: Show a progress dialog while checking for bug patterns and execute report_search_bug_patterns() in a separate thread, so that the UI is not potentially blocked for a long time. * apport: Gracefully abort if we cannot readlink /proc/pid/exe, instead of falling over with an exception. Closes: LP#59993 * debian/rules: Use 'multiuser' instead of 'defaults' for dh_installinit. Clean up the unnecessary rc symlinks in postinst and add appropriate sysv-rc dependency. -- apport stuck in loop https://launchpad.net/bugs/59993 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59993] Re: apport stuck in loop
Scott, can you please take a look at bug 59988? Does that resemble your experience? I'll fix that bug as soon as uploads are opened again after knot-3. -- apport stuck in loop https://launchpad.net/bugs/59993 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59993] Re: apport stuck in loop
It does. I guess I'll wait. How do I get a pending crash log to occur at login? I could reliably test a couple other bugs if I could do that... -- apport stuck in loop https://launchpad.net/bugs/59993 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs