Bug 10692

Summary:	Liferea crashing all the time
Product:	Mageia	Reporter:	Sascha Schroeder <sascha.schroeder>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	Keywords:	UPSTREAM
Version:	3
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	liferea	CVE:
Status comment:

Description Sascha Schroeder 2013-07-04 19:49:00 CEST

Description of problem:

Liferea is crashing permanently. Neither the official version from the repo, nor the Cauldron version 1.8.15 is working correctly.

It seems it has problems with Java AND Flash. Anyway, these crashes happen when you browse the feeds with one of them activated which is often pretty essential.

Here is my log from the command line:

bash$ liferea
java version "1.7.0_25"
OpenJDK Runtime Environment (mageia-2.3.10.1.mga3-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Speicherzugriffsfehler (which means "memory write error" or sth.)

Version-Release number of selected component (if applicable):
1.8.15 (and the one available through the repos)

Steps to Reproduce:
1. Install Liferea
2. in Tab "Browser" "Activate Browser Plugins"
3. browse feeds, especially some with Flash and/or Java
4. see that it crashes
5. restart, do the same to understand what I mean


Reproducible: 

Steps to Reproduce:

Sascha Schroeder 2013-07-04 19:50:04 CEST

Priority: Normal => release_blocker

Comment 1 Manuel Hiebel 2013-07-04 21:47:30 CEST

it seems strange to have flash or java in rss feed but well, can you provide an url ?

Priority: release_blocker => Normal
Source RPM: (none) => liferea

Comment 2 Sascha Schroeder 2013-07-04 22:03:21 CEST

(In reply to Manuel Hiebel from comment #1)
> it seems strange to have flash or java in rss feed but well, can you provide
> an url ?

I don't get why this should be unusual. Ever heard of gaming pages and that there are trailers as well? Or ever checked the feed of Laughing Squid when they post some Vimeo clips which don't work in Liferea either?

Anyway, here are some feeds for you to test it yourself:

http://feeds.feedburner.com/TinyCartridge
http://destructoid.com/elephant/index.phtml?mode=atom
http://www.allgamesbeta.com/feeds/posts/default?alt=rss
http://feeds.feedburner.com/laughingsquid

Regards

Priority: Normal => release_blocker

Comment 3 Manuel Hiebel 2013-07-12 18:26:23 CEST

okok

seems more upstream bug like http://sourceforge.net/mailarchive/message.php?msg_id=25334086

(btw release_blocker are used _only_ for cauldron bugs witch blocks a stable release)

Keywords: (none) => UPSTREAM
Priority: release_blocker => Normal

Comment 4 Sascha Schroeder 2013-07-16 10:00:34 CEST

(In reply to Manuel Hiebel from comment #3)
> okok
> 
> seems more upstream bug like
> http://sourceforge.net/mailarchive/message.php?msg_id=25334086
> 
> (btw release_blocker are used _only_ for cauldron bugs witch blocks a stable
> release)

1) okay, so the only thing you recommend is deactivating all these nice little features like browser plugins, Javascript and such? I will do so. But one should keep in mind that this is equivalent to not offering these options at all.

2) Regarding the status: Of course you are right. It should only emphasize how much I rely on Liferea and that there weren't such severe issues with Mageia 2. Now I know it could also be because of Webkit, Java, whatever, but this still renders my default RSS reader useless and I need it to work.

Well, let's hope that with all these new updates it will become stable. Right now it is _not_. So everyone working with it should keep that in mind.

Regards

Comment 5 Marja Van Waes 2015-03-31 16:03:52 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD