Ubuntu
zeitgeist package

zeitgeist-daemon crashed in middle of Software update center)

Bug #815542 reported by John Fancher on 2011-07-24

This bug report is a duplicate of: Bug #807950: zeitgeist-daemon crashed with LookupError in remove_from_connection(): <_zeitgeist.engine.remote.RemoteInterface at /org/gnome/zeitgeist/log/activity at 0xb74ee2cc> is not exported at a location matching (None,None). Edit Remove

This bug affects 1 person

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

Bug Description

Was running Software update and this zeitgeist crash occurred. Software update was checking for new updates.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: zeitgeist-core 0.8.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux 3.0.0-6-generic x86_64
Architecture: amd64
Date: Sun Jul 24 15:04:05 2011
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with LookupError in remove_from_connection(): <_zeitgeist.engine.remote.RemoteInterface at /org/gnome/zeitgeist/log/activity at 0x7f47c07f9890> is not exported at a location matching (None,None)
UpgradeStatus: Upgraded to oneiric on 2011-07-24 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

John Fancher (fancherjw) wrote on 2011-07-24:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-24: 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 #807950, 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.