fills $HOME/.cache/gdm/session.log

[Mike Greenly]

Rhythmbox fills $HOME/.cache/gdm/session.log with a constant error stream resulting in gigabytes per minute of the exact same error no matter if it's playing content or sitting idle (sample below).

(rhythmbox-metadata:27790): GStreamer-CRITICAL **: gst_bus_timed_pop_filtered: assertion `timeout == 0 || bus->priv->poll != NULL' failed

If this is truley a critical error it should crash or at least quit trying to do what ever it's doing. If not it should log the error and be on it's happy way. It certainly shouldn't fill up my hard drive every couple of days.

lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04

apt-cache policy rhythmbox
rhythmbox:
  Installed: 2.98-0ubuntu5
  Candidate: 2.98-0ubuntu5
  Version table:
 *** 2.98-0ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

I'm more than happy to provide additional information if needed.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Yogu (yogu)]

I've got the same error, but with a different file number:

(rhythmbox-metadata:8136): GStreamer-CRITICAL **: gst_bus_timed_pop_filtered: assertion `timeout == 0 || bus->priv->poll != NULL' failed

lsb_release and apt-cache information exactly as in description.

I don't know if this is releated, but this error occured while I tried to import my library from an NTFS drive, and that imported the whole file system instead of the folder I selected.

[Šimánek (jasonsimanek)]

I am getting the same repeating error filling up my gdm session file as Yogu.

[xouns (xxouns)]

Found the same error in ~/.xsession-errors:
(rhythmbox-metadata:(pid)): GStreamer-CRITICAL **: gst_bus_timed_pop_filtered: assertion `timeout == 0 || bus->priv->poll != NULL' failed.
32bit, 13.04

[Alexander Pánek (a-panek)]

I just found Rhythmbox filled up my complete /home partition with 8G worth of the very same error message the others pointed out.

That's not so cool. Is there an easy way to fix this until an update is available?

[Defacto Seven (be-real)]

Until it's fixed, I wrote a cron command that checks that file every 5 minutes and deletes it whenever it reaches 500Mb. That's still too large but I don't mind looking at the log to see what's happening once in a while. At leat my /home doesn't boil over.

[Ben Copeland (bcc)]

yup this just happened to me too. Would be good to get this fixed.

[Walter Garcia-Fontes (walter-garcia)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

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