Hide Forgot
Description of problem: When I start gnome-system-monitor, it begins to use all available CPU and becomes unresponsive. It seems to be using D-Bus as fast as it can. Version-Release number of selected component (if applicable): gnome-system-monitor-3.2.1-2.fc16.x86_64 How reproducible: 100% at the moment. Steps to Reproduce: 1.Log into GNOME 2.Start gnome-system-monitor Actual results: Application becomes unresponsive. From top(1): 28817 twaugh 20 0 529m 29m 11m R 48.1 1.5 0:09.53 gnome-system-mo 1621 twaugh 20 0 39196 7856 552 R 36.5 0.4 1:43.34 dbus-daemon Expected results: Not that. :-) Example backtrace while it's looping: #0 0x00000032b5ae6af3 in poll () from /lib64/libc.so.6 #1 0x00007f5439811d50 in ?? () from /lib64/libdbus-1.so.3 #2 0x00007f5439810c3d in ?? () from /lib64/libdbus-1.so.3 #3 0x00007f54397fbb45 in ?? () from /lib64/libdbus-1.so.3 #4 0x00007f54397fcea9 in ?? () from /lib64/libdbus-1.so.3 #5 0x00007f54397fc464 in dbus_connection_send_with_reply_and_block () from /lib64/libdbus-1.so.3 #6 0x00007f54397f7886 in ?? () from /lib64/libdbus-1.so.3 #7 0x00007f54397f8e3f in dbus_bus_remove_match () from /lib64/libdbus-1.so.3 #8 0x00007f54380dab0a in ?? () from /usr/lib64/gio/modules/libgioremote-volume-monitor.so #9 0x00000032b8a1145d in g_object_unref (_object=0x137fa80) at gobject.c:2746 #10 0x00000032b927d180 in g_union_volume_monitor_finalize (object= 0x114e590 [GUnionVolumeMonitor]) at gunionvolumemonitor.c:72 #11 0x00000032b8a1145d in g_object_unref (_object=0x114e590) at gobject.c:2746 #12 0x00007f54380d6a3f in ?? () from /usr/lib64/gio/modules/libgioremote-volume-monitor.so #13 0x00000032b8a113db in g_object_unref (_object=0x11a3db0) at gobject.c:2709 #14 0x00007f54380d5511 in ?? () from /usr/lib64/gio/modules/libgioremote-volume-monitor.so #15 0x00000032b7a44a7d in g_main_dispatch (context=0xc72290) at gmain.c:2425 #16 g_main_context_dispatch (context=0xc72290) at gmain.c:2995 #17 0x00000032b7a45278 in g_main_context_iterate (context=0xc72290, ---Type <return> to continue, or q <return> to quit--- block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073 #18 0x00000032b7a457c5 in g_main_loop_run (loop=0x108f020) at gmain.c:3281 #19 0x00000033561516ed in gtk_main () at gtkmain.c:1362 #20 0x000000000040fc1d in main (argc=1, argv=0x7fffe8b3c7e8) at procman.cpp:719
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.