Bug 963054

Thank you for the report!

I'm not really sure but I would say this is caused by retrieving problems from abrt-dbus which is performed at start up. The operation could be postponed and performed asynchronously after the window became visible.

Does it perhaps use an inefficient database and/or retrievel method?

Or, if nothing else, perhaps a message and a progress meter after the window opens.

(In reply to comment #2)
> Does it perhaps use an inefficient database and/or retrievel method?

It is more likely the method than the database.


(In reply to comment #3)
> Or, if nothing else, perhaps a message and a progress meter after the window
> open.

Sorry. I wasn't precise. I meant I do something like you say.

Sounds like you know what you're doing.

Thanks.

I've submitted a patch set which should make the start up faster but the worst case (all problems are different from each other) is not still fixed.
https://lists.fedorahosted.org/pipermail/crash-catcher/2013-July/004926.html

I've updated to the Fedora 19 version and noted it here.

Thanks for your continuing work on this problem.  I will watch for the upgrade.

By the way, I just checked the link you gave, and I wanted to note that I am not meaning a few seconds; I am meaning 20-30 seconds, and it also often stops responding on close.

(In reply to KitchM from comment #8)

How many problems do you see listed in gnome-abrt? I ran tests with 60 problems.

And regardless of the number of problems, the performance of gnome-abrt depends on the number of all installed applications in your system (because of search for a desktop entry[1] which provides the icon and the user friendly name). I'm trying to break this performance dependency but I need more time to think about it before I start coding.

Anyway, the patches mentioned in comment #6 has been already applied. So, if you want to help us, please update abrt/libreport/gnome-abrt packages from the nightly repository[2] and report the results here.


1: http://standards.freedesktop.org/desktop-entry-spec/latest/
2: http://rmarko.fedorapeople.org/

I have over 70 problems in my list.  But I am not using gnome; I am using xfce 4.10.1.  Does that make a difference?

What should I do in this case?

(In reply to KitchM from comment #10)
> I have over 70 problems in my list.  But I am not using gnome; I am using
> xfce 4.10.1.  Does that make a difference?

I would say yes. Even though gnome-abrt is pure gtk application, it benefits from GNOME because GNOME loads all Gtk stuff and probably makes the start up faster. But neither I use GNOME (I use KDE) and gnome-abrt starts reasonable fast. I will do some test in xfce.

> 
> What should I do in this case?

Well, I just wanted to know if the patches have had some performance impact in your case.

I continually (daily) update to the latest normal updates, but I have see no change that I can tell.  Sorry.

Thanks for your help.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.