Liferea , the free news aggregator on your Linux desktop.

Liferea 1.10 FAQ

Q: Why doesn't Liferea start (anymore)?
A: This often is reported for users of the GNOME shell or Ubuntu Unity desktops which got rid of the tray icon. Previously Liferea started minimized to the tray icon and you clicked on the tray icon to raise the application Liferea window (More Details).

Workaround: Start once with
liferea -w shown
Q: Why doesn't Flash work (anymore)?
A: Easy flash support broke when Liferea 1.10 which uses GTK3 is used with WebkitGTK3 versions before 2.0 (More Details).

There are the following known workarounds:

  1. Upgrade WebkitGTK3 to 2.0 or later
  2. Install nspluginwrapper and the 32bit flash plugin (instructions)
Q: Why doesn't Liferea have feature X?
A: Please do NOT request new features! The project goal is to implement a simple feed reader. And you can be sure that the developer(s) will implement their own favourite features as soon as they have time to do so. If you really miss a feature please take the time to write a patch or even join the active development.
Q: What does "Liferea" stand for and how do I pronounce it?
A: "Liferea" is the abbreviation for Linux Feed Reader. It doesn't really matter how you pronounce it. I sounds pretty strange when trying to pronounce it like an English word so I'd suggest to pronounce it like a Latin word.
Q: How to use DBUS to automatically add subscriptions?
A: Check out the "liferea-add-feed" script that comes with the sources. Usage:
liferea-add-feed "http://feed.url.example.com/"
With Firefox you can use this script to configure Firefox to add new feed subscriptions directly to Liferea.
Q: How to backup/copy all files?
A: As Liferea follows the XDG directory standard it is just copying the relevant XDG directories to the other computer. The following bash command shows you all non-cache files locations Liferea uses on a typical setup:
find $HOME/{.config,.local/share}/liferea
If you transfer all of them to another computer it should be fine. Please ensure to copy the .local/share part (containing the DB) only when Liferea is not running.
Q: Security and Liferea
A: Liferea might be quite functional but is not the best choice when you consider security to be very important. There are some points you should know:
  • When using feed or proxy authentication usernames and passwords are saved plain text in ~/.liferea/feedlist.opml. File Permissions: 0600. Ensure to use 1.9.4 or later with the GNOME keyring plugin enabled if you do not want this.
  • The cache directory with the contentn database is user readable only. Contents are stored as plain text in the database.
  • This list may not be complete!
Q: I want cookies!
A: Liferea supports cookies provided by a text file ~/.cache/liferea/cookies.txt which contains cookies in Netscape format. The easiest way is to copy the file from your Mozilla profile after you created the cookies with the browser.
Q: I don't like the HTML styles Liferea uses!
A: You can have your own stylesheet. Just place a liferea.css into ~/.config/liferea/. It will be loaded additionally to the default stylesheets so you can modify some or all style definitions. To learn about the styles have a look at the default stylesheet in <install root>/share/liferea/css.
Q: I want Liferea to use dark colors!
A:There are 3 solutions:
  1. Liferea follows the global GTK dark theme hinting and pre-defined colors from GTK. So if you configure a dark theme globally Liferea will use it.
  2. If you want to use a light GTK theme for your desktop and still use a dark theme for Liferea check out: http://unix.stackexchange.com/questions/14129/gtk-enable-set-dark-theme-on-a-per-application-basis
  3. Finally there is a plugin based solution by to enforce dark rendering https://github.com/mozbugbox/liferea-plugin-studio (try the shader plugin)
Q: How can I subscribe to Gmails inbox feed?
A: Google provides a Atom feed with a list of all new messages under "https://mail.google.com/mail/feed/atom". You can simply subscribe to this URL and Liferea will pop up an authentication dialog where you need to supply your Gmail login information.
Note: Without GnomeKeyring your password will be saved in plain text in ~/.config/liferea/feedlist.opml!
Q: How do I see my LiveJournal friend's friends-only entries?
A: Use the authenticated LiveJournal RSS feed. For example use http://www.livejournal.com/users/pigrew/data/rss?auth=digest. You will need to use the feed properties dialog box to set the username and password of your LiveJournal account.
Q: How do I subscribe to MySpace or Xanga feeds?
A: For MySpaces RSS feeds subscribe to

http://blog.myspace.com/blog/rss.cfm?friendID=<friendID>

and for Xanga feeds subscribe to

http://www.xanga.com/rss.aspx?user=<username>
Q: Why do feed items keep being displayed as new?
A: This is usually due to a bad feed which associated a particular ID to multiple items. If you are experienced with syndication formats please check the feed source code. If you find problems please contact the author/webmaster of the feed. If not please submit a bug report including the URL of the problem feed to the Liferea bug tracker.

Note: If you experience this problem with a planet feed the reason might be that the planet feed does not provide unique item ids for one or all off its source feeds. If this is the case Liferea has no chance to match identical items.
Q: Liferea crashes too much.
A: We hear this complaint a lot, but we rarely do get information on how it crashed. If you find a way to make Liferea crash, we would love to know about it. Please send us a copy of the output of running Liferea with the --debug-all flag, plus a backtrace if possible.

To create a backtrace, open up a terminal and type
ulimit -c unlimited
and then start Liferea. This causes Liferea to create a core dump when it crashes. Then, run
gdb liferea-bin core
and type bt at the gdb prompt. This will display the backtrace of the crash, which should be sent along with the bug report.
Q: What does "There were errors while parsing this feed!" mean and how can I fix it?
A: The feed parser of Liferea expects valid XML. So, this error happens when a feed contains invalid XML. You can check the validity of a feed with http://feedvalidator.org/ and http://validator.w3.org/feed/.

To fix this problem, you can try to sanitize the XML with xmllint. For this, open the subscription properties of the affected feed and add xmllint as a conversion filter in the source tab like this: xmllint --recover -

Note: On Debian-based distribution xmllint is part of the libxml2-utils package.