aptd crashed with UnboundLocalError in _emit_acquire_item(): local variable 'lang' referenced before assignment

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

affected me on updating resources ... after a partial apt-get upgrade!
Seems to be fixed after complete upgrade ... now!

Affect me again . . . after partial upgrade. Seems to happen from time to time.

I was working with my graphics cards. I have an XFX 1 GB PCI-e running my Dell 22 inch monitor on dvi and my Dell 17 inch monitor. On my first PCI I have the ATI Radeon 64 MB graphics card running the Acer 19 inch monitor. The Acer is working now but the Nvidia is giving me troubles because it is saying no proprietary drivers are in use on this system. Probably not related.

1) Ubuntu 12.04 LTS Beta 2 (nightly build)

2) aptdaemon: Installiert: 0.43+bzr790-0ubuntu1

The bug was just triggered here by starting the update-manager and after pressing "check for updates".

Just got the bug after a clean testing installation of Lubuntu precise amd64 current daily 20120402.
I was testing another bug on pcmanfm. "Check for updates" got me as well in Update Manager.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/971839

And again here. For me it shows up after a clean installation from the "alternate desktop version 32 bit" of Ubuntu. And it is triggered with every call of the update-manager.

Occurred on clean install of 12.04 beta 2 64-bit. Update Manager generally working but threw this once.

Just got this twice after pressing "Check for updates" once.

The bug will be fixed with the next upload of aptdaemon. Sorry for the trouble.

the bug report says: <<Architecture: amd64>> but I'm running a 32bit System

I'm running a 32bit system too, same prob. Happened after reboot following after update using update manager.
Usually use terminal yo update/upgrade, so not aware if this is a regular occurrence.

me 2

Me. Ubuntu 12.04b2 under Server Hyper-V 2008 R2 SP1.

Ubuntu 12.04 (precise)
3.2.0-21-generic-pae (#34-Ubuntu SMP Thu Mar 29 22:33:16 UTC 2012)
1.11.3 (30 March 2012 01:52:14AM)
Intel(R) Atom(TM) CPU N550 @ 1.50GHz
Intel N10 Asus 1015PEM

Happens at log in /boot up

same like user wilsonb

Crash when opening "system update to date".

Same here. First upgrade was fine, but after checking for updates again error shows up.

happens during installation of y-ppa-manager from getdeb.net

Antoni Kudelski <email address hidden> schrieb:

>Same here. First upgrade was fine, but after checking for updates again
>error shows up.
>
>--
>You received this bug notification because you are a member of
>Aptdaemon
>Developers, which is subscribed to aptdaemon in Ubuntu.
>https://bugs.launchpad.net/bugs/971839
>
>Title:
> aptd crashed with UnboundLocalError in _emit_acquire_item(): local
> variable 'lang' referenced before assignment
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/aptdaemon/+bug/971839/+subscriptions

Hello. There isn't any futher input required. The problem is already located and will be fixed as soon as possible. Cheers, sebastian
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Can confirm. Crashes when I plug in my headphones into the audio jack. (Sound transfers to the headphones as I plug in partially but once the jack is fully inserted in crashes.) Sound mutes with both the speakers and the headphones, but returns to the speakers once the jack is unplugged.

The app report bug didn't come up at first-but I used sudo apt-get upgrade -d to get all updates to install (the kernel packages and a few others).

I'm new to reporting bugs so please provide terminal commands if you want any debugging information.

Bug occurred during an update session. Seems to also occurr after a request to check for updates.

Same as noted above: Bug occurred during an update session. Seems to also occurr after a request to check for updates.

Crashed when searching for new updates. - ubuntu 12.04 beta2

Fix released ? I've updated all packages prior to reboot, then I checked again, boom; crash. So,uhm what fix was that again ? Released ? In thin air maybe.

Hit me just now *after* daily upgrade (a few minutes ago) & (necessary) reboot...

crash when searching for new updates. i can't reproduce it again.
and after upgrade and reboot i can't reproduce it.

This is happening on start-up - 32bit Lubuntu 12.04

This is getting pretty much idiotic, fast. Changing bug status because even after ANOTHER set of updates, it is still not fixed. Dunno who the hell thinks this is STILL FIXED, but I'm telling you: IT ISN'T !

Ждём стабильный выпуск Ubuntu 12.04 64 или 32

Confirmed, the bug is still there.

Проблема с поиском обновлений. Часто появляются ошибки.

Dear Andrei,

You did the right thing by changing the status.

Please refrain from harsh language <3 .

Dear Oleg,

English please :) Pretty please :)

