zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!

Bug #1463332 reported by dino99
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
zeitgeist (Ubuntu)
Confirmed
High
Unassigned

Bug Description

get that error logged into journalctl:

org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING **: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: zeitgeist-datahub 0.9.14-2.2ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.17.3-0ubuntu4
Architecture: i386
CurrentDesktop: GNOME
Date: Tue Jun 9 11:32:35 2015
SourcePackage: zeitgeist
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Changed in zeitgeist (Ubuntu):
status: New → Confirmed
Changed in zeitgeist (Ubuntu):
importance: Undecided → High
Revision history for this message
Samuel Suther (s-suther) wrote :

Same here for Kubuntu (KDE-Desktop)

Revision history for this message
dino99 (9d9) wrote :

Digging around that error, i've found http://askubuntu.com/questions/48994/unity-files-folders-lens-cant-find-anything

and did:

sudo zeitgeist-daemon --quit
[sudo] password for oem:
[09:26 - 0]
[u32 4] ~ > sudo rm -rvf ~/.local/share/zeitgeist/fts.index/
removed ‘/home/oem/.local/share/zeitgeist/fts.index/postlist.baseB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/flintlock’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/iamchert’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/position.DB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/record.baseA’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/termlist.DB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/termlist.baseB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/termlist.baseA’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/record.DB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/position.baseB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/postlist.baseA’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/postlist.DB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/record.baseB’
removed ‘/home/oem/.local/share/zeitgeist/fts.index/position.baseA’
removed directory: ‘/home/oem/.local/share/zeitgeist/fts.index/
[09:26 - 0]
[u32 5] ~ > sudo zeitgeist-daemon --replace
 extension-collection.vala:123: Skipping SearchEngine (disabled)

The latest message "Skipping SearchEngine (disabled)" is quite a surprise, and wonder what it really means.

Revision history for this message
dino99 (9d9) wrote :

Feedback since the #4 commands:

after a cold reboot, the fts.index have been rebuilt, and journalctl no more show the reported bug error.

That's it

Revision history for this message
Superman ha Muerto (superman-ha-muerto) wrote :

I think I got this error because I've restored a full backup from an older system (Ubuntu 14). I think that this fts.index was restored from a previous version of Ubuntu and therefore the problem started because of this.

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

I tried deleting the directory ~/.local/share/zeitgeist/fts.index/ and the error still shows up on 16.04.2

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.