<type 'exceptions.NameError'>: global name 'trans' is not defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aptdaemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: aptdaemon
I was doing a software update on 19/04/11 at 4.30pm south australian time (UTC + 9.30) and received an error that "an unhandable error occurred. There seems to be a programming error in aptdaemon, the software that allows you to install/remove software and perform other package management related tasks."
Laptop is a Toshiba T230D PST4LA-00R008, ubuntu was installed from Beta 1, upgraded to Beta 2 (via update manager) before this happened. I don't know if it's relevant, but after hibernating the machine this morning, it failed to start, and so i had to reinstall grub from the 11.04 Beta 1 Live x64 that i had on a USB stick. After ubuntu sucessfully started again, it detected the problem and i clicked report problem but was told that several packages were out of date and to do an update and see if the problem reoccurs. That was why i was updating this afternoon.
Hope that helps,
Jason
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.41+bzr646-
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelMo
Annotation: Applying software changes failed
Architecture: amd64
Date: Tue Apr 19 16:27:26 2011
DesktopFile: /usr/share/
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
PackageArchitec
SourcePackage: aptdaemon
Title: <type 'exceptions.
TransactionDepends: [[], [], [], [], [], [], []]
TransactionErro
TransactionKwargs: {}
TransactionLocale: en_US.UTF8
TransactionOutput:
TransactionPack
TransactionRole: role-commit-
UpgradeStatus: No upgrade log present (probably fresh install)
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 #764883, 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.