Thanks and Blessings,
Shahar

Please note the difference between the status 'Fix Committed' and 'Fix Released'. 'Fix Committed' simply means that the fix has been identified by the developers and dumped into the source code repository. It does *not* mean that the fix is available via the normal update channels. When a new version of the package with this fix is released via updates, the status will change to 'Fix Released'.

Please also note the difference between the two bug targets: 'Aptdaemon' and 'aptdaemon (Ubuntu)'. 'Aptdaemon' refers to the upstream project, where this bug is 'Fix Released'. This is because upstream has released a new version with the fix for this bug included. 'aptdaemon (Ubuntu)' refers to the version in Ubuntu, which is still only 'Fix Committed' because that new version hasn't yet been included. As per @glatzor's several comments, however, it will be soon.

I received this error shortly after logging in an starting the update manager. I had no other applications running.

I also received this error shortly after logging in.

I was looking for new updates with the selector "gestionnaire de mises à jour" and it finds 208 item

A+

Affects me, more often after in the past two days....!!!

@isoloveyko Please do not change bug statuses without understanding what they mean. This bug should still be 'Fix Committed' in 'aptdaemon (Ubuntu)', as the fixed packaged has not landed in the repository yet.

problem occurs during look up for updates

I just had this issue when running updates.

Still a bug with all updates applied. Fix is apparently no good.

For the record: The FIX IS NOT YET RELEASED in Ubuntu, so any further reports should get redirected to /dev/null, until the fix is really in the repository.

How to fix this problem??

Thank you for the good work ......

Continues to affect my system just by opening update manager..... 12.04 beta2 updated

Same here , problem remains

Same problem since yesterday :)

i dont know.

umh, i just started the update manager and i get this error but i don't see anything failing really? By the time i click confirm there's another error waiting saying it can't open the browser after which firefox opens, seems like a few things are happening at once there, something with timers or priorities or threads ? no actual clue i'm not the leet coder but it looks like that

The bug have just happened again now.

AFAIT, the fix is committed and should be available on updates soon. Great.

Just downloaded the latest fixes. Problem is still happening to me as well. Awaiting FIX!

bug still there

I still have the Bug on Ubuntu 12.04 Beta 2, aptdaemon 0.43+bzr790-0ubuntu1

The program crashed when updating the system. Xubuntu 12.04 x64

I was able to recreate the issue the same as others are reporting:
  1) launched update-manager from terminal
  2) press the check for updates button

this is hapening after larg updates and doses not change day from last update.
the updates load ok

ho win the hell did you give me 64bit when I installed 32 bit for a 386 how in the hell does this take place?????

I am running Kernel 3.3, Gnome 3.4, an ATI video card with a Nvidia one, too on top of Lubuntu 12.04 Beta 2. Its a miracle my computer runs at all.

this is the same junk as you blacklisting folks hardware when Iv'e been using the same comuter with the original wifi once I went to do a repair from one of your servers you black flag 5 things in one comuter that has run ubuntu10,04, 10.10, and the junk natty! and I upgraded too 11.10 fine untill the power out screwed my images beyond repair and I got it to boot using terminal u booted me and then I restarted! whats next? Pig with wings???

@vanillachip01 The bug occurs regardless of whether the computer is 32-bit or 64-bit. Since the original reporter was running 64-bit, that's how the bug was filed. Your other comments are not constructive. If you have issues you want to take up with the community, I suggest the ubuntu-devel-discuss mailing list [1], as this bug report is not the place.

To everyone else: there is no need to comment on this bug anymore. The fix has been identified and will be released shortly. No further information is needed, so please stop commenting with "Me too" messages - they only create noise.

[1] https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

---
Ubuntu Bug Squad Volunteer
https://wiki.ubuntu.com/BugSquad

First I woke up the computer, I updated system using terminal (apt-get update+apt-get upgrade). Restart. Log in. Crashed. Report.
Otherwise - no problems. Crushing daemon did not crush the system.

