Indeed, I reported that upstream but there is nobody really actively working on that code nowadays, https://bugs.freedesktop.org/show_bug.cgi?id=89777
** Bug watch added: freedesktop.org Bugzilla #89777 https://bugs.freedesktop.org/show_bug.cgi?id=89777 ** Also affects: mission-control-5 via https://bugs.freedesktop.org/show_bug.cgi?id=89777 Importance: Unknown Status: Unknown ** Changed in: telepathy-mission-control-5 (Ubuntu) Importance: Undecided => High ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1376322 Title: telepathy-mission-control is spamming dbus.log with error messages Status in Telepathy Mission Control 5: Unknown Status in telepathy-mission-control-5 package in Ubuntu: Triaged Bug description: I was trying to figure out where excessive file system writes were coming from (to try to reduce flash writes and hence reduce power consumption) and I spotted that the dbus log on my phone is being hit by messages from process 2046: root@ubuntu-phablet:~# ps -ef | grep 2046 phablet 2046 1741 0 14:43 ? 00:00:00 /usr/lib/telepathy/mission-control-5 root@ubuntu-phablet:~# tail -f /home/phablet/.cache/upstart/dbus.log (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' ..at a rate of ~15K an hour or so. This is causing unnecessary writes to the log, filling up file system space and these kind of writes to a flash file system do cost a small amount of power. Seems that there is an error somewhere, else dbus would not be logging it. To manage notifications about this bug go to: https://bugs.launchpad.net/mission-control-5/+bug/1376322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
