Regression: Cannot install signatures in Utopic any more

Bug #1340830 reported by Till Kamppeter
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
Invalid
Undecided
Unassigned
packagekit (Ubuntu)
New
Undecided
Unassigned

Bug Description

In the script /usr/share/system-config-printer/install-printerdriver.py I use package kit to add a repository to install printer driver packages, install the signature for te repository and finally install the driver package from the repository, to get a secure installation and the system's update facility also updating my printer driver package if an update gets available.

Under Trusty this works correctly, but under Utopic it stopped working.

Under Utopic I get the following if I run the Python statements of the script one by one at the Python prompt:

----------
till@till-twist:~$ python
Python 2.7.7 (default, Jun 4 2014, 05:21:28)
[GCC 4.8.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from gi.repository import GLib, PackageKitGlib
>>> import sys
>>> def progress(progress, type, user_data):
... pass
...
>>> repo_gpg_id = "E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56"
>>> pk = PackageKitGlib.Client()
>>> res = pk.install_signature(PackageKitGlib.SigTypeEnum.GPG, repo_gpg_id, '', None, progress, None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
GLib.Error: g-dbus-error-quark: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 (25)
>>>
----------

The signature key is from Epson. I also tried with the key

F8897B6F00075648E248B7EC24CBF5474CFD1E2F

from OpenPrinting and got the same result.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Sorry, on my system there was for some reason, perhaps some experiments several months ago, installed the original PackageKit D-Bus service ("packagekit" binary package) and not the Ubuntu standard PackageKit D-Bus service emulation using aptdaemon ("python3-aptdaemon.pkcompat" binary package). aptdaemon was installed, giving me the impression that it was used.

This caused the bug to occur and after returning to the standard setup with python3-aptdaemon.pkcompat the bug went away.

So the bug is most probably in the packagekit package and most users are still having automatic printer driver installation working, so closing aptdaemon task ...

Changed in aptdaemon (Ubuntu):
status: New → Invalid
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.