Getting Involved

More information about getting involved with other GNOME apps (and many tips that apply to Rhythmbox) can be found at GettingInvolved.

Building Rhythmbox from Source

You can download the current Rhythmbox source from the GNOME git server, or release tarballs from the GNOME download site.

Before you can build Rhythmbox from a source tarball, or from source checked out from git, you'll need to make sure you have the required development libraries and headers installed. Rhythmbox requires:

  • GNOME 3.0 or newer (including GLib 2.32 and GTK+ 3.4) GStreamer 0.10.32 or newer totem-pl-parser 3.2.0 libsoup 2.34 gobject-introspection 0.10.0 json-glib libpeas 0.7.3 tdb 1.2.6

Optional packages for additional functionality:

  • GUdev 143 or newer (or hal) libgpod 0.6 or newer for iPod support libmtp 0.3 or newer for MTP device support libnotify 0.7.0 brasero for audio CD burning Python and pygobject 3.0 to enable plugins written in Python libdmapsharing 2.9.19 or newer for DAAP music sharing grilo 0.2.0 or newer


In most ways, Rhythmbox is a typical GNOME application. There is some information on debugging GTK+ applications, and instructions for providing stack traces.

Rhythmbox can provide debug output when invoked with the '-d' command line option, which enables all debug output, or the '-D <match>' option, which enables all debug output from functions and source files containing the match string. When running in a debugger with some debug output enabled, Rhythmbox will also cause the debugger to stop on any GLib warning or critical message.

For more complicated problems, it may be necessary to use the Valgrind tools. Instructions for running these on GNOME applications.


Just as many other GNOME applications, Rhythmbox is translated by the GNOME translation team. You can check the translation status here.


If you want to write documentation for Rhythmbox, you should join the GNOME Documentation team.

Apps/Rhythmbox/Contributing (last edited 2018-02-20 07:25:24 by SvitozarCherepii)