aptd crashed with AttributeError in _inline_callbacks()

Bug #639616 reported by Chris
276
This bug affects 60 people
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
Confirmed
High
Michael Vogt

Bug Description

Binary package hint: aptdaemon

Cause not known, just spotted the crash report

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: aptdaemon 0.31+bzr496-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Uname: Linux 2.6.35-21-generic i686
Architecture: i386
Date: Wed Sep 15 15:24:18 2010
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:

PythonArgs: ['/usr/sbin/aptd']
SourcePackage: aptdaemon
Title: aptd crashed with AttributeError in _inline_callbacks()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.6/dist-packages/aptdaemon/defer.py", line 550, in _inline_callbacks
     result = gen.send(result)
 AttributeError: 'NoneType' object has no attribute 'send'
UserGroups:

Revision history for this message
Chris (cjbarrow) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Sebastian Heinlein (glatzor) wrote :

This should be fixed in the latest release of aptdaemon. (503).

Changed in aptdaemon (Ubuntu):
status: New → Fix Released
visibility: private → public
Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

Description: Ubuntu precise (development branch)
Release: 12.04

aptdaemon:
  Installato: 0.43+bzr805-0ubuntu1
  Candidato: 0.43+bzr805-0ubuntu1
  Tabella versione:
 *** 0.43+bzr805-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

Revision history for this message
dino99 (9d9) wrote :

Seems that apport take care only of the beginning of the error message :

it identify:
- aptdaemon crashed with AttributeError in _inline_callbacks()
- but ignore the end of the error : 'NoneType' object has no attribute 'send'

and does not care about "fix released" field (at least for this package)

Revision history for this message
Nicolas LE BAS (1gkq) wrote :

Definitely occurring on 12.04 beta (Precise - aptdaemon 0.43+bzr805-0ubuntu1) with slightly different line numbers:

Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/defer/__init__.py", line 475, in _inline_callbacks
     result = gen.send(result)
 AttributeError: 'NoneType' object has no attribute 'send'

attaching the full crash report.

Revision history for this message
Nicolas LE BAS (1gkq) wrote :

full crash report

Revision history for this message
simon (mrmoor4) wrote :

this bug occours in ubuntu 12.04 Beta 2.
It happens by opening the software center.

Christian Reis (kiko)
Changed in aptdaemon (Ubuntu):
status: Fix Released → Confirmed
importance: Undecided → Critical
importance: Critical → High
milestone: none → ubuntu-12.04.1
Revision history for this message
Raimund Sacherer (hatrix) wrote :

Hello, this happens in 12.04 Release to!

dino99 (9d9)
tags: added: precise
Revision history for this message
marco python (marco-python-x) wrote :

Error message occurs on fresh installed 12.04-release without any user actions (just after boot).

Revision history for this message
marco python (marco-python-x) wrote :

Also occurs on software center start.

Revision history for this message
Nick (nick222-yandex) wrote :

Also on update-manager start.

Martin Pitt (pitti)
Changed in aptdaemon (Ubuntu):
assignee: nobody → Michael Vogt (mvo)
Revision history for this message
Fabien Tassin (fta) wrote :

looks similar to bug 971748, for which i provided more information.
Please dupe one if needed.

Revision history for this message
John Coulthard (retired) wrote :

This occurs at startup for my 12.04 system. Part of the reporting procedure has a checkbox for "ignore future problems of this type". Do the maintainers prefer I continue to report it for as long as it keeps happening?

Revision history for this message
Ted Bodfish (tedbs) wrote :

12.04 Desktop - no problems - installed latest updates - reboot required. After reboot, ubuntu waits (twice) for networking, then starts without NetworkManager and this problem occurs. Rebooted again, same wait for networking and this problem still occurs.

Revision history for this message
joherrer (joherrer) wrote :

I've been having same syntomps as Ted Bodfish, since installing updates last week (I'm not sure if May 31st or June 1st).
My Precise is installed on a desktop, with a Nvidia GEForce 3700 video card, AMD processor.

Revision history for this message
Manjul Apratim (manzdagratiano) wrote :

Fresh install of Precise amd64 here with the same issue... I have not looked at the code for aptd or anything, but IMHO, it smells of a Python2 -> Python3 transition issue?

Revision history for this message
David Svarrer (david-t-svarrer) wrote :

Dearest Canonical,

First and foremost - this is my first time to report anything with Ubuntu, and I only do it because the system asked me to comment. I am a developer of software for 31 years, and have worked under Linux, Java, MySQL, since 1999. I run a college (owner) in Kenya, called Digital Age Institute, the top most college in Software Development in Africa, in which capacity I was requested to comment on this bug :-).

Thanks guys, for Ubuntu. It is a gift to the world. No jokes. It is a gift. Secondly - in professional regards to this particular error, I did not know that it happened. I would guess that it is related to the only activity I did last week - namely installing an Adobe plug in.

Have a wonderful day, dear developers of Ubuntu. Great job. If we can contribute to the development, I would appreciate if you can give us guide lines - we have more than 700 students who have graduated yet - all of them in Ubuntu, Java, MySql - and professional software development disciplines.

Warmly
David Svarrer
Digital Age Institute Ltd.
+254 786 936 145
<email address hidden>

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.