Bug 691881

Summary: GUI doesn't sort by last occurrence by default, and doesn't remember that sort order if you set it and restart the app
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED WONTFIX QA Contact: Nikola Pajkovsky <npajkovs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: anton, dfediuck, dhoward, dvlasenk, iprikryl, jmoskovc, kklic, mtoman, npajkovs, stephent98, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 20:25:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Adam Williamson 2011-03-29 19:00:37 UTC
Prior to 2.0, abrt-gui would sort crashes by last occurrence by default. To me this makes the most sense - you probably want to see the most recent crashes on top of the list. Now it doesn't do that any more. You can scroll across to the 'last occurrence' column and click on it (twice) to sort this way, but then if you quit abrt-gui and restart it, it's back to whatever sort method (or none) it uses by default - it doesn't remember.

I think it should default to sorting by last occurrence, and also remember any sort method the user chooses for future runs.

Comment 1 Vít Ondruch 2011-03-31 11:32:37 UTC
Unfortunately, the last occurrence column is the last one and if you have bug report such as:

"prefs.py:94:__init__:GError: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: Chyba pi voln ping serveru: IDL:omg.org/CORBA/COMM_FAILURE:1.0)"


you have to scroll far far to the right to reach the column, so I would like to see the "last occurrence" column as a first, definitely before "Problem" column.

Comment 2 Jiri Moskovcak 2011-05-02 18:52:13 UTC
Fixed in git.

Comment 3 Fedora Update System 2011-05-06 10:53:42 UTC
abrt-2.0.2-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.2-1.fc15

Comment 4 Fedora Update System 2011-05-07 15:07:09 UTC
Package abrt-2.0.2-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.2-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/abrt-2.0.2-1.fc15
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2011-05-08 04:04:36 UTC
abrt-2.0.2-3.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.2-3.fc15

Comment 6 Fedora End Of Life 2012-08-07 20:25:32 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Adam Williamson 2012-08-08 23:27:44 UTC
For the record, this seems fixed in F17, I just ran abrt and see 'last occurrence' as the default order.