Processor: AMD Athlon(tm) II X2 245 Processor × 2
OS Type: 32-bit

It seems to happen on the upgrades. I did two fresh installs to friend's computers and I don't believ they had this issue.

THE FIX HAS BEEN COMMITTED AND WILL BE RELEASED SOON. THERE IS NO NEED TO FILE A BUG REPORT ANYMORE.
THANK YOU.

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

@j-jose1197 Please don't change the bug status unless you know what it means. The correct status for this bug is "Fix Committed" in "aptdaemon (Ubuntu)" and "Fix Released" in "Aptdaemon".

it is still a problem even after update. the fix was not a fix it just was an epic fail.

@jmate31 The fix has not been released yet, but it will be released soon (probably on April 10th). Please be patient until then.

The problem is still there. I just installed Ununtu 12.04 on a brand new computer and the bug appeared after I checked Ununtu partners in sources list and applied an update.

This should not be marked as Fix Released in aptdaemon (Ubuntu). The patch hasn't appeared downstream yet.

crash reported on system restart after updating today.

It crashed by itself, it starts to be annoying since the system was idle...

very annoying bug

 How can a fix, in a nimble open-source world, take so long to "reach the servers"? Are we using 300 baud modems on the backend? The bug reports won't stop just cuz you ask when you won't release the fix.

I'm having this problem testing Precise Pangolin Beta 2 with all updates installed.

Description: Ubuntu precise (development branch)
Release: 12.04
aptdaemon:
  Installed: 0.43+bzr790-0ubuntu1
  Candidate: 0.43+bzr790-0ubuntu1
  Version table:
 *** 0.43+bzr790-0ubuntu1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

Still there today. I will eat worms until the 10th.

