Description of problem: this has been a bug off an on for KDE w/ qt 4.7. Items added to a sorted list sometimes appended to the bottom of the list unless explicitly told to. When new items are added to a sorted feed, the items are added to the bottom of the list regardless of sorting chosen. Version-Release number of selected component (if applicable): How reproducible: occasionally for some new feeds, but always once it starts to occur for a feed Steps to Reproduce: 1. add a feed 2. sort by date, so newest items show on top 3. new items are added to the bottom of the list
I think that is an upstream bug.
CC: (none) => balcaen.john
(In reply to comment #1) > I think that is an upstream bug. Correct: https://bugs.kde.org/show_bug.cgi?id=247473 They already know, so this bug can be closed for now without reporting upstream?
CC: (none) => m.van.waesSee Also: (none) => https://bugs.kde.org/show_bug.cgi?id=247473
no, we add the keyword UPSTREAM and we keep the bug open. "N.B. An UPSTREAM keyword also exists for bugs severe enough that needs to be fixed by Mageia even when upstream hasn't released yet a new version fixing the problem. In this case, the bug is kept open and UPSTREAM keyword is added, leaving it for the Mageia maintainer to close it as REPORTEDUPSTREAM if he thinks it's better. " in the triage_guide
Keywords: (none) => UPSTREAMAssignee: bugsquad => balcaen.johnSource RPM: kdepim4-4.4.11.1-2.1.mga1.src.rpm => kdepim4
I'm afraid I am not aware that this is a severe bug. But when there is a maintainer (I didn't check, I should have) shouldn't he/she always decide, regardless of how severe a bug is?
Well seems like there's a patch upstream so i'll try this week end to add it, we'll need to check for the regression pointed at least in kdepim 4.6 but if we're lucky our kdepim 4.4 won't be affected :)
Status: NEW => ASSIGNEDHardware: x86_64 => All
(In reply to comment #5) > Well seems like there's a patch upstream so i'll try this week end to add it, > we'll need to check for the regression pointed at least in kdepim 4.6 but if > we're lucky our kdepim 4.4 won't be affected :) Great that you noticed, I misunderstood and thought the 4.4 patch had to be reverted as well. From now on, I won't so easily suggest to close an upstream bug.
Ok in fact the upstream patch was reverted in mageia as upstream with patch402 ( http://svnweb.mageia.org/packages/updates/1/kdepim4/current/SOURCES/kdepim-4.4.11.1-mga-revert-maint-order-when-new-articles-are-added-kde-271794-271149-271640.patch?view=log ) because it causes kde #271640 (i just remember because i was also affected :/ ) So currently it's more a « wait for upstream to fix it indeed » :/
Blocks: (none) => 2929
Blocks: 2929 => (none)
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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. -- Mageia Bugsquad
Status: ASSIGNED => RESOLVEDResolution: (none) => WONTFIX