indicator-network-service writing debug messages about cell signal strength to /home/phablet/.cache/upstart/indicator-network.log

Bug #1228083 reported by Colin Ian King
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Network Menu
Fix Released
Medium
Ted Gould
indicator-network (Ubuntu)
Fix Released
Medium
Ted Gould

Bug Description

indicator-network-service is frequently writing copious amounts of debug messages to /home/phablet/.cache/upstart/indicator-network.log, for example:

tail -f /home/phablet/.cache/upstart/indicator-network.lo
** (process:1378): DEBUG: device-base.vala:152: Marking '/ril_0' as Disabled
** (process:1378): DEBUG: device-base.vala:152: Marking '/ril_0' as Disabled
** (process:1378): DEBUG: network-action-manager.vala:581: Active connection changed to: wlan0
** (process:1378): DEBUG: network-action-manager.vala:581: Active connection changed to: wlan0
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 22
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 25
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 29
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 25
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 22
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 25
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 22
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 19
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 16
** (process:1378): DEBUG: network-action-manager.vala:261: Cell Strength: 19

If I am moving around then the signal strength is frequently changing and this log is being appended to every second or so. This is wasteful on flash and also wastes power just for debug messages.

Related branches

Ted Gould (ted)
Changed in indicator-network:
status: New → In Progress
Changed in indicator-network (Ubuntu):
status: New → In Progress
Changed in indicator-network:
importance: Undecided → Medium
Changed in indicator-network (Ubuntu):
importance: Undecided → Medium
Changed in indicator-network:
assignee: nobody → Ted Gould (ted)
Changed in indicator-network (Ubuntu):
assignee: nobody → Ted Gould (ted)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:indicator-network at revision 300, scheduled for release in indicator-network, milestone Unknown

Changed in indicator-network:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-network - 0.5.1+13.10.20131011-0ubuntu1

---------------
indicator-network (0.5.1+13.10.20131011-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Ensure APs with SSIDs we don't want to show aren't shown. (LP:
    #1231532, #1088956)
  * Check to make sure we don't get zero interfaces back. (LP: #1232651)
  * Force the UI of other APs to be disabled when starting a new
    connection. (LP: #1233194)
  * Only select active connection once it has a device.
  * Stop AP actions from being removed by the menu object.
  * Don't output cell strength to log files. (LP: #1228083)
  * Removing settings items for network prompting.
  * Listen to auto-reconnect setting. (LP: #1236747)

  [ Nick Dedekind ]
  * SIM pin/puk unload menu & dialog notification.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 302
 -- Ubuntu daily release <email address hidden> Fri, 11 Oct 2013 04:28:09 +0000

Changed in indicator-network (Ubuntu):
status: In Progress → Fix Released
Ted Gould (ted)
Changed in indicator-network:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.