update-manager crashed with aptdaemon.errors.AptDaemonError in commit(): org.debian.apt: kinit#auto isn't a valid package name
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | update-manager (Ubuntu) |
Medium
|
Unassigned | ||
Bug Description
This is likely due to the fix for LP: #1439769.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: update-manager 1:15.10.3
ProcVersionSign
Uname: Linux 4.2.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 12 11:12:57 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2013-01-16 (999 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
InterpreterPath: /usr/bin/python3.4
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
PATH=(custom, user)
SHELL=/bin/zsh
LANG=en_US.UTF-8
LANGUAGE=en_US
XDG_RUNTIME_
PythonArgs: ['/usr/
SourcePackage: update-manager
Title: update-manager crashed with aptdaemon.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
| Brian Murray (brian-murray) wrote : | #1 |
| tags: | removed: need-duplicate-check |
| Changed in update-manager (Ubuntu): | |
| importance: | Undecided → Medium |
| Brian Murray (brian-murray) wrote : | #2 |
| Brian Murray (brian-murray) wrote : | #3 |
Here's the Traceback:
Traceback (most recent call last):
File "/usr/lib/
result = gen.throw(excep)
File "/usr/lib/
downgrade, defer=True)
aptdaemon.
| Brian Murray (brian-murray) wrote : | #4 |
I was able to upgrade my laptop without an issue and packages also contained the #auto tag, so I'm not certain what went wrong here.
| information type: | Private → Public |
| Brian Murray (brian-murray) wrote : | #5 |
The Error Tracker has a bucket with similar crashes:
https:/
As expected only the 15.10 crashes contain #auto part. A report from 15.04 contains the following error:
Traceback (most recent call last):
File "/usr/lib/
result = gen.throw(excep)
File "/usr/lib/
downgrade, defer=True)
aptdaemon.
| Brian Murray (brian-murray) wrote : | #6 |
The aptdaemon changes look complete and before the valid package name check we can see the auto_flag tag is stripped.
2070 for fullname in pkg_names:
2071 name, version, release = split_package_
2072 name, sep, auto_flag = name.partition("#")
2073 if not auto_flag in ("", "auto"):
2074 raise errors.
2075 auto_flag)
2076 if not re.match(
2077 raise errors.
2078 name)
| Brian Murray (brian-murray) wrote : | #7 |
Speaking to mvo about this he believes its possible that update-manager and aptdaemon were updated but that the running aptdaemon was not replaced with the new version of aptdaemon. Subsequently, the flag was passed to aptdaemon and it didn't know how to handle it.
Looking at the Aptdaemon.txt attachment in this bug report we can see the same process id used for aptdaemon even after the package is upgraded.
Log started: 2015-10-12 11:10:01
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 870936 files and directories currently installed.)
Preparing to unpack .../python3-
Unpacking python3-
Preparing to unpack .../python3-
Unpacking python3-
Preparing to unpack .../aptdaemon_
Unpacking aptdaemon (1.1.1+
Preparing to unpack .../python3-
Unpacking python3-aptdaemon (1.1.1+
Processing triggers for dbus (1.10.0-1ubuntu1) ...
Processing triggers for man-db (2.7.3-1) ...
Setting up python3-aptdaemon (1.1.1+
Setting up python3-
Setting up python3-
Setting up aptdaemon (1.1.1+
Log ended: 2015-10-12 11:10:06
Oct 12 11:09:23 impulse AptDaemon[7097]: INFO: Initializing daemon
Oct 12 11:09:23 impulse org.debian.
Oct 12 11:09:23 impulse AptDaemon.
Oct 12 11:09:23 impulse org.debian.
Oct 12 11:09:23 impulse AptDaemon[7097]: INFO: UpdateCache() was called
Oct 12 11:09:23 impulse org.debian.
...........
Oct 12 11:12:45 impulse org.debian.
Oct 12 11:12:49 impulse AptDaemon.
Oct 12 11:12:49 impulse org.debian.
Oct 12 11:12:57 impulse AptDaemon[7097]: INFO: CommitPackages() was called: dbus.Array(
So this th...
| Changed in update-manager (Ubuntu): | |
| status: | New → Triaged |
| syscon-hh (syscon-kono) wrote : | #8 |
The Traceback on our computer differ to #3 as following, see last line:
Traceback (most recent call last):
File "/usr/lib/
result = gen.throw(excep)
File "/usr/lib/
trans = yield self.client.
dbus.exceptions
| Chrescht (sekateur) wrote : | #9 |
Am getting the same when running "ubuntu-manager -d", then trying to update to Ubuntu 16.04.
Traceback (most recent call last):
File "/usr/lib/
result = gen.throw(excep)
File "/usr/lib/
trans = yield self.client.
dbus.exceptions


It looks like kinit was being installed for the first time on my system:
2015-10-12 11:16:44 install kinit:amd64 <none> 5.15.0-0ubuntu1
2015-10-12 11:16:44 status half-installed kinit:amd64 5.15.0-0ubuntu1
2015-10-12 11:16:44 status unpacked kinit:amd64 5.15.0-0ubuntu1
2015-10-12 11:16:44 status unpacked kinit:amd64 5.15.0-0ubuntu1