Liferea

This is a bugfix release fixing tray icon minimizing. It also adds seeking to the media player. Please upgrade.

With the switch to GTK3 all Webkit using applications like Epiphany, Liferea, devhelp, yelp and others lost Flash support. The reason is that Linux-Flash is GTK2 only! And of course there won't be new releases from Adobe ever. So we have the ... [More] following compatibility situation for Liferea Release Line Uses Flash Status 1.6 1.8 GTK2 + WebkitGTK2 any native Flash Works 1.10 GTK3 + WebkitGTK3 v1.8 32bit native Flash Broken 1.10 GTK3 + WebkitGTK3 v1.8 64bit native Flash Broken 1.10 GTK3 + WebkitGTK3 v1.8 32bit Flash + nspluginwrapper Works 1.10 GTK3 + WebkitGTK3 v2.0 any native Flash Works The WebkitGTK+ solution for the Flash problem was implemented in version 2.0 by having a second process linked against GTK2 to run browser plugins while Webkit itself is linked to GTK3. This makes Flash work again. But the currently widely distributed WebkitGTK3 v1.8 does not have this feature yet and fails to use the native flash. nspluginwrapper Workaround The only workaround is to use nspluginwrapper to run the 32bit version of Flash. This is guaranteed to work on 64bit platforms. It might not work on 32bit hardware, sometimes also because nspluginwrapper is not available there. The steps to install it are: Install nspluginwrapper. On Debian apt-get install nspluginwrapper Download 32bit Flash .tar.gz from Adobe Extract /usr files according to the Adobe instructions In the tarball directory run nspluginwrapper -i -a -v -n libflashplayer.so to install the plugin Now all WebkitGTK3 using applications should be able to run Flash. Ensure to restart them and check command line output for any plugin errors. Upgrading to WebkitGTK3 2.0 If you can try upgrading to WebkitGTK3 2.0 (e.g. Debian Experimental). [Less]

There is slow progress in the world of news aggregation services. Since the last post on possible sync implementations I was able to submit API access requests for AOL Reader and Feedly. There is a chance that the request for AOL Reader will be ... [More] successful. The unexpected thing with AOL is that they require OAuth2 authentication which Liferea does not yet support. Still it will be possible to add it. My clear favourites are still AOL and Digg. With two 3rd party hosters and one self-hosted solution (TinyTinyRSS) Liferea would provide a reasonable set of choices. Name API Status Implementation Status Google Reader Deprecated Implemented, Now Useless TinyTinyRSS Published. Implemented, Stable TheOldReader Published. Implemented, Experimental AOL Reader Published API Key Requested Digg Reader Planned 1) % NewsBlur Published Not Planned. Feedly Secret 2) API Access Requested 1) Digg has announced they will be implementing Google Reader API and hope is they open it up 2) Feedly has announced there will be a public API with v17 [Less]

This is a 1.10 bugfix release. Please upgrade! It provides fixes for proxy issues, theme color issues, GStreamer 1.0 support and some schema problems. This release introduces SOCKS proxy support through libproxy.

This is a 1.10 bugfix release. Please upgrade! It provides fixes for proxy issues, theme color issues, GStreamer 1.0 support and some schema problems. This release introduces SOCKS proxy support through libproxy.

If you are using 1.10 with the GnomeKeyring plugin, which will be automatically activated in GNOME environments, you might run into a strange bug (see SF #1099). It appears that the keyring "liferea" created by the plugin can become "stale" - it ... [More] just doesn't work anymore. At the moment I have no idea what triggers this and what is exactly the problem. If this happens Liferea cannot store passwords into the keyring anymore and you get password prompts all the time. Workaround: Delete the "liferea" keyring from GnomeKeyring using the "seahorse" keyring editor. Ensure you have installed "seahorse" and launch it from the command line seahorse and delete the keyring as shown in the screenshot: [Less]

As reported on the TheOldReader status page it is online again since July 25, 21:07 UTC.

If you are using Liferea with TheOldReader you currently see errors when synchronizing. This is caused by a storage incident with TheOldReader (see details here). There was an official mail from TheOldReader this morning informing about the downtime ... [More] of approx. 1-2 days. From the post Here comes the worst news - this will probably take a day or two. Sorry about that. The amazing information in this post is that there are now 400k TheOldReader users! So if you are affected please keep patient and give the guys credit for working so hard. After all it is a free service. [Less]

If you are using ArchLinux and clicking HTTPS links in the internal browser suddenly doesn't work anymore have a look at this bug report: https://bugs.archlinux.org/task/36212. It seems that a gnutls upgrade broke HTTPS in Webkit (which is the embedded browser in Liferea).

This is a new major release replacing the 1.8 line. This release introduces TheOldReader synchronisation support, an item history navigation, the possibility to converting external source into local subscription (e.g. to save your Google Reader ... [More] items), a music player for attachments, GNOME keyring support, the usage of XDG compliant paths, improved link handling in context menus, a default view mode preference, a full screen option, better dark theme support, improved unread counter display and many smaller improvements. Please also note that 1.10+ requires GTK+3. [Less]