update-manager cannot initialize with NameError 'logging'

Bug #467904 reported by Josh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

Using 9.10, upgraded from 9.04. May have to do with an incorrectly configured locale.
Traceback:
  File "/usr/bin/update-manager", line 107, in <module>
    app = UpdateManager(data_dir, options)
  File "/usr/lib/python2.6/dist-packages/UpdateManager/UpdateManager.py", line 119, in __init__
    logging.exception("setlocale failed")
NameError: global name 'logging' is not defined

ProblemType: Crash
Architecture: i386
Date: Sat Oct 31 21:41:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.6
Package: update-manager 1:0.126.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with NameError in __init__()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse pulse-access sambashare vboxusers

Revision history for this message
Josh (josh-holthaven) wrote :
Revision history for this message
Josh (josh-holthaven) wrote :

Solved. I sent this bug report, and found out how to fix it on my system:
The file /etc/default/locale originally contained only one line:
LANG="en_US.UTF-8"
I added a second line:
LANGUAGE="en_US:en"
Then ran:
$ sudo dpkg-reconfigure locales
with output:
Generating locales...
  en_US.UTF-8... up-to-date
Generation complete.
Now update-manager works just fine.

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #473101, 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
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.