apport-gtk crashed with TypeError in ui_present_crash(): glib.markup_escape_text() takes at most 1 argument (2 given)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu oneiric (development branch)
Release: 11.10
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
apport-gtk:
Installed: 1.22.1-0ubuntu1
Candidate: 1.22.1-0ubuntu1
Version table:
*** 1.22.1-0ubuntu1 0
500 http://
100 /var/lib/
3) What you expected to happen
Expected to be able to file a bug report on whatever is ailing my desktop on launch
4) What happened instead
I have a crash on desktop launch. While trying to get to what is wrong when I go to submit a bug apport crashes so I'll start with submitting a bug on apport-gtk and go from there.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apport-gtk 1.22.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-10-generic i686
ApportLog:
ERROR: apport (pid 10214) Tue Sep 6 21:21:57 2011: called for pid 10134, signal 11
ERROR: apport (pid 10214) Tue Sep 6 21:21:57 2011: executable: /usr/lib/
ERROR: apport (pid 10214) Tue Sep 6 21:22:02 2011: wrote report /var/crash/
Architecture: i386
Date: Mon Sep 5 15:18:09 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: apport
Title: apport-gtk crashed with TypeError in ui_present_crash(): glib.markup_
UpgradeStatus: Upgraded to oneiric on 2011-09-04 (2 days ago)
UserGroups:
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 #833592, 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.