Bug 317890 - Odd behavior after importing .opml file from Akregator 1.6.6
Summary: Odd behavior after importing .opml file from Akregator 1.6.6
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.10.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-05 17:17 UTC by Tom Littauer
Modified: 2017-01-07 22:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Littauer 2013-04-05 17:17:35 UTC
I'm moving from OpenSUSE 11.4 to 12.3 (both 64-bit on VirtualBox on AMD).

I installed 12.3 clean on a new VM and Akregator seemed to run fine. I then exported my feeds in 11.4 (AK 1.6.6, KDE 4.6) and imported them into 12.3 (AK & KDE 4.10.0).

Since doing this:

1) I can no longer move a feed from one folder to another. The UI seems to be doing what I want but when I release the mouse button no action takes place.

2) If I change to Status: Unread and leave the feed, when I return the status is back to All Articles


Reproducible: Didn't try

Steps to Reproduce:
1.Install a clean Akregator
2.Import a multiple level .OPML file
3.Try to move folders around
4.See if Status reverts to All Articles when changed.
Actual Results:  
See details

Expected Results:  
See details
Comment 1 Tom Littauer 2013-04-05 23:13:50 UTC
I have since (using YASR2) uninstalled AK, renames .kde4/config/akregatorc and .kde4/app/akregator and reinstalled.

Issue 2) above has gone away and the stus remains what it was the last time I changed it. The defaulft list of feeds has changed since I first installed implying some kind of OpenSUSE interaction. This means the product is now usable so I've moved the priority to Normal.

I still can't reorganize feeds and folders, even with the virgin re-install..
Comment 2 Denis Kurz 2016-09-24 19:42:04 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 3 Denis Kurz 2017-01-07 22:48:26 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.