check-new-release crashed with IOError in print_usage()

[Sascha]

first boot in 10.4 LTS after upgrade from release 9.10.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: update-manager-core 1:0.134.12.1
ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23
Uname: Linux 2.6.32-40-generic i686
Architecture: i386
Date: Wed Apr 11 12:45:36 2012
ExecutablePath: /usr/lib/update-manager/check-new-release
GConfNonDefault:
 /apps/update-manager/check_new_release_ignore=
 /apps/update-manager/show_details=false
 /apps/update-manager/show_versions=false
InterpreterPath: /usr/bin/python2.6
ProcCmdline: /usr/bin/python2.6 /usr/lib/update-manager/check-new-release -q
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/update-manager/check-new-release', '-q']
SourcePackage: update-manager
Title: check-new-release crashed with IOError in print_usage()
UserGroups:

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robert Roth (evfool)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #571190, so it 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. Feel free to continue to report any other bugs you may find.