mythbuntu-control-centre failed to start

Bug #1108552 reported by Jason Cullen
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
Fix Released
Undecided
Unassigned
mythbuntu-control-centre (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When trying to start this on Ubuntu 13.04 I get this:

Traceback (most recent call last):
  File "/usr/bin/mythbuntu-control-centre", line 38, in <module>
    from aptdaemon import client
  File "/usr/lib/python2.7/dist-packages/aptdaemon/client.py", line 55, in <module>
    class AptTransaction(GObject.Object):
AttributeError: 'module' object has no attribute 'Object'

Jason Cullen (jcullen86)
description: updated
Revision history for this message
Mario Limonciello (superm1) wrote :

Looking at that callback, I suspect that's actually an aptdaemonbug.

Changed in mythbuntu-control-centre (Ubuntu):
status: New → Invalid
Revision history for this message
Rob Fargher (fargher-gmail) wrote :

Just did a fresh install of Raring and did a dist-upgrade. I get the same result as reported above.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in aptdaemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Rob Fargher (fargher-gmail) wrote :

Removing aptdaemon still gives the same result.

Revision history for this message
Sebastian Heinlein (glatzor) wrote : Re: [Bug 1108552] Re: mythbuntu-control-centre failed to start

mythubuntu control center uses the ancient python gtk2 bindings. Are
there any plans to go for python3, gtk3 and gobject introspection?

We broke backwards compatibility in aptdaemon. I will try to restore
it.

Revision history for this message
Mario Limonciello (superm1) wrote :

Would like to, there are some other modules that need to come to python3 to be able to do that. Looks like some of them still haven't made it to raring.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package aptdaemon - 1.0-0ubuntu1

---------------
aptdaemon (1.0-0ubuntu1) raring; urgency=low

  * New stable bug fix release 1.0:
    - Add PEP8 compliance and a corresponding test
    - Fix PackageKit tests if an http proxy is set (LP: #1050799)
    - Fix crash for Python GTK2 clients (LP: #1108552)
    - Fix crash if configuration file changes are only one line long -
      thanks to Barry Warsaw and Robert Collins (LP: #1120322)
    - Fix crash if the removal of a package valid candidate is simulated
    - Allow repository release names to include dots
    - Convert aptdaemon exceptions to PackageKit ones in the compat
      layer (currently only invalid input ant failed authorization are
      supported)
    - Store the default values in the PackageKit transaction interface
      statically typed
    - Fix setting the speed property in the PackageKit interface
    - Several grammar and typo fixes in user interface messages and
      documentation (LP: #1112492)
  * debian/patches:
    - fix-high-trust-pkcompat.diff: updated
    - apt-dbus-text-api.patch: updated
    - fix-gobject-io-add-watch.patch: Added. Always include the priority
      in a GLib.io_add_watch() call to not cause problems with the backwards
      compatibility

  [ Barry Warsaw ]
  * debian/control:
    - Add Build-Depend on gir1.2-gnomedesktop-3.0, gir1.2-vte-2.90, pep8,
      and xvfb.
    - Bump Standards-Version to 3.9.4.
  * debian/rules: Run the tests under xvfb-run to avoid core dumps.
  * debian/patches/pep8-fixes.patch: Fix PEP 8 violations.
  * debian/patches/lp1153725-temporary-workaround.patch: Temporarily
    disable two tests which fail during the build.
  * debian/rules:
    - Add the missing test directory and symlinks before running tests.
    - Clean up symlink directory in override_dh_auto_clean.
    - Sleep before the xvfb-run with a different Python version. Tear
      down of xvfb-run resources is apparently not immediate.
 -- Sebastian Heinlein <email address hidden> Mon, 11 Mar 2013 07:02:07 +0100

Changed in aptdaemon (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Rob Fargher (fargher-gmail) wrote :

Bug is not fixed in Raring.

Traceback (most recent call last):
  File "/usr/bin/mythbuntu-control-centre", line 40, in <module>
    from aptdaemon.gtkwidgets import (AptErrorDialog,
ImportError: cannot import name AptMessageDialog

Changed in mythbuntu-control-centre (Ubuntu):
importance: Undecided → Critical
milestone: none → ubuntu-13.04
status: Invalid → Triaged
Changed in aptdaemon (Ubuntu):
status: Fix Released → Invalid
status: Invalid → Fix Released
Changed in mythbuntu-control-centre (Ubuntu):
status: Triaged → Invalid
importance: Critical → Undecided
milestone: ubuntu-13.04 → none
Revision history for this message
Sebastian Heinlein (glatzor) wrote :

Sorry, for the noise on this bug. Perhaps it is too early in the morning here :)

The new issue that you see Rob is the fault of control center. It imports (but never uses) a deprecated widget from aptdaemon that was removed in the 1.0 release.

See LP #1158117 for details and a fix.

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.