Bug 221904

Summary:	After long time stop to work
Product:	[Applications] akregator	Reporter:	BRULE Herman <alpha_one_x86>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description BRULE Herman 2010-01-09 12:15:58 UTC

Version:            (using KDE 4.3.4)
Installed from:    Gentoo Packages

Hello, after long time (more than 5days) without stop akregator stop download the rss, when I do it manually, it seam poll it (some with red cross, and other no), but in reality no for ALL rss.
Thanks to fix it.

Comment 1 BRULE Herman 2010-02-02 14:21:39 UTC

It's possible that's liked to wifi lost of connection.

Comment 2 BRULE Herman 2010-02-20 22:29:45 UTC

Error in log (cleaned):
file retriever error: 114
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::begin: Widget painting can only begin as a result of a paintEvent
akregator(32607): Failed to lock file "/home/user/.kde4/cache-amber.fw.local/kpc/kde-icon-cache.lock" , last result = 1 
file retriever error: 114
file retriever error: 149
file retriever error: 123
file retriever error: 123

Comment 3 Denis Kurz 2016-09-24 19:44:51 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 21:30:19 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.