Ubuntu
rhythmbox package

Window becomes unresponsive and sound stops when skipping to next track

Bug #1532544 reported by Luke picciau
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

When skipping to the next track rhythmbox will sometimes become unresponsive and rapidly send the error

(rhythmbox:4897): GStreamer-CRITICAL **: gst_poll_write_control: assertion 'set != NULL' failed

(rhythmbox:4897): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again: 11:Resource temporarily unavailable

to ~/.cache/upstart/indicator-sound.log which takes up most of the CPU and quickly fills all hard drive space.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: rhythmbox 3.2.1-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jan 10 23:04:18 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-26 (168 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to wily on 2015-10-23 (79 days ago)

Revision history for this message
Luke picciau (luke-b-picciau) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in rhythmbox (Ubuntu):
importance: Undecided → Low
Revision history for this message
Artem S. (arano) wrote :

Please raise improtance of the issue. It's not Low!

indicator-sound.log very quickly eats all free space. It also tries to do this constantly. My 13G of free space it took in less then hour.

And since it tries to write log line tens times in a second, I have got several apps that lost their settings, because when they tried to save them (overwrite files with settings) they failed to do this and wrote file with 0 size. All settings were lost.

It's huge impact.

I had to create script to protect me from this:
------------------------------
 ~ -> cat ~/.local/indicator-workaround.sh
#!/bin/bash

echo $(date) "Check for indicator-sound size"

if [ $(stat -c %s ~/.cache/upstart/indicator-sound.log) -ge 10000000 ] ; then
    echo $(date) "Killing indicator-sound!"
    rm ~/.cache/upstart/indicator-sound.log
    pkill -f indicator-sound-service
------------------------------

And add it to 'crontab -e':
-----------------------------
SHELL=/bin/bash

*/5 * * * * ~/.local/indicator-workaround.sh >>~/.cache/cron.log 2>&1
-----------------------------

Revision history for this message
Artem S. (arano) wrote :

I fogot copypaste 'fi' as last line in the script

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

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

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Luke picciau (luke-b-picciau) wrote :

I haven't had this issue in a long time. Maybe it has been fixed?

Ken Sharp (kennybobs)
Changed in rhythmbox (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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