touch-packages team mailing list archive

[Barry Warsaw <1365646@xxxxxxxxxxxxxxxxxx>]

More fun: I've verified that when this .crash file gets written, the si-
dbus process does *not* exit.  That seems crazy right?  Here's what I
think is happening.  PyErr_Print() calls PyErr_PrintEx(1), and the
latter does sys.excepthook processing.  There are several places within
dbus-python that calls PyErr_Print().  I haven't gdb'd the process but
my guess is that the "exception-in-@method" case causes a PyErr_Print()
but clears, <gasp> ignores, or otherwise arranges for the exception to
not propagate to the Python main loop or otherwise cause the process to
exit.  Since apport hooks into sys.excepthook to write the .crash file,
that's how you get the crash without exiting the si-dbus process.

How to test the darn thing?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1365646

Title:
  Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download

Status in Ubuntu system image (server/client/updater):
  In Progress
Status in “system-image” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding system-image.  This problem was most recently seen with
  version 2.3.2-0ubuntu2, the problem page at
  https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions