Ubuntu
aptdaemon package

aptd crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.AccessDenied: Connection ":1.58" is not allowed to own the service "org.debian.apt" due to security policies in the configuration file

Bug #715819 reported by prabhakar pujeri on 2011-02-09

This bug report is a duplicate of: Bug #450662: DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.63" is not allowed to own the service "org.debian.apt" due to security policies in the configuration file. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	aptdaemon (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: aptdaemon

app crashing

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.40+bzr541-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Wed Feb 9 14:50:27 2011
ExecutablePath: /usr/sbin/aptd
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:
LANGUAGE=en_US.UTF-8:en
LANG=en_US.UTF-8
LC_MESSAGES=en_AG.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/sbin/aptd']
SourcePackage: aptdaemon
Title: aptd crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.AccessDenied: Connection ":1.58" is not allowed to own the service "org.debian.apt" due to security policies in the configuration file
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

prabhakar pujeri (prabhakar-pujeri) wrote on 2011-02-09:

Traceback.txt Edit (835 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-02-09: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #450662, 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.