system-tools-backends abuses the timers in a big way

Bug #61186 reported by Allison Karlitskaya
2
Affects Status Importance Assigned to Milestone
GST
Fix Released
High
system-tools-backends (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: system-tools-backends

20 wakeups per second from the system-tools-backends perl script.

caused by this line in /usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl

Net::DBus::Reactor->main->add_timeout (50, Net::DBus::Callback->new(method => \&Utils::Monitor::do_monitor_files));

every 50 milliseconds. crikey!

since ubuntu doesn't even have Sys::Gamin, this results in a call to a handler that returns immediately (so it's entirely useless).

a fix for this problem is to comment that line out.

see upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=356649

Changed in system-tools-backends:
status: Unconfirmed → Confirmed
Changed in system-tools-backends:
assignee: nobody → desktop-bugs
importance: Untriaged → Low
Changed in gst:
status: Unknown → Unconfirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload fixes the issue:

" system-tools-backends (1.9.6-0ubuntu1) edgy; urgency=low
 .
   * New upstream version:
     - Do not repeat multiple SMB share entries when the name has a $ symbol
       (Ubuntu: #6142)
     - Avoid timeouts during file monitoring (Ubuntu: #61186)
     - Code improvements to BSD, RCng and SuSE services init code
     - Add an UID/GID independent ID number in UsersConfig and GroupsConfig
       to avoid confusions when adding/deleting groups (Ubuntu: #18632)
     - DBus struct improvements in ServicesConfig
     - Avoid "use lib" warning during s-t-b initialization
     - Fix a possible bug when saving modem interfaces configuration
     - Code cleanups"

Changed in system-tools-backends:
status: Confirmed → Fix Released
Changed in gst:
status: Unconfirmed → Fix Released
Changed in gst:
importance: Unknown → High
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.