Fixed.
The code is using os.makedirs now, instead of os.mkdir.
** Changed in: zeitgeist
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
2010/12/7 Markus Korn thek...@gmx.de:
Ohh? Is KDE (or the distro you are using) not using xdg, or why is
~/.cache not there?
«KDE supports the base directory specification and the various
environment variables it prescribes in addition to the KDE filesystem
hierarchy.»
2010/12/15 Seif Lotfy 690...@bugs.launchpad.net:
abner yes, but what about my pending requests?
abner are they all gone?
seiflotfy ah you mean during an async
Zeitgeist only handles one request at a time, so the Quit will be
alone. The next (queued or not) request should wake it up again.
--
+1 from me.
--
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/691660
Title:
Allow Extensions without PUBLIC_METHODS
Status in Zeitgeist Framework:
New
Bug description:
** Changed in: zeitgeist
Assignee: Markus Korn (thekorn) = Siegfried Gevatter (rainct)
--
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/680360
Title:
Zeitgeist builds
Yup. Or rename the message so it's clear the the query was inserting X
events but not all of them may have been successful (eg Requested
insertion of X events or Processed X events).
This message is just there for the timing information and users aren't
supposed to care about it.
--
You
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
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
._inv_dict[id]
KeyError: 1
** Affects: zeitgeist
Importance: High
Assignee: Siegfried Gevatter (rainct)
Status: Triaged
** Changed in: zeitgeist
Importance: Undecided = High
** Changed in: zeitgeist
Status: New = Triaged
** Changed in: zeitgeist
Assignee
** 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
*** 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
*** 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
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
Yeah, removed that. Thanks for spotting.
** Changed in: zeitgeist
Importance: Undecided = Low
** Changed in: zeitgeist
Status: New = Fix Released
** Changed in: zeitgeist
Milestone: None = 0.7.0
** Changed in: zeitgeist
Assignee: (unassigned) = Siegfried Gevatter (rainct
Public bug reported:
def set_data_source_enabled_callback(self, enabled_callback):
[...]
# TODO: Make it possible to access the return value!
** Affects: zeitgeist
Importance: Low
Status: New
** Changed in: zeitgeist
Importance: Undecided = Low
** Changed in:
** Changed in: zeitgeist
Importance: Undecided = Medium
** Changed in: zeitgeist
Status: New = In Progress
** Changed in: zeitgeist
Milestone: None = 0.7.0
** Changed in: zeitgeist
Assignee: (unassigned) = Siegfried Gevatter (rainct)
--
You received this bug notification
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/bug695311 into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#695311 DataSourceRegistry is a huge performance bottleneck
https://bugs.launchpad.net/bugs/695311
For more details, see
(Uhm, I had send out an e-mail about this earlier but it looks like
Launchpad lost it:)
There's a typo in my first comment, what I meant is b) or c), not a)
or b). That is, the solution I'd prefer is a). After that I'd choose
b), since a GetDataSourceForId method by itself (without the signals)
Mikkel: I agree 100% on this :).
--
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/695003
Title:
Bzr datasource doesn't use different uri for different events on the same
Question #143318 on Zeitgeist Framework changed:
https://answers.launchpad.net/zeitgeist/+question/143318
Siegfried Gevatter posted a new comment:
https://launchpad.net/zeitgeist-fts
--
You received this question notification because you are a member of
Zeitgeist Framework Team, which
Question #143318 on Zeitgeist Framework changed:
https://answers.launchpad.net/zeitgeist/+question/143318
Siegfried Gevatter posted a new comment:
Erm, sorry.
You can find the Zeitgeist FTS (full text search) extension, which is
powered by Xapian, at https://launchpad.net/zeitgeist-extensions
The proposal to merge lp:~zeitgeist/zeitgeist/bug673008 into lp:zeitgeist has
been updated.
Commit Message changed to:
ZeitgeistClient: reinstall monitors upon reconnection (LP: #673008)
For more details, see:
https://code.launchpad.net/~zeitgeist/zeitgeist/bug673008/+merge/48914
--
If you read DenyEvent's description your head explodes.
--
https://code.launchpad.net/~kamstrup/zeitgeist/new-event-interpretations/+merge/49039
Your team Zeitgeist Framework Team is requested to review the proposed merge of
lp:~kamstrup/zeitgeist/new-event-interpretations into lp:zeitgeist.
in: zeitgeist
Assignee: Siegfried Gevatter (rainct) = (unassigned)
--
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
I'm closing this bug since it isn't really being useful anymore. The
current status is that only the --help output is translated, and
translations done on Launchpad (for the three help strings) are
automatically pushed to a separate branch from where we can incorporate
them.
I think it'd make
** Changed in: zeitgeist
Milestone: 0.8.0 = None
--
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/660307
Title:
zeitgeist fails to run if its database structure is not
I think we can bump the Python dependency to Python 2.6 by now, and fix
this the right way.
--
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
So I think we decided to add origin to events in addition to what is
there 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/425258
Title:
origin should be a property of
Review: Needs Fixing
+logging.basicConfig(level=logging.DEBUG)
WHY?
And why is this and the imports there twice (before and after the big comments)?
+# storgaemonitor extension. This is actually backwards compatible.
Storgae? Is that like 'deine mudda' in Danish?
--
Public bug reported:
The FTS extension uses SQLite's argument parsing, which limits the
results to 132 distinct URIs. FTS should workaround this restriction
like Zeitgeist itself already does.
** Affects: zeitgeist-extensions
Importance: Undecided
Status: New
--
You received this
Review: Needs Fixing
lambda :
The space before the colons looks ugly :P.
except:
Please make this except sqlite3.foobar (or, worst-case, except Exception).
Also, why do you need the rollback there?
A storage medium is indetified by a key
How can I indetify you? :)
You could move most the
Haven't tried it yet, but the code looks good to me (although I still think a
baseclass would be neat :P).
--
https://code.launchpad.net/~zeitgeist/zeitgeist/storagemonitor2/+merge/49212
Your team Zeitgeist Framework Team is subscribed to branch
lp:~zeitgeist/zeitgeist/storagemonitor2.
Hi Richard,
Thank you for using Zeitgeist and taking the time to report this
problem.
However, this is not a problem in the Zeitgeist engine, but simply the
blacklist pattern isn't in the correct format. It should be:
file:///home/ric/.h/*.
In any case, I appreciate that the current blacklist
** Changed in: zeitgeist
Status: In Progress = Fix Committed
--
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/704931
Title:
Publish property names, accesslevel and
** Summary changed:
- origin should be a property of events, not items
+ Add origin as a property of events
--
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/425258
Title:
Public bug reported:
Bug #673008 fixed the Python API not reconnecting all signals when it
starts the Zeitgeist daemon again after loosing the connection with it.
Now what's missing is doing the same when someone else is restarting
Zeitgeist (ie. by listening to D-Bus's join/leave notifications).
I'm re-opening this since I've finally found the cause of this problem!
When events are deleted, interpretations/manifestations/mimetypes/etc.
which are no longer used are automatically removed from the database.
However, the cache isn't informed about this and until Zeitgeist is
restarted it'll
Review: Needs Fixing
[2011-03-04 22:48:11,119] - ERROR - zeitgeist.extension - Failed loading the
'StorageMonitor' extension
Traceback (most recent call last):
File
/home/rainct/Desenvolupament/Python/zeitgeist-project/storagemonitor2/zeitgeist/../_zeitgeist/engine/extension.py,
line 265, in
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/dbschema4 into
lp:zeitgeist with lp:~zeitgeist/zeitgeist/storagemonitor2 as a prerequisite.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
For more details, see:
https://code.launchpad.net/~zeitgeist/zeitgeist/dbschema4
Hi Owais,
Thank you for your report. This is a problem with Zeitgeist versions
older than 0.6. You can get the latest Zeitgeist version for Maverick by
installing it from our PPA.
** Changed in: zeitgeist
Status: New = Invalid
--
You received this bug notification because you are a
Indeed, thanks for catching that.
There's one additional issue, as discussed on IRC:
19:07 RainCT seiflotfy: should ZG 0.7 and 0.8 be compatible?
19:08 seiflotfy RainCT, how so ur asing
19:09 RainCT ZG isn't specifying the column names when it creates an event
19:09 RainCT so if you update to 0.8
** Branch linked: lp:~zeitgeist/zeitgeist/dbschema4
--
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/425258
Title:
Add origin as a property of events
Status in Zeitgeist
Hey Markus,
Nice to hear from you again.
What you're proposing sounds better than adding a C binding file for
update_hook (unless we decide we want to start adding more C stuff, but
I can't think of what that'd be right now). I guess it's the best we can
do.
If we're going to do this it should
*** This bug is a duplicate of bug 598666 ***
https://bugs.launchpad.net/bugs/598666
I've just added a new benchmark test to lp:~zeitgeist/zeitgeist/no-
table-cache, test/cache-test.py, which inserts 1000 events with a
different interpretation each (could as well -and more likely in the
real
OK, so I've moved the new columns to the end of the table and now Zeitgeist 0.7
is at least able to read an upgraded database. Unfortunately it looks like we
won't get around breaking compatibility for inserts, since:
OperationalError: table event has 15 columns but 13 values were supplied
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/move-event into
lp:zeitgeist with lp:~zeitgeist/zeitgeist/dbschema4 as a prerequisite.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
For more details, see:
https://code.launchpad.net/~zeitgeist/zeitgeist/move-event
Review: Needs Fixing
- Why is it possible to modify uri_current (and such modifications are
respected when inserting the event) if URIs are only supposed to change when
there is a MOVE_EVENT? This allows for inconsistencies.
- Consider renaming uri_current to current_uri.
--
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/dbus-paranoia
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
Bug #732015 in zeitgeist (Ubuntu): zeitgeist-daemon crashed with
NameExistsException in __new__(): Bus name already exists
Review: Approve
Alright, I've tested it with Network Manager and it seems to work fine. Awesome
work!
Since I love nitpicking so much, self._up () could be changed to self._up()
:P. But anyway, I think this is ready to merge as soon as dbschema4 goes in
(outstanding issues for that are
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/bug727226 into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
Bug #727226 in Zeitgeist Framework: Python API: Reconnect signals on
Zeitgeist restart notification
https://bugs.launchpad.net
** Changed in: zeitgeist (Ubuntu)
Status: New = Triaged
--
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/732015
Title:
zeitgeist-daemon crashed with
** Changed in: zeitgeist
Milestone: 0.8.0 = 0.7.1
--
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/732015
Title:
zeitgeist-daemon crashed with NameExistsException in
** Changed in: zeitgeist
Status: Triaged = Fix Committed
** Changed in: zeitgeist
Milestone: 0.8.0 = 0.7.1
** Changed in: zeitgeist
Assignee: (unassigned) = Siegfried Gevatter (rainct)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team
** Changed in: zeitgeist
Milestone: None = 0.7.1
--
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/714636
Title:
Zeitgeist needs AcceptEvent, DenyEvent and ExpireEvent
** Changed in: zeitgeist
Milestone: 0.8.0 = 0.7.1
--
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/704931
Title:
Publish property names, accesslevel and type in
** Changed in: zeitgeist
Milestone: 0.8.0 = 0.7.1
--
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/695363
Title:
Python API doesn't expose DataSourceRegistry's enabled
** Changed in: zeitgeist
Milestone: 0.8.0 = 0.7.1
--
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/673008
Title:
Reinstall monitors upon startup
Status in Zeitgeist
Public bug reported:
From bug #727226: «Another outstanding problem is that, when a method
fails and triggers the reconnect, it is run again straight away but it
ends up failing another time. »
** Affects: zeitgeist
Importance: Low
Status: New
** Changed in: zeitgeist
Hi Vadim,
Thank you for taking the time to report this bug and helping improve
Zeitgeist.
I'm closing this report, though, because the Python zeitgeist-datahub
has been discontinued (it wasn't included in the last Zeitgeist release
anymore and has been replaced with an alternative implementation
** Changed in: zeitgeist
Milestone: None = 0.8.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/736176
Title:
Python API: Methods which discover that the connection was
Since Mikkel hasn't commented yet, let's leave this for 0.8.
** Changed in: zeitgeist
Milestone: 0.7.1 = 0.8.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
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
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/732015
Title:
zeitgeist-daemon crashed with
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
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/704931
Title:
Publish property names, accesslevel and
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
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/695363
Title:
Python API doesn't expose
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
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/673008
Title:
Reinstall monitors upon startup
Status in
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/querybystorage
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
For more details, see:
https://code.launchpad.net/~zeitgeist/zeitgeist/querybystorage/+merge/57911
--
https://code.launchpad.net
Note that this is already implemented in GNOME Activity Journal under
the name incognito mode (it's available in the tray icon).
--
You received this bug notification because you are a member of History
Manager, which is the registrant for History Manager.
https://bugs.launchpad.net/bugs/762138
Add a try except block in the _write_to_disk method
Fixed some indents
Looks good. Feel free to commit this part already.
Add a counter to write to disk upon every 20 events
Why every 20 events? I don't like this, too arbitrary (and it ends writing to
disk a lot again).
Also, shouldn't
Committed. Thanks for the patch, Martin!
** Changed in: zeitgeist-dataproviders
Status: New = Fix Released
--
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/704934
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/db4fixes into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
For more details, see:
https://code.launchpad.net/~zeitgeist/zeitgeist/db4fixes/+merge/59115
--
https://code.launchpad.net/~zeitgeist/zeitgeist
See https://bugs.launchpad.net/zeitgeist/+bug/771491 for the failing test case,
please ignore it for the purpose of this merge request.
--
https://code.launchpad.net/~zeitgeist/zeitgeist/db4fixes/+merge/59115
Your team Zeitgeist Framework Team is subscribed to branch
I propose the following solution for this problem.
** Patch added: Proposed patch
https://bugs.launchpad.net/zeitgeist/+bug/771491/+attachment/2090664/+files/bug771491.diff
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to
Public bug reported:
Currently the MostPopular* and LeastPopular* methods are choosing a
random (*) event from within all events matching the criteria.
Is this desired? I believe it'd make more sense to return that one with
the highest timestamp for MostPopular* and the one with the oldest
Apparently cb_timeout() is running in it's own world. Even if I create a
class variable, and change it inside cb_timeout, when I check it outside
the timeout afterwards it hasn't changed. Really weird...
--
You received this bug notification because you are a member of Zeitgeist
Framework Team,
I'm attaching an initial try at fixing this. The patch fixes all test
cases, but I still need to clean it up somehow before it can be merged.
** Patch added: initial_patch.diff
https://bugs.launchpad.net/zeitgeist/+bug/772041/+attachment/2096985/+files/initial_patch.diff
--
You received
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/fix772041 into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
Bug #772041 in Zeitgeist Framework: Timestamp isn't considered when choosing
events by popularity
https://bugs.launchpad.net
Public bug reported:
After adding origin as a new event property (bug #425258), it should
also be an option for sorting when querying events.
** Affects: zeitgeist
Importance: Undecided
Status: New
** Summary changed:
- Add sorting by current URI
+ Add sorting by event origin
**
** Patch added: eventorigin.diff
https://bugs.launchpad.net/zeitgeist/+bug/777114/+attachment/2111897/+files/eventorigin.diff
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
** Changed in: zeitgeist
Status: New = Fix Committed
** 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
timestampprevious_move_event.timestamp
seiflotfy RainCT, exactly
seiflotfy i am +- 0 on that tbh
seiflotfy not sure
RainCT ok, I don't dislike finding the previous timestamp
RainCT i'll open a bug
** Affects: zeitgeist
Importance: Medium
Assignee: Siegfried Gevatter (rainct)
Status: Triaged
--
You
** Changed in: zeitgeist
Importance: High = Medium
--
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/777115
Title:
Add sorting by current_uri
Status in Zeitgeist
** Changed in: zeitgeist
Importance: Undecided = High
** Changed in: zeitgeist
Status: New = Fix Committed
** Changed in: zeitgeist
Assignee: (unassigned) = Siegfried Gevatter (rainct)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team
) = Siegfried Gevatter
(rainct)
--
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/740911
Title:
Timed-out testcases should be marked as SKIPPED, or FAILED
Status in Zeitgeist
Closing the Zeitgeist task of this since it seems to be a datahub thing.
** Changed in: zeitgeist
Status: New = Invalid
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/no-metaclasses
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
For more details, see:
https://code.launchpad.net/~zeitgeist/zeitgeist/no-metaclasses/+merge/60276
--
https://code.launchpad.net
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
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/602211
Title:
Monitoring Create/Move/Copy Files events
Thanks, I've committed your fix.
Can you please check if it's working right (since I applied the chnges by hand):
http://bazaar.launchpad.net/~zeitgeist-dataproviders/zeitgeist-dataproviders/trunk/view/head:/emacs/zeitgeist.el
** Changed in: zeitgeist-dataproviders
Status: Confirmed = Fix
2011/5/17 Manish Sinha (मनीष सिन्हा manishsi...@ubuntu.com:
I think we can get the list from dataaource registery.
One question in such case would be what to do for files logged via
datahub?
The data-source registry correlates to data-sources, but not
necessarily to applications. The way to
thekorn I know we had a good reason to do it this way, but I cannot remember
which, let me think about it a bit
We do. The upgrade scripts rely on all that being run afterwards, to re-create
the event view as well as create any new index, etc. I like it being this way
since it avoids
** Changed in: history-manager
Importance: Undecided = Wishlist
** Changed in: history-manager
Status: New = Confirmed
** Changed in: history-manager
Milestone: None = 0.8.1
--
You received this bug notification because you are a member of History
Manager, which is the registrant
** Changed in: history-manager
Status: New = Incomplete
--
You received this bug notification because you are a member of History
Manager, which is the registrant for Activity Log Manager.
https://bugs.launchpad.net/bugs/783979
Title:
Latest version available in the Zeitgest PPA (br
** Changed in: history-manager
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of History
Manager, which is the registrant for Activity Log Manager.
https://bugs.launchpad.net/bugs/783566
Title:
Logging Active confusingly looks like Apply
** Changed in: history-manager
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of History
Manager, which is the registrant for Activity Log Manager.
https://bugs.launchpad.net/bugs/762138
Title:
Please add a button Stop all logging
Hi,
Do you have Zeitgeist 0.8.0 installed system-wide? If not, you need to
start it manually before you run Activity Log Manager.
** Changed in: history-manager
Status: New = Incomplete
--
You received this bug notification because you are a member of Activity
Log Manager, which is the
Thanks for getting back to us so fast.
Can you please try running activity-log-manager from the terminal and
seeing whether it shows any debug message when you try to delete recent
entries?
Also, does the blacklist part work? (Ie., is deleting the only problem
or isn't it working at all for
Cool, thanks!
** Changed in: history-manager
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Activity
Log Manager, which is the registrant for Activity Log Manager.
https://bugs.launchpad.net/bugs/784067
Title:
Fixed in revision 41.
Thanks!
** Changed in: history-manager
Status: Confirmed = Fix Committed
** Changed in: history-manager
Assignee: (unassigned) = Siegfried Gevatter (rainct)
--
You received this bug notification because you are a member of Activity
Log Manager, which
** Changed in: zeitgeist
Status: Triaged = Fix Committed
** Changed in: zeitgeist (Ubuntu)
Importance: Undecided = Low
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif) = J.P. Lacerda (jplacerda)
--
You received this bug notification because you are a member of Zeitgeist
** Changed in: zeitgeist
Milestone: None = 0.8.1
--
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/660307
Title:
zeitgeist fails to run if its database structure is not
** Changed in: zeitgeist
Importance: Undecided = Medium
** Changed in: zeitgeist
Status: New = Confirmed
** Changed in: zeitgeist
Milestone: None = 0.8.1
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
201 - 300 of 595 matches
Mail list logo
