apport-kde crashed with NameError in ui_present_package_error(): global name 'name' is not defined

Bug #905895 reported by mrl586
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

mrl586@S205:~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
mrl586@S205:~$ apt-cache policy apport-kde
apport-kde:
  Asennettu: 1.90-0ubuntu1
  Ehdokas: 1.90-0ubuntu1
  Versiotaulukko:
 *** 1.90-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     1.23-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-kde 1.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
Uname: Linux 3.2.0-5-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Dec 18 10:37:25 2011
DuplicateOf: https://bugs.launchpad.net/bugs/899898
ExecutablePath: /usr/share/apport/apport-kde
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111211)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde
ProcEnviron:
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/apport/apport-kde']
SourcePackage: apport
Title: apport-kde crashed with NameError in ui_present_package_error(): global name 'name' is not defined
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
mrl586 (mrl586) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #899898, 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.

tags: removed: need-duplicate-check
visibility: private → public
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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