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

[Rasty]

Binary package hint: apport

crashed with ImportError in module

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apport-gtk 1.14.1-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
ApportLog:
 apport (pid 2884) Wed Aug 11 14:11:32 2010: called for pid 2883, signal 11
 apport (pid 2884) Wed Aug 11 14:11:32 2010: executable: /usr/bin/update-alternatives (command line "update-alternatives --remove-all ps2pdf")
 apport (pid 2884) Wed Aug 11 14:11:33 2010: wrote report /var/crash/_usr_bin_update-alternatives.0.crash
Architecture: i386
CrashReports:
 600:0:0:42366:2010-08-11 14:11:32.969211000 +0200:2010-08-11 14:31:02.901211269 +0200:/var/crash/_usr_bin_update-alternatives.0.crash
 600:0:0:18299:2010-08-11 14:31:00.341211000 +0200:2010-08-11 14:31:10.961211268 +0200:/var/crash/_usr_share_apport_apport-gtk.0.crash
Date: Wed Aug 11 14:31:01 2010
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/pymodules/python2.6/gtk-2.0/gi/__init__.py", line 23, in <module>
     from ._gi import _API
 ImportError: libgirepository-1.0.so.1: cannot open shared object file: No such file or directory
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #433087, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.