touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #85730
[Bug 1278780] Re: [Ubuntu-phone] BQ r23 total off and unwilling to react
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/
slangasek@xxxxxxxxxx vorlon@xxxxxxxxxx
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1278780
Title:
apport takes too long to write crash report, appears to lock up phone
Status in Apport crash detection/reporting:
Confirmed
Status in apport package in Ubuntu:
Triaged
Bug description:
I can trigger a crash easily on my phone via bug 1262711. Other bugs
are available.
When that happens my phone appears to freeze. I am unable to do
anything for approximately 1 to 1.5 minutes. As a user my initial gut
reaction is to reboot the phone, thus losing the crash report, and
wasting my time.
Having the phone lock up for 1.5 minutes is a terrible user
experience. Can we fix/mitigate/workaround that?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.13.2-0ubuntu2
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.13.2-0ubuntu2
Architecture: armhf
CrashReports:
664:32011:110:10083:2014-02-10 15:41:18.152893384 +0000:2014-02-10 15:11:09.169231740 +0000:/var/crash/_usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash
640:0:110:1681527:2014-02-10 15:12:10.985193887 +0000:2014-02-10 15:12:05.639489630 +0000:/var/crash/_usr_bin_powerd.0.crash
640:0:110:21384:2014-02-11 07:58:44.876281991 +0000:2014-02-11 07:58:44.876281991 +0000:/var/crash/_usr_sbin_system-image-dbus.0.crash
640:32011:110:17122318:2014-02-11 09:19:49.915478726 +0000:2014-02-11 09:18:20.850439824 +0000:/var/crash/_usr_bin_unity8.32011.crash
Date: Tue Feb 11 09:20:15 2014
InstallationDate: Installed on 2014-02-11 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140211)
PackageArchitecture: all
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1278780/+subscriptions
Follow ups
References