I think you can fix it manually (if you still haven't got the update) by replacing second "lang" (without quotes) with "lang_code" (again, without quotes) in line 342 of /usr/lib/python2.7/dist-packages/aptdaemon/progress.py. Additionally, you will need to replace "country" with "region" in line 349 to prevent another crash.

Occurred just after boot-up. no other programs running.

I cleared /var/crash/* to make sure am not reporting the same bug again and again but keeps appearing over and over.....

Had just booted, selected HOME folder, send a .DEB object to trash, and then it produced the error.

got this error while booting the system

Please do not change the status/assignment of this bug unless you know what you are doing.

not solved

Why delay the release if a fix is already commited? Seems silly to keep bug reports pouring in and people's systems giving errors for no reason.

not solved

Sorry, new system for me, will not send any more bug reports.
Am 08.04.2012 21:25 schrieb "PatrickSCarrroll" <email address hidden>:

> Why delay the release if a fix is already commited? Seems silly to keep
> bug reports pouring in and people's systems giving errors for no reason.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/971839
>
> Title:
> aptd crashed with UnboundLocalError in _emit_acquire_item(): local
> variable 'lang' referenced before assignment
>
> Status in Aptdaemon:
> Fix Released
> Status in “aptdaemon” package in Ubuntu:
> Fix Committed
>
> Bug description:
> IMPORTANT
> ---
> Please do not change the status of this bug unless you know what you are
> doing.
>
> The fix for this bug has already been identified and will be released
> soon. There is no need to comment if you only wish to say that you're
> still experiencing this bug.
>
> I expect the fix to be released on Tuesday, the 10th of April.
> ---
>
> Ubuntu 12.04 Beta 2 64 bit
> Error happened after upgrade,
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: aptdaemon 0.43+bzr790-0ubuntu1
> ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
> Uname: Linux 3.2.0-21-generic x86_64
> ApportVersion: 2.0-0ubuntu2
> Architecture: amd64
> CrashCounter: 1
> Date: Mon Apr 2 20:32:47 2012
> DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
> ExecutablePath: /usr/sbin/aptd
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64
> (20120328)
> InterpreterPath: /usr/bin/python2.7
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/sbin/aptd
> ProcEnviron:
>
> PythonArgs: ['/usr/sbin/aptd']
> SourcePackage: aptdaemon
> Title: aptd crashed with UnboundLocalError in _emit_acquire_item(): local
> variable 'lang' referenced before assignment
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/aptdaemon/+bug/971839/+subscriptions
>

Sorry, new system for me, will not send any more reports. But some kind
should it go already. Regards
Am 08.04.2012 21:25 schrieb "PatrickSCarrroll" <email address hidden>:

> Why delay the release if a fix is already commited? Seems silly to keep
> bug reports pouring in and people's systems giving errors for no reason.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/971839
>
> Title:
> aptd crashed with UnboundLocalError in _emit_acquire_item(): local
> variable 'lang' referenced before assignment
>
> Status in Aptdaemon:
> Fix Released
> Status in “aptdaemon” package in Ubuntu:
> Fix Committed
>
> Bug description:
> IMPORTANT
> ---
> Please do not change the status of this bug unless you know what you are
> doing.
>
> The fix for this bug has already been identified and will be released
> soon. There is no need to comment if you only wish to say that you're
> still experiencing this bug.
>
> I expect the fix to be released on Tuesday, the 10th of April.
> ---
>
> Ubuntu 12.04 Beta 2 64 bit
> Error happened after upgrade,
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: aptdaemon 0.43+bzr790-0ubuntu1
> ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
> Uname: Linux 3.2.0-21-generic x86_64
> ApportVersion: 2.0-0ubuntu2
> Architecture: amd64
> CrashCounter: 1
> Date: Mon Apr 2 20:32:47 2012
> DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
> ExecutablePath: /usr/sbin/aptd
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64
> (20120328)
> InterpreterPath: /usr/bin/python2.7
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/sbin/aptd
> ProcEnviron:
>
> PythonArgs: ['/usr/sbin/aptd']
> SourcePackage: aptdaemon
> Title: aptd crashed with UnboundLocalError in _emit_acquire_item(): local
> variable 'lang' referenced before assignment
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/aptdaemon/+bug/971839/+subscriptions
>

Still getting this error, so it hasn't been fixed yet.

Ah, nevermind. I see it has only been committed and not released.

Crashes immediately after a fresh login into a Unity session.

Happened to me first time while attempting an update through update manager on 12.04 32 bit.

Crashes immediately after a fresh login.

aptdaemon:
  Installerad: 0.43+bzr790-0ubuntu1
  Kandidat: 0.43+bzr790-0ubuntu1
  Versionstabell:
 *** 0.43+bzr790-0ubuntu1 0
        500 http://se.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

tried to update the system after restart and got this error

Updating with updated manager and in the same time, looking at mail with Mozilla Firefox.
32bit version with portable pc HP DV7 2220 sf
A+

After the initial crash, it can reliable be reproduced when rm _usr_sbin_aptd.0.crash file from /var/crash.
After removal of .crash file either run update-manager in a terminal or via dash.
Click the check-button results in apport report.
syslog says:
AptDaemon: CRITICAL: Another daemon is already running

I`m look this error after updating in update-manager.
ubuntu 12.04

Pops up on every login.

Some people should really learn to read before they start to write... 8/

<quote>
IMPORTANT
---
Please do not change the status of this bug unless you know what you are doing.

The fix for this bug has already been identified and will be released soon. There is no need to comment if you only wish to say that you're still experiencing this bug.

I expect the fix to be released on Tuesday, the 10th of April.
</quote>

got this error while trying to install adobe flash plugin through software center.

Problem happened before and after upgrade..
System if important: intel core2duo quad 2.3 Mhz ( Q 8200 ), ATI 6770 Grafikcard, Asus MB p5g41t-m lx

It will be helpful guys, if you insert references to closing commits here. My subjective opinion after 12.04 switch that this update architecture is rather crappy and it would be nice to see if it is at least can be covered by tests.

Still happening fairly consistently..

It happened directly after restart. I did only start firefox and thunderbird ... nothing else. All current updates are installed.

Crashed when Update-Manager is running.

totally updated precise
happened when was downloading in Software Center

Hello!
Make sure that when it is stated, it's 64 bit version that has problems. I'm running i386 (32 bit) version and have similar problem.
Dimonen fails for no apparent reason even though the system was idle.
Anders

i dont know.

stop reopening the bug. and this is also no discussion forum. go somewhere else. © Ulrich Drepper

Interesting. I am not receiving this crash anymore when checking for updates (with the latest updates installed), but the package was updated in Ubuntu 8 days ago. Can anybody else please confirm that this crash is no longer occurring?

Had just booted, selectet updatemanager and then it produced the error.

Just updated, rebooted and upon login selected "Software Up To Date" from login menu. Got error when updatemanager opened up.

Still getting this error after today's update fix

Still getting this error after today's update.

It's 10th April, and I still got the same error.
Isn't there a way of knowing what package should've been installed for this bug to go away?
I don't know if the update has been pushed yet.

getting this error when trying to update from source center in ubuntu tweak

i don't know whether or not it is the same bug , but whenever i click on "report" crash , it points to this bug, and i have updated my system and there was never a problem while updating, but my system frequently gets halted after the signing in dialog , and it is still happening even after installing all the updates, it is xubuntu 12.04 beta2 amd64.

I face the same issue. Whenever i click on "report" crash , it points to this bug, and i have updated my system.

I tried to update and I got this same for me as well but two times report request came. This is first. for second I'm attaching screen shot.

happens after I login in to system for 1st time.

This will be fixed in this version of aptdaemon:

aptdaemon (0.43+bzr805-0ubuntu1) precise;

Occured for me while installing from Software Center. Beta 2, 32bit, clean install, fully updated at the time of this comment.

Humm,

Synaptic shows version 0.43+bzr805-0ubuntu1 after my last update was installed and the issue is still there.

Question; Is there a way to reliably get an update to this issue? Seriously, I knew girls in school that didn't tease as much about being able to get it. It's commited, It's released, it's commited, Etc.

came after fixed released, did not work. Crashed when checking for updates.

aptdaemon (0.43+bzr805-0ubuntu1) precise; urgency=low
  - Fix wrong variable names in the download progress (fixes LP: #971839,
      LP: #976521)

Am Mittwoch, den 11.04.2012, 00:39 +0000 schrieb Ernest Kudron:
> came after fixed released, did not work. Crashed when checking for
> updates.

Please make sure that the latest version of aptdaemon has been installed
(0.43+805). If you are not downloading from the main archive it can take
some time before your download mirror has been updated and provides the
latest version of aptdaemon.

Furthermore please close software-center and wait more than 5 minutes.
Aptdaemon will shutdown and the new version will be started the next
time.

After update the problem seems to be fixed, thanks!

I did however also threw away neglected crash reports from /var/crash, probably not necessary but cleans up so nicely :)

Lubuntu 12.04

Happened during update using Update Manager

Just happened again after upgrading (on main servers) at 12:32 CET on monday 12/04/2012.
Aptdaemon package version is 0.43+bzr805-0ubuntu1

Could someone remind me how long after fix-released status does the fix show up in a normal apt-get upgrade?

Thanks!

@ronsteed-o Depends on how long the change takes to build and propagate to whichever mirror your using. The change is already on the main (Canonical-hosted) mirror, so most other mirrors shouldn't be far behind. Note that the bug may appear one more time after applying the fix if you still have an old apt-daemon instance running. Restarting aptdaemon after updating will clear it.

I just want to report that I just updated five minutes ago, rebooted, immediately got the System Error popup after logging in, clicked to report this bug, and it sent me here. So, if the fix has been released, I didn't get it.

Actually, manually restarting apt-daemon immediately brings up the following error and bug report: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/450662 ,but that doesn't affect normal use.

Upon rebooting, the former bug is fixed, and I suppose the latter is not important. So, thanks.

Am Donnerstag, den 12.04.2012, 14:29 +0000 schrieb Ron Steed:
> Could someone remind me how long after fix-released status does the fix
> show up in a normal apt-get upgrade?

https://launchpad.net/ubuntu/+archivemirrors

After update, rebooted and once desktop showed, immediately system error occured.

Same as everyone else..

Also using 0.43+bzr805-0ubuntu1 of the aptdaemon. Shortly after logging in, crash occurs on OS starting an automatic update. Same error pops up while running updater.

ii aptdaemon 0.43+bzr805-0ubuntu1

After update, rebooted and once desktop showed, immediately system error occured.

still seeing it on 4/18 after freshly updating

I seem to have gotten it just now. just after upgrading. If i can help in any way, please let me know.