apport-gtk crashed with ImportError in <module>()

Bug #124354 reported by fragro
164
This bug affects 36 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Medium
Martin Pitt

Bug Description

Binary package hint: apport

ProblemType: Crash
ApportLog:
 apport (pid 8366) Fri Jul 6 10:31:05 2007: called for pid 7825, signal 11
 apport (pid 8366) Fri Jul 6 10:31:05 2007: executable: /usr/bin/inkscape (command line "inkscape")
 modinfo: could not open cdrom: No such device
 modinfo: could not open cdrom: No such device
 apport (pid 8366) Fri Jul 6 10:31:19 2007: wrote report /var/crash/_usr_bin_inkscape.1000.crash
Architecture: i386
Date: Fri Jul 6 10:32:00 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx
Package: apport-gtk 0.88
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcCwd: /home/fragro
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with ImportError in <module>()
Uname: Linux fragro-laptop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux

Tags: apport-crash
Revision history for this message
fragro (frank-grossmann) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Did this happen during a system upgrade? What does

  python -c 'import launchpadBugs.storeblob'

print out when you run this in a terminal?

Changed in apport:
status: New → Incomplete
Revision history for this message
Andrew Conkling (andrewski) wrote :

I think bug #124488 may be a duplicate. When I import lpB.sb on the command line, I get no error (no output at all, so I'm assuming it's working).

Martin Pitt (pitti)
Changed in apport:
assignee: nobody → pitti
status: Incomplete → Fix Committed
Changed in apport:
importance: Undecided → Medium
Revision history for this message
Martin Pitt (pitti) wrote :

apport (0.92) gutsy; urgency=low

  * bin/crash-digger: Do not crash if duplicate db is locked when attempting
    to consolidate it. This happens often because in the DC we have two
    parallel instances (for amd64 and i386).
  * Move ubuntu-fat-chroot from bin/ to debian/local/, since it is so heavily
    Ubuntu specific.
  * debian/local/ubuntu-fat-chroot: Use diversions for the binaries we want to
    disable, so that chroot upgrades do not trash the modifications.
  * debian/local/setup-apport-retracer: launchpad-crash-digger ->
    crash-digger.
  * bin/crash-digger: Add option -i/--arch-indep-dupcheck to explicitly enable
    duplicate checking of arch-independent crashes like Python exceptions. We
    only want to process them on one architecture to avoid scattering the
    duplicate database.
  * apport/crashdb_impl/launchpad.py, get_unfixed(): Search for 'apport-crash'
    tag, not 'apport'.
  * bin/apport-unpack: Fix format string in error message.
  * apport/ui.py, __init__(): Intercept ImportError, which can happen for
    crashes during system upgrades. (LP: #124354)
  * Add general-hooks/automatix.py: Refuse to send problem reports if
    automatix is installed.
  * doc/package-hooks.txt: Do not document UnsupportableReason, since it does
    not make sense to set it in package hooks (it is checked before calling
    the hooks). Hooks should use UnreportableReason only.
  * apport/ui.py, test_run_crash_package(): Check that 'Package' problem
    reports collect additional information, too.
  * apport/ui.py, collect_info(): Collect additional information for 'Package'
    problem reports, too.
  * Revive preloadlib/:
    - Remove PIPE_CORE #ifdefs and make them the default. We do not need to
      support the Edgy kernel patches in this version any more.
    - Install signal handler for SIGABRT, too.
    - Read core ulimit, pass it to apport in CORE_REAL_RLIM, and set it to
      zero for the program, since we do not actually want the kernel to write
      core files when we pipe the core dump to apport.
    - test-apport: Pass APPORT_REPORT_DIR to the manually called apport
      instance in the memory clipping test; otherwise it'll write into
      /var/crash/, which we do not consider in library mode.
  * apport/crashdb_impl/launchpad.py, __init__(): Only do the "download bug
    #2" hack if we actually have an authentication cookie. Thus, do it only on
    the retracing servers, not on the client side. (LP: #125142)
  * apport/report.py, crash_signature(): Generate a signature for one-line
    Python tracebacks, too. This sometimes seems to happen, e. g. LP#124588.
    (LP: #125020)
  * apport/crashdb_impl/launchpad.py, update(): Set bug importance to Medium
    if retracing was successful. (LP: #106379)

 -- Martin Pitt <email address hidden> Tue, 24 Jul 2007 21:50:34 +0200

Changed in apport:
status: Fix Committed → Fix Released
Revision history for this message
hosoka (hosoka-deactivatedaccount-deactivatedaccount) wrote :

Hello, I was doing the Update Manager and got this error also.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.