On Mon, Jun 22, 2015 at 08:21:44PM +0200, Torsten Sachse wrote: > On Mon, 22 Jun 2015, Steve Langasek wrote: > >The only part that should be running when not on wifi is the crash > >collection. We certainly *should* be running that when not on wifi; you > >don't get a second chance to run the kernel crash handler, and we want to > >know about crashes that only happen when not on wifi (including, possibly, > >crashes that happen /because/ you're not on wifi).
> While that may be true, there has to be an option to switch off such crash > collection permanently or temporarily. There is an option, and there is reportedly a bug in the handling of that option, as was already mentioned in this thread. https://bugs.launchpad.net/ubuntu/+source/whoopsie- preferences/+bug/1437633 I was responding to the suggestion that the behavior should somehow be dependent on whether the device is connected to wifi at the time of the crash. That's just wrong. > >The trouble is that, until the crash handler has finished consuming the core > >file from the kernel and exited, the original process is blocked. So the > >shell can't know that the process has died and move on until the crash > >handler has finished running. (The same is true on the desktop, it's just > >less impactful because the app is usually not full screen and blocking the UI > >at the time.) > Thanks for the explanation. To me, this is just all the more reason to > have an option to disable it, maybe only for a day or a couple. Imagine > being somewhere and urgently needing your phone which then hangs because > some crash logs are being collected? The app that crashed might not even > be the one you urgently need. Crash collection should, imho, not take > precedence over the dialog to accept a call as this is still the main > functionaly of a phone, at least for me. While the shell can't do anything with the crashed app until the crash handler has finished, that *shouldn't* mean that it prevents the shell from, e.g., switching apps. This is why people were asking about crash files for unity8. It's unexpected that a crashed app should take out the /whole/ UI, and if that happens that's a bug in unity8, not just a bug in the app that's crashing. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278780 Title: apport takes too long to write crash report, appears to lock up phone To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1278780/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
