zeitgeist DEBUG log messages appearing in zeitgeist log - should be disabled

Bug #906451 reported by Colin Ian King on 2011-12-19
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu Power Consumption Project
Low
Unassigned
Zeitgeist Framework
Fix Released
Low
Unassigned
zeitgeist (Ubuntu)
High
Unassigned
Precise
High
Unassigned

Bug Description

While trying to identify rogue processes that periodically write log data unnecessarily I identified that zeitgeist is appending DEBUG messages to the /home/$user/.cache/zzeitgeist/daemon.log (see attached log).

Logging messages to a debug log is useful, however on production release code I don't expect to see DEBUG messages being written to log files:

1. If they are for debugging only then they should be inhibited in production quality code.
2. Unnecessary debug messages to logs cause additional unwanted writes to the disk - when on battery power this can cause laptops to spin drives up and waste power.

Since we are trying to reduce the power consumption I am requesting that debug messages are not written to this log unless debug is explicitly turned on.

How to reproduce:

On an installed system observe the daemon.log get DEBUG messages appended to it over time. Occurs on idle and non-idle systems.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: zeitgeist 0.8.2-1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Dec 19 17:46:42 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: zeitgeist
UpgradeStatus: No upgrade log present (probably fresh install)

Colin Ian King (colin-king) wrote :
Colin Ian King (colin-king) wrote :

Attached: log

Changed in zeitgeist (Ubuntu):
milestone: none → ubuntu-12.04-beta-1
Steve Langasek (vorlon) on 2011-12-19
Changed in zeitgeist (Ubuntu):
status: New → Triaged
importance: Undecided → High
tags: added: battery-power-consumption
Changed in zeitgeist:
importance: Undecided → Low
milestone: none → 0.9.0
status: New → Triaged
Seif Lotfy (seif) on 2012-01-03
Changed in zeitgeist:
status: Triaged → Fix Committed
Martin Pitt (pitti) on 2012-01-16
Changed in ubuntu-power-consumption:
status: New → In Progress
Martin Pitt (pitti) on 2012-01-19
Changed in ubuntu-power-consumption:
importance: Undecided → Low
Seif Lotfy (seif) on 2012-01-27
Changed in zeitgeist:
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package zeitgeist - 0.8.99~alpha2-1

---------------
zeitgeist (0.8.99~alpha2-1) experimental; urgency=low

  * New upstream release. Some of the changes are:
    - Enhanced error handling, reporting and recovery (LP: #848710,
      LP: #743857).
    - The database file is now only readable by the user (LP: #910273).
    - GVFS usage in StorageMonitor has been disabled for now (LP: #905898).
    - Fixed a problem where the FTS extension could block the DB (LP: #919111).
    - Debug messages are no longer displayed by default (LP: #906451).
  * debian/rules:
    - Do not install the raw .trig files.
  * debian/zeitgeist-core.bash_completion:
    - Change source directory from extra/ to data/.

 -- Siegfried-Angel Gevatter Pujals <email address hidden> Fri, 27 Jan 2012 15:56:06 +0100

Changed in zeitgeist (Ubuntu Precise):
status: Triaged → Fix Released
Martin Pitt (pitti) on 2012-01-30
Changed in ubuntu-power-consumption:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers