update-manager crashed with aptdaemon.errors.AptDaemonError in commit(): org.debian.apt: kinit#auto isn't a valid package name

Bug #1505337 reported by Brian Murray
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Triaged
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
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 12 11:12:57 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'626'
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'window-width' b'605'
 b'com.ubuntu.update-manager' b'launch-time' b'1444673564'
InstallationDate: Installed on 2013-01-16 (999 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/zsh
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with aptdaemon.errors.AptDaemonError in commit(): org.debian.apt: kinit#auto isn't a valid package name
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Brian Murray (brian-murray) wrote :
tags: removed: need-duplicate-check
Changed in update-manager (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Brian Murray (brian-murray) wrote :

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

Revision history for this message
Brian Murray (brian-murray) wrote :

Here's the Traceback:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 89, in commit
    downgrade, defer=True)
aptdaemon.errors.AptDaemonError: org.debian.apt: kinit#auto isn't a valid package name

Revision history for this message
Brian Murray (brian-murray) wrote :

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
Revision history for this message
Brian Murray (brian-murray) wrote :

The Error Tracker has a bucket with similar crashes:

https://errors.ubuntu.com/problem/7ebdd3a47a22b40385f9eb92e6a329765708cf19

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/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 89, in commit
    downgrade, defer=True)
aptdaemon.errors.AptDaemonError: org.debian.apt: TrickPit isn't a valid package name

Revision history for this message
Brian Murray (brian-murray) wrote :

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_id(fullname)
2072 name, sep, auto_flag = name.partition("#")
2073 if not auto_flag in ("", "auto"):
2074 raise errors.AptDaemonError("%s isn't a valid flag" %
2075 auto_flag)
2076 if not re.match(REGEX_VALID_PACKAGENAME, name):
2077 raise errors.AptDaemonError("%s isn't a valid package name" %
2078 name)

Revision history for this message
Brian Murray (brian-murray) wrote :
Download full text (3.1 KiB)

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-aptdaemon.pkcompat_1.1.1+bzr982-0ubuntu13_all.deb ...
Unpacking python3-aptdaemon.pkcompat (1.1.1+bzr982-0ubuntu13) over (1.1.1+bzr982-0ubuntu12) ...
Preparing to unpack .../python3-aptdaemon.gtk3widgets_1.1.1+bzr982-0ubuntu13_all.deb ...
Unpacking python3-aptdaemon.gtk3widgets (1.1.1+bzr982-0ubuntu13) over (1.1.1+bzr982-0ubuntu12) ...
Preparing to unpack .../aptdaemon_1.1.1+bzr982-0ubuntu13_all.deb ...
Unpacking aptdaemon (1.1.1+bzr982-0ubuntu13) over (1.1.1+bzr982-0ubuntu12) ...
Preparing to unpack .../python3-aptdaemon_1.1.1+bzr982-0ubuntu13_all.deb ...
Unpacking python3-aptdaemon (1.1.1+bzr982-0ubuntu13) over (1.1.1+bzr982-0ubuntu12) ...
Processing triggers for dbus (1.10.0-1ubuntu1) ...
Processing triggers for man-db (2.7.3-1) ...
Setting up python3-aptdaemon (1.1.1+bzr982-0ubuntu13) ...
Setting up python3-aptdaemon.pkcompat (1.1.1+bzr982-0ubuntu13) ...
Setting up python3-aptdaemon.gtk3widgets (1.1.1+bzr982-0ubuntu13) ...
Setting up aptdaemon (1.1.1+bzr982-0ubuntu13) ...
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.apt[1349]: 11:09:23 AptDaemon [INFO]: Initializing daemon
Oct 12 11:09:23 impulse AptDaemon.PackageKit[7097]: INFO: Initializing PackageKit compat layer
Oct 12 11:09:23 impulse org.debian.apt[1349]: 11:09:23 AptDaemon.PackageKit [INFO]: Initializing PackageKit compat layer
Oct 12 11:09:23 impulse AptDaemon[7097]: INFO: UpdateCache() was called
Oct 12 11:09:23 impulse org.debian.apt[1349]: 11:09:23 AptDaemon [INFO]: UpdateCache() was called
...........
Oct 12 11:12:45 impulse org.debian.apt[1349]: 11:12:45 AptDaemon.Worker [INFO]: Updating cache
Oct 12 11:12:49 impulse AptDaemon.Worker[7097]: INFO: Finished transaction /org/debian/apt/transaction/458231a0ba3346518ce0f4c60fff50ee
Oct 12 11:12:49 impulse org.debian.apt[1349]: 11:12:49 AptDaemon.Worker [INFO]: Finished transaction /org/debian/apt/transaction/458231a0ba3346518ce0f4c60fff50ee
Oct 12 11:12:57 impulse AptDaemon[7097]: INFO: CommitPackages() was called: dbus.Array([dbus.String('kinit#auto'), ...

So this th...

Read more...

Changed in update-manager (Ubuntu):
status: New → Triaged
Revision history for this message
syscon-hh (syscon-kono) wrote :

The Traceback on our computer differ to #3 as following, see last line:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 65, in update
    trans = yield self.client.update_cache(defer=True)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying

Revision history for this message
Chrescht (sekateur) wrote :

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/python3/dist-packages/defer/__init__.py", line 483, in _inline_callbacks
    result = gen.throw(excep)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 65, in update
    trans = yield self.client.update_cache(defer=True)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.