** Changed in: zeitgeist
Status: New => Confirmed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/691690
Title:
DataSourceRegistry should have GetDataSourceForId metho
** Changed in: zeitgeist
Status: In Progress => Fix Committed
** Changed in: zeitgeist
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bu
** Changed in: zeitgeist
Status: In Progress => Fix Committed
** Changed in: zeitgeist
Importance: Undecided => High
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/6
Ah, I see, yeah I agree with the analysis above. I suggest solution c
at this point.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/691690
Title:
DataSourceRegistry should
OK, so as I see it there are various ways to fix this:
a) Not a bug - If they care about data-sources they should keep track of
them (GetDataSources at start and DataSourceRegistered after that).
However, what should be fixed is the DataSourceDisconnected signal, it
is currently sending the whole
Ok, hope I did everything!
Now:
jo...@joshg:~/zeitgeist$ ~/zeitgeist/zeitgeist/zeitgeist-daemon.py &
[1] 10001
jo...@joshg:~/zeitgeist$ [2010-12-28 19:58:20,818] - DEBUG - root - Checking
for another running instance...
[2010-12-28 19:58:20,856] - DEBUG - root - No running instances found.
[201
*** This bug is a duplicate of bug 598666 ***
https://bugs.launchpad.net/bugs/598666
In the previous benchmark, /tmp/zeitgeist-trunk is trunk and ../ is the
modified branch.
I'm also attaching a comparison of running GNOME Activity Journal, but
the data here is too random to get anything out
*** This bug is a duplicate of bug 598666 ***
https://bugs.launchpad.net/bugs/598666
I think I have a clue on what's going on, but before we fix this, I
guess I'd be good to have some documentation on why we even have the
cache. For this purpose, I've tried removing it from the engine (code at
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
Title:
Invalid cache access (was: Error when trying to fetch item
** Summary changed:
- Error when trying to fetch items
+ Invalid cache access (was: Error when trying to fetch items)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
Ti
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif) => Siegfried Gevatter (rainct)
** Changed in: zeitgeist
Importance: Low => High
** Changed in: zeitgeist
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Zeitgeist
Framework Team,
*** This bug is a duplicate of bug 598666 ***
https://bugs.launchpad.net/bugs/598666
** This bug has been marked a duplicate of bug 598666
Error when trying to fetch items
* You can subscribe to bug 598666 by following this link:
https://bugs.launchpad.net/zeitgeist/+bug/598666/+subscribe
Public bug reported:
ala...@alagos-desktop:~$ gnome-activity-journal
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
/usr/share/gnome-activity-journal/src/common.py:747: DeprecationWarning:
object.__new__() takes no parameters
GIO_FILES[subj] = object.__new__(classtype, *args,
Hello Zeitgeist Framework Team,
joshg (joshg) has been added as a member of Friends of GNOME Zeitgeist
(gnome-zeitgeist-users) by joshg (joshg). Follow the link below for more
details.
https://launchpad.net/~gnome-zeitgeist-users/+member/joshg
--
You received this email because you are an a
What's the difference between this bug and bug #692645?
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/691167
Title:
The payload is sometimes mentioned as string and sometim
before doing what i've just said try this: sudo apt-get install appmenu-
gtk
--
You received this bug notification because you are a member of GNOME
Zeitgeist Team, which is the registrant for GNOME Activity Journal.
https://bugs.launchpad.net/bugs/694849
Title:
Gnome Activity Journal doesn't
It seems to work properly...Other try: download and try the trunk version from
here:https://launchpad.net/gnome-activity-journal
Follow the instructions and tell me if it works.
Meanwhile i'll think to what is causing this bug...:)
--
You received this bug notification because you are a member o
+1 for me. I've suggested the same thing in a previous bug.
If nobody else has a better idea i could assign this bug to me.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Data-Sources.
https://bugs.launchpad.net/bugs/69
this is "zeitgeist-daemon" without the --replace, after killing it:
DEBUG:root:Checking for another running instance...
DEBUG:root:No running instances found.
INFO:zeitgeist.sql:Using database:
/home/joshg/.local/share/zeitgeist/activity.sqlite
DEBUG:zeitgeist.sql:Core schema is good. DB loaded i
Thi is "zeitgeist-daemon --replace" (I also opened an image while it was
running):
DEBUG:root:Checking for another running instance...
DEBUG:root:Replacing currently running process.
INFO:zeitgeist.sql:Using database:
/home/joshg/.local/share/zeitgeist/activity.sqlite
DEBUG:zeitgeist.sql:Core sch
IMO subject of a bzr event is the branch, and a branch is identified by
the uri, exact revision is just metadata of the event, not really a
subject property. Perhaps gaj should take a look also on the text and
not cluster events with different subject text?
--
You received this bug notification b
** Summary changed:
- Bzr data-source doens't use different uri for different events on same branch
+ Bzr datasource doesn't use different uri for different events on the same
branch
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed
Public bug reported:
Step to reproduce:
-commit or pull in a bzr branch >the event show up in GAJ
-commit or pull another time---> the event doens't show up because GAJ
discard it (these two events have the same uri: the branch's path one)
RainCT opinion: IMHO the Bazaar plugin should
I'm closing this bug since it has been fixed both in Zeitgeist (by
always committing removals) and in GNOME Activity Journal (by removing
all events in the same day part).
Stefano, please open a new bug about your issue, against Zeitgeist Data-
sources. IMHO the Bazaar plugin should be fixed to gi
Is this still a problem or have all instances been fixed by now?
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/632363
Title:
Slow queries: SQL indexes not used
Status in Z
** Changed in: zeitgeist
Status: Confirmed => In Progress
** Changed in: zeitgeist
Assignee: (unassigned) => Siegfried Gevatter (rainct)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bug
26 matches
Mail list logo
