do-release-upgrade crashed with NameError in init_proxy()

Bug #616005 reported by Mathieu Marquer
76
This bug affects 15 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

Not sure, bug report appeared after start. Currently using X failsafe mode.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: update-manager-core 1:0.142.6
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Aug 10 20:04:11 2010
ExecutablePath: /usr/bin/do-release-upgrade
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
InterpreterPath: /usr/bin/python2.6
ProcCmdline: /usr/bin/python2.6 /usr/lib/update-manager/check-new-release -q
ProcEnviron:

PythonArgs: ['/usr/lib/update-manager/check-new-release', '-q']
SourcePackage: update-manager
Title: do-release-upgrade crashed with NameError in init_proxy()
UserGroups:

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :
visibility: private → public
Revision history for this message
Peter Collins (shipit-3720) wrote :

Same here - only way I seem to be able boot is in safemode.

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :

Confirmed since 10 people report being affected.

Changed in update-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Tony Mugan (tmugan) wrote :

Same here with Maverick Alpha and all latest updates.

tony@orac:~$ uname -a
Linux orac 2.6.35-14-generic #20-Ubuntu SMP Fri Aug 6 22:28:24 UTC 2010 x86_64 GNU/Linux

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.