apturl-gtk crashed with AttributeError in __init__(): 'InstallBackendAptdaemon' object has no attribute 'connect'

[Manish-Raj]

I tried to open an apt url link ( apt:adobe-flashplugin?channel=$distro-partner ) using firefox browser from adobe website ( http://get.adobe.com/flashplayer/ ) in apturl and it crashed.

manish@SR1931IL:~$ lsb_release -rd
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
manish@SR1931IL:~$ apt-cache policy apturl
apturl:
  Installed: 0.5.2ubuntu1
  Candidate: 0.5.2ubuntu1
  Version table:
 *** 0.5.2ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apturl 0.5.2ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Sat Jul 13 10:40:57 2013
ExecutablePath: /usr/bin/apturl-gtk
InstallationDate: Installed on 2013-03-15 (119 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/apturl-gtk apt:adobe-flashplugin?channel=$distro-partner
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/apturl-gtk', 'apt:adobe-flashplugin?channel=$distro-partner']
SourcePackage: apturl
Title: apturl-gtk crashed with AttributeError in __init__(): 'InstallBackendAptdaemon' object has no attribute 'connect'
UpgradeStatus: Upgraded to saucy on 2013-07-03 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Launchpad Janitor (janitor)]

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

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1200775, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.