** Changed in: canonical-devices-system-image
Status: Confirmed => Invalid
--
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
** Project changed: qtubuntu => qtubuntu (Ubuntu)
--
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 notifi
** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => backlog
--
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
On Fri, Oct 23, 2015 at 01:07:16PM -, Martin Pitt wrote:
> Steve Langasek [2015-10-22 18:11 -]:
> > > * If we really want to dump, we could investigate into sendfile. I'm not
> > > * entirely sure that it works with data coming in via stdin, but it's
> > > * worth a try as we would av
Steve Langasek [2015-10-22 18:11 -]:
> > * If we really want to dump, we could investigate into sendfile. I'm not
> > * entirely sure that it works with data coming in via stdin, but it's
> > * worth a try as we would avoid the kernel -> userspace copy.
>
> This is an interesting suggest
On Thu, Oct 22, 2015 at 03:27:59PM -, Thomas Voß wrote:
> So a few thoughts:
> * Releasing graphics buffers in case of SIGSEGV seems to be quite
> dangerous as we are dealing with potentially corrupted memory. I
> don't think we should take this approach.
Why is this "quite dangero
@Pat: Not yet, on my list.
--
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
So a few thoughts:
* Releasing graphics buffers in case of SIGSEGV seems to be quite dangerous
as we are dealing with potentially corrupted memory. I don't think we should
take this approach.
* It would be nice to have the ability to skip core dumping and instead just
produce a threaded sta
@thomas have you discussed a new approach for crash analysis?
--
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 m
** Changed in: canonical-devices-system-image
Milestone: ww40-2015 => ww46-2015
--
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
** Changed in: qtubuntu
Status: Confirmed => Invalid
--
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 man
On Tue, Sep 15, 2015 at 08:45:39PM -, Gerry Boland wrote:
> Ok, task is for Qt clients to intercept the sigsegv signal, and in a
> handler close the mir connection which should release all its video
> buffers, then re-raise segv. Would it be of interest to have all mir
> clients exhibit this be
Ok, task is for Qt clients to intercept the sigsegv signal, and in a
handler close the mir connection which should release all its video
buffers, then re-raise segv. Would it be of interest to have all mir
clients exhibit this behaviour by default? If so, should put this
behaviour in "mirclient"
I
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
--
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:
appo
it would generally not be appropriate for a library to install a signal
handler, however. Is this something that will need support up and down
the unity8 stack?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
--
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:
appo
Assigning down to QtMir as it does all the video buffer handling for
unity8.
** Package changed: unity8 (Ubuntu) => qtmir (Ubuntu)
--
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:
appor
opening a task on unity8, for discussion with the unity team about the
possibility of unmapping video buffers from a SIGSEGV handler.
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for the nice summary Steve. I dropped the nice in
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/3003 .
It might certainly improve things a bit, but if it takes long now it
will still take long with this; this is a little optimization, not
really a complete solution.
We d
some thoughts upon analysis of /usr/share/apport/apport:
- apport does have support for blacklisting crash reporting for specific
programs. For programs that are critical for the UI on the phone and which
cause a hard lockup of the UI while the crash report is running, we could use
this blackl
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-ima
It's estimated to have a moderate impact on a large portion of Ubuntu
users.
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: Confirmed => Triaged
** Changed in: appo
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
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
23 matches
Mail list logo