Bug 184232 - Irregular appearance and articles management.
Summary: Irregular appearance and articles management.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-13 16:51 UTC by priamo
Modified: 2017-01-07 22:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description priamo 2009-02-13 16:51:20 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

update Akregator 1.3.5 to 1.4.0. I have kDE 4.2 and Kubuntu intrepid.

My problem is that in Akregator 1.4.0 the feeds unread has the same appearance that the read feeds. In the configuratio/Appearance, in theory, the unread are blue and the read red, but in the practice isn't work. 

Besides, I can't mark an article as read, I have to mark all the source/feed as read. In fact, I can't select any article to do anything. If I put the cursor on the article and i push the right button of the mouse I only can print the article, I hasn't any option.

A image of my Akregator version. The articles of the rigth one is read and the other not. The appearance is the same. Besides you can view that the program load all the articles not only the articles that I select...

http://img14.imageshack.us/img14/5554/akregatorrv9.th.png

Vincens

P.D: Excuse my english
Comment 1 Christophe Marin 2009-03-19 12:41:50 UTC
Can you attach a bigger screenshot please ?
Comment 2 priamo 2009-03-19 17:19:45 UTC
I think this will be fine.


http://cid-86f0625fa34b5394.skydrive.live.com/self.aspx/.Public/akregator.png
Comment 3 Denis Kurz 2016-09-24 19:44:36 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 22:10:50 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.