zeitgeist-daemon crashed with LookupError in remove_from_connection(): <_zeitgeist.engine.remote.RemoteInterface at /org/gnome/zeitgeist/log/activity at 0xb72e61ac> is not exported at a location matching (None,None)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| zeitgeist (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Crash encountered when try to adjust the screen resolution. Using Ubuntu 11.10 Alpha 2 PC X86 edition on VirtualBox. What's more, I have been successful on installing the Virtualbox graphics driver but after I installed it, the screen refreshed when I click the mouse. Then I upgraded the system to the newest and I found that the resolution dropped to what it had been when I didn't install the driver. I found that the driver wasn't activated and that when I tried to activate it, it couldn't be installed. I was told to look up var/log/jockey.log.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: zeitgeist-core 0.8.1-1ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-5-generic i686
Architecture: i386
Date: Sat Jul 16 12:18:24 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=zh_CN:zh
LANG=zh_CN.UTF-8
PythonArgs: ['/usr/
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with LookupError in remove_
UpgradeStatus: Upgraded to oneiric on 2011-07-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Grubstreet (gogoltpr) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
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.