Using logging output for debugging purposes
Bug #660440 reported by
Markus Korn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Framework |
Fix Released
|
Low
|
Mohamed Amine Ilidrissi |
Bug Description
Right now, whenever we get a bugreport from a user who is zeitgeist `indirectly` (via unity, gnome-activity-
This is not optimal, as we a requesting some extra work from our users (who maybe don't care about zeitgeist, they just want there clients to work) and it might also take a long time to get the debugging output, we are depending on our users here.
It would be much easier if zeitgeist would also log to a file (or even better to a rotating set of files). On ubuntu we can then make apport to add such files to a bugreport.
Related branches
lp:~ilidrissi.amine/zeitgeist/zeitgeist-logging
- Siegfried Gevatter: Approve
- Seif Lotfy: Needs Resubmitting
- Markus Korn: Needs Fixing
-
Diff: 66 lines (+27/-1)2 files modified_zeitgeist/engine/__init__.py (+1/-0)
zeitgeist-daemon.py (+26/-1)
Changed in zeitgeist: | |
assignee: | nobody → Mohamed Amine IL Idrissi (ilidrissi.amine) |
Changed in zeitgeist: | |
status: | Confirmed → In Progress |
Changed in zeitgeist: | |
milestone: | 0.6 → 0.7 |
Changed in zeitgeist: | |
status: | In Progress → Fix Committed |
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I would suggest that we create a new log on every startup. in the format yyyymmddtimesta mp.log 890.log
something like 201010191234567