Ubuntu
command-not-found package

command-not-found crashed with UnboundLocalError in setup_locale()

Bug #269821 reported by toobuntu on 2008-09-13

20

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	command-not-found (Ubuntu)	Fix Released	Medium	Colin Watson

Bug Description

Binary package hint: command-not-found

$ lsb_release -dr
Description: Ubuntu intrepid (development branch)
Release: 8.10

$ apt-cache policy command-not-found
command-not-found:
  Installed: 0.2.22ubuntu1
  Candidate: 0.2.22ubuntu1
  Version table:
*** 0.2.22ubuntu1 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/command-not-found
InterpreterPath: /usr/bin/python2.5
Package: command-not-found 0.2.22ubuntu1
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/command-not-found -- lsb-release
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
PythonArgs: ['/usr/lib/command-not-found', '--', 'lsb-release']
SourcePackage: command-not-found
Title: command-not-found crashed with UnboundLocalError in setup_locale()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags:

Revision history for this message

toobuntu (toobuntu) wrote on 2008-09-13:

#1

Dependencies.txt Edit (988 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (8.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (760 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (715 bytes, text/plain; charset="utf-8")

Revision history for this message

Andreas Moog (ampelbein) wrote on 2008-09-16:

#2

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in command-not-found:
importance:	Undecided → Medium
status:	New → Incomplete

Revision history for this message

Colin Watson (cjwatson) wrote on 2008-10-13:

#3

This is easy for a developer with a modicum of creativity to reproduce. (Run command-not-found with e.g. LANG=foo PATH=/bin.)

Changed in command-not-found:
status:	Incomplete → Triaged

Revision history for this message

Colin Watson (cjwatson) wrote on 2008-10-13:

#4

Oh, and you have to force a crash somewhere as well - this is in the crash handler. Nevertheless, still a bug.

Colin Watson (cjwatson) on 2008-10-13

Changed in command-not-found:
assignee:	nobody → kamion
status:	Triaged → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-10-15:

#5

This bug was fixed in the package command-not-found - 0.2.25ubuntu2

---------------
command-not-found (0.2.25ubuntu2) intrepid; urgency=low

  [ Era Eriksson ]
  * Print where-to-find-command, incorrect-PATH, and crash-guard messages to
    stderr rather than stdout (LP: #212723).

  [ Colin Watson ]
  * Fix various crash bugs in the crash handler (LP: #269821).
  * Adjust crash handler syntax to be friendly to Python 2.4 (LP: #234540).

-- Colin Watson <email address hidden> Wed, 15 Oct 2008 13:27:20 +0100

Changed in command-not-found:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #282319

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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