Skip to content
Liferea Official Development
C Python Makefile CSS M4 XSLT Shell
Failed to load latest commit information.
css Fixes #49: incorrect path in help Sep 23, 2014
doc Fixes Github #195: Out-dated documentation on enclose download (repor… Jun 19, 2015
dtd *** empty log message *** Jan 16, 2005
glade Set license type property instead of a whole copy of the license Mar 19, 2016
man Update manpage Dec 26, 2015
opml Fixes Github #134: Broken default news feed (reported by pvdl) Jan 11, 2015
pixmaps Add symbolic icon suitable for HighContrast. Mar 7, 2015
plugins Code cleanup and readd minimize to tray on minimize Mar 30, 2016
po Merge pull request #329 from GreenLunar/patch-2 Apr 4, 2016
src Fixes Github #73: Problem with favicon updates Apr 4, 2016
xslt Remove GeoIP rendering via OSM to avoid exposing users to possible un… Mar 22, 2016
.gitignore Ignore tests binaries Jan 5, 2015
.travis.yml Fix webkit dependency for Travis Jun 2, 2014
AUTHORS Update of Swedish translation (Andreas Ronnquist) Mar 22, 2016
COPYING Fixes SF #1041: Some GPLv2 license headers were outdated (reported by… Dec 25, 2012
ChangeLog Fixes Github #73: Problem with favicon updates Apr 4, 2016
INSTALL get rid of missing, depcomp, and install-sh because they are auto-gen… Feb 28, 2006 Add missing libnotify plugin from release tarballs #39 Jul 27, 2014 Update Feb 2, 2016 Fixes #331: wrong permission of Apr 4, 2016 Pre-release version bump. Jan 30, 2016 Extend appdata to reflect 1.11 Jul 22, 2014
liferea.convert Simplied external browser handling. Now Liferea only supports the gtk… Feb 27, 2015 Fixes #283: Bad .desktop catgories definition (reported by Wuzzy2) Oct 30, 2015 Fixes #254 for 1.11+ when migrating. Apr 4, 2016

build status git master Coverity Scan Build Status


Liferea is a desktop feed reader/news aggregator that brings together all of the content from your favorite subscriptions into a simple interface that makes it easy to organize and browse feeds. Its GUI is similar to a desktop mail/newsclient, with an embedded graphical browser.


Installation from Package

We do not provide packages, but others do. Detailed instructions on how to get Liferea packages installed on the different distributions can be found at

Building Liferea Yourself

This section describes how to compile Liferea yourself. If you have any problems compiling the source file an issue at Github and we will help you asap.



gtk3 libxml2 libxslt sqlite3 libwebkit3 libjson-glib libgirepository1.0 libpeas gsettings-desktop-schemas


  • To use plugins:
    • Python >= 2
  • For the media player plugin
    • GStreamer 0.10+ library and codecs
Compiling from Tarball

Download a tarball from and extract and compile with

tar jxvf liferea-1.11.0.tar.bz2 
make install
Compiling from Git

Check out the code:

git clone

Then build it with:

make install


As the project is hosted at Github pull requests and tickets via Github are the best way to contribute to Liferea.


Before starting to translate you need a translation editor. We suggest to use poedit or gtranslator. Please edit the translation using such a translation editor and send us the resulting file. Once you have finished your work please send us the resulting file.

Please do not send translation patches. Those are a lot of work to merge and the bandwidth saving is not that huge!

New Translations

To create a new translation you must load the translation template, which you can find in the release tarball as "po/liferea.pot", into the translation editor. After editing it save it under a new name (usually your locales name with the extension ".po").

Updating Translations

When updating an existing translation please ensure to respect earlier translators work. If the latest translation is only a few months old please contact the latest translator first asking him to review your changes especially if you change already translated literals.

Localizing Feed Lists

When Liferea starts for the first time it installs a localized feed list if available. If this is not the case for your locale you might want to provide one. To check if there is one for your country have a look into the "opml" subdirectory in the latest release tarball or GIT.

If you want to provide/update a localized feed list please follow these rules:

  • Keep the English part of the default feed list
  • Only add neutral content feeds (no sex, no ideologic politics, no illegal stuff)
  • Provide good and short feed titles
  • Provide HTML URLs for each feed.

Once finished post the result OPML file in the mailing list or the SF patch tracker.

Creating Plugins

Liferea 1.10+ support GObject Introspection based plugins using libpeas. The Liferea distribution comes with a set of Python plugin e.g. the media player, GNOME keyring support, a tray icon plugin and maybe others.

Why We Use Plugins?

The idea behind plugins is to extend Liferea without changing compile time requirements. With the plugin only activating if all its bindings are available Liferea uses plugins to automatically enable features where possible.

How Plugins Interact With Liferea

You can develop plugins for your private use or contribute them upstream. In any case it makes sense to start by cloning one of the existing plugins and to think about how to hook into Liferea. There are two common ways:

  • using interfaces,
  • or by listening to events on Liferea objects,
  • or not at all by just controlling Liferea from the outside.

The media player is an example for 1.) while the tray icon is an example for 3.) If you find you need a new plugin interface (called Activatables) in the code feel free to contact us on the mailing list. In general such a tight coupling should be avoided.

About the exposed GIR API: At the moment there is no stable API. Its just some header files fed into g-ir-scanner. Despite this method names of the core functionality in Liferea has proven to be stable during release branches. And if you contribute your plugin upstream it will be updated to match renamed functionality.

Testing Plugins

To test your new plugin you can use ~/.local/share/liferea/plugins. Create the directory and put the plugin script and the .plugin file there and restart Liferea.

Watch out for initialization exceptions on the command line as they will permanently disable the plugin. Each time this happens you need to reenable the plugin from within the plugin tab in the preferences dialog!

How to Help With Testing
Bug Reports

If you want to help with testing grab the latest tarball or follow GIT master and write bug reports for any functional problem you experience. If you have time help with bug triaging the SF tracker. Check if you see any of the open bugs on your setup.

Debugging Crashes

In case of crashes create gdb backtraces and post them in the bug tracker. To create a backtrace start Liferea using "gdb liferea". At the gdb prompt type "run" to start the execution and "bt" after the crash. Send us the "bt" output!

Note: Often people confuses assertions with crashes. Assertions do halt the program because of a totally unexpected situation. Creating a backtrace in this situation will only point to the assertion line, which doesn't help much. In case of an assertion simply post a bug report with the assertion message.

Debugging Memory Leaks

If you see memory leakage please take the time to do a run

valgrind --leak-check=full liferea

to identify leaks and send in the output.

Browser Integration

Liferea allows subscribing directly from Firefox and browser with similar mechanism


If you want to subscribe from within Firefox you can configure it to add subscriptions to Liferea directly. To do so click the feed icon in the location entry. Firefox will then present a menu where you can configure a manual command instead of the Live Bookmarks to add subscriptions.

There enter


How to Get Support

When using distribution packages:

Do not post bug reports in the Liferea bug tracker, use the bug reporting system of your distribution instead. We (upstream) cannot fix distribution packages!

Before getting support for stable releases:

Install the latest stable release and check if the problem is solved already. Please do not ask for help for older releases!

At the moment there are two major support channels:

Hopefully we can help with your problem.

Something went wrong with that request. Please try again.