lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Light Display Manager |
Fix Released
|
Low
|
Unassigned | ||
1.10 |
Won't Fix
|
Low
|
Unassigned | ||
1.12 |
Fix Released
|
Low
|
Unassigned | ||
lightdm (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
I was trying to figure out where excessive file system writes were
coming from on the ubuntu phone (to try to reduce flash writes and hence reduce power
consumption) and I spotted that /var/log/
tail -f /var/log/
[+5109.66s] DEBUG: User /org/freedeskto
[+5409.67s] DEBUG: User /org/freedeskto
[+5709.66s] DEBUG: User /org/freedeskto
[+6009.66s] DEBUG: User /org/freedeskto
[+6309.64s] DEBUG: User /org/freedeskto
[+6609.65s] DEBUG: User /org/freedeskto
[+6909.67s] DEBUG: User /org/freedeskto
[+7209.66s] DEBUG: User /org/freedeskto
[+7509.66s] DEBUG: User /org/freedeskto
[+7809.57s] DEBUG: User /org/freedeskto
[+8109.65s] DEBUG: User /org/freedeskto
while this isn't much of a message, it still is causing file system writes every 5 minutes for the same debug message. Is this necessary? The fact that it is the same message about the same account and that it occurs every 300 seconds make me wonder if we can cull this particular piece of repeated logging.
Changed in lightdm: | |
importance: | Undecided → Medium |
status: | New → Triaged |
importance: | Medium → Low |
Changed in lightdm (Ubuntu): | |
importance: | Medium → Low |
status: | Incomplete → Triaged |
Changed in lightdm: | |
status: | Triaged → Fix Committed |
milestone: | none → 1.13.0 |
Changed in lightdm: | |
status: | Fix Committed → Fix Released |
I'd like to find out what is changing on this user every 300s - this doesn't occur on desktop and there's nothing that I can see that should be frequently changed for a user. The debugging is useful, but can be removed if there is a legitimate reason for a user to change this frequently.