Bug 917222

*** Bug 917223 has been marked as a duplicate of this bug. ***

eventually, after maybe 15 minutes, it started. 
i started to report a bug and, at the end, it gave a DBUS error, and gui freezes, using ~ 20% of CPU (amd/1800 mhz)

then, i've noticed that also some perl processes (two) contribute together with abrt-gui to filling up processor cores. abrt-gui itseld used sometimes almost 90% of one core. after that, computer freezed.

after reboot, computer was very slow. looking at iotop i've seen that abrtd.service makes a lot of i/o so i've stopped it for now. if i can reproduce it, i'll report the bug.

*** Bug 917220 has been marked as a duplicate of this bug. ***

*** Bug 917221 has been marked as a duplicate of this bug. ***

Thank you for the bug report. Unfortunately, without a stack trace from the crash it is impossible to determine what caused the crash. Please see http://fedoraproject.org/wiki/StackTraces#Obtaining_a_stack_trace_using_just_GDB for more information about getting a useful stack trace with debugging symbols.  Thank you.

I'll be back home at the beginning of next month. There's nothing i can do until i get home.

attempting to run it as root:

]# abrt-gui
Can't get problem list from abrt-dbus: Timeout was reached
Error in DBus communication, falling back to direct access to '/var/spool/abrt'

and then it hangs for at least 21 minutes.

running from gdb i get:

# gdb abrt-gui
GNU gdb (GDB) Fedora (7.4.50.20120120-54.fc17)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/abrt-gui...(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install abrt-gui-2.1.2-2.fc17.i686
(gdb) run
Starting program: /usr/bin/abrt-gui 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Detaching after fork from child process 1765.
[New Thread 0xb7d40b40 (LWP 1771)]
Can't get problem list from abrt-dbus: Timeout was reached
Error in DBus communication, falling back to direct access to '/var/spool/abrt'
^C
Program received signal SIGINT, Interrupt.
0xb7fff424 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fff424 in __kernel_vsyscall ()
#1  0x4afe0486 in nanosleep () from /lib/libc.so.6
#2  0x4b01693d in usleep () from /lib/libc.so.6
#3  0xb7fb3d2f in ?? () from /lib/libreport.so.0
#4  0xb7fb4008 in dd_opendir () from /lib/libreport.so.0
#5  0x0804d263 in ?? ()
#6  0x0804d6a8 in ?? ()
#7  0x0804d76a in ?? ()
#8  0x0804f12e in ?? ()
#9  0x4b2d0b4f in g_cclosure_marshal_VOID__VOID () from /lib/libgobject-2.0.so.0
#10 0x4b2ced97 in g_closure_invoke () from /lib/libgobject-2.0.so.0
#11 0x4b2e0a3d in ?? () from /lib/libgobject-2.0.so.0
#12 0x4b2e8cf1 in g_signal_emit_valist () from /lib/libgobject-2.0.so.0
#13 0x4b2e8e74 in g_signal_emit () from /lib/libgobject-2.0.so.0
#14 0x4c5c1901 in g_application_activate () from /lib/libgio-2.0.so.0
#15 0x4c5c1c48 in ?? () from /lib/libgio-2.0.so.0
#16 0x4c5c1d8e in g_application_run () from /lib/libgio-2.0.so.0
#17 0x0804bb19 in ?? ()
#18 0x4af42635 in __libc_start_main () from /lib/libc.so.6
#19 0x0804bb81 in ?? ()

i"ll try again after installing debuginfo, if it is required.

Thank you for the backtrace. It is not necessary to install debuginfo. It has good quality for us. But it would be nice to have the output from the following commands:

$ abrt-gui -vvv
$ grep abrt /var/log/messages


I am not sure but I would say that one of the dump directories remains locked for some reason.

Created attachment 718225 [details]
abrt-gui -vvv

Created attachment 718226 [details]
grep abrt /var/log/messages

Unfortunately, it seems that the bug can no longer be reproduced. Now the behaviour is the same with the one when running as root.

Of course, still takes one hour(?) for the gui to show up but the process is no longer terminated.

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17'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 Fedora 17 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 to Fedora 17's end of life.

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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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