unity8.log spammed: Failed to get current playback position: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

Bug #1613056 reported by Vincas Dargis
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
media-hub (Ubuntu)
Expired
Undecided
Unassigned
qtubuntu-media (Ubuntu)
Invalid
Undecided
Unassigned
unity8 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

BQ E5, OTA-12.

I've noticed that my ~/.cache/upstart/unity8.log contains lot's of these messages, filled every second (file is around 6 Megs at time of writing):

[2016-35-10:11:35:07.388] Failed to get current playback position: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

[2016-35-10:11:35:08.388] Failed to get current playback position: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

[2016-35-10:11:35:09.388] Failed to get current playback position: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

I do not know what produces these, or since when it has started. These lines starts from beginning of log file, I cannot trace that event / app that started it.

I've just rebooted, and these messages have stopped.

There was no other app, except terminal where I was debugging, launched, no musig playing, etc.

summary: - unity8.log spammed with Failed to get current playback position messages
+ unity8.log spammed: Failed to get current playback position:
+ org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature
+ "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
Revision history for this message
Albert Astals Cid (aacid) wrote :

Jim, those seem to be coming from qtubuntu-media

Changed in unity8 (Ubuntu):
status: New → Invalid
Revision history for this message
Jim Hodapp (jhodapp) wrote :

This happens when media-hub-server has crashed or become unresponsive in some way, either because the current player session over dbus has hung or because the system load is very high for some reason. Can you clear out the crash files in /var/crash, then the next time you notice this do the following:

1. Attach the crash file(s) for media-hub here
2. Attach the media-hub log file from /home/phablet/.cache/upstart/media-hub.log
3. See if you're able to play music from music-app when you're getting these messages.

Changed in qtubuntu-media (Ubuntu):
status: New → Invalid
Changed in media-hub (Ubuntu):
status: New → Incomplete
Revision history for this message
Vincas Dargis (talkless) wrote :

Thanks for info, I'll try.

Revision history for this message
Vincas Dargis (talkless) wrote :

There is one .crash file, though log was not spammed.

Revision history for this message
Jim Hodapp (jhodapp) wrote :

You'll want to try again with OTA-13 once it's released. My hunch is that it will greatly help in reducing this issue as various system components will now be able to reconnect to media-hub-server after a crash.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for media-hub (Ubuntu) because there has been no activity for 60 days.]

Changed in media-hub (Ubuntu):
status: Incomplete → Expired
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.