Version-Release number of selected component: firewall-applet-0.3.4-1.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/firewall-applet crash_function: g_logv executable: /usr/bin/python2.7 kernel: 3.10.10-200.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Oct 4 12:13:24 localhost abrt[3042]: Saved core dump of pid 1676 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-10-04-12:13:22-1676 (45281280 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 g_logv at /lib64/libglib-2.0.so.0 #1 g_log at /lib64/libglib-2.0.so.0 #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2556 #5 handle_error at xcb_io.c:213 #6 handle_response at xcb_io.c:325 #7 _XEventsQueued at xcb_io.c:364 #8 XPending at Pending.c:55 #9 gdk_check_xpending at gdkeventsource.c:266 #10 gdk_event_source_check at gdkeventsource.c:303 #11 g_main_context_check at /lib64/libglib-2.0.so.0
Created attachment 807797 [details] File: backtrace
Created attachment 807798 [details] File: cgroup
Created attachment 807799 [details] File: core_backtrace
Created attachment 807800 [details] File: dso_list
Created attachment 807801 [details] File: environ
Created attachment 807802 [details] File: limits
Created attachment 807803 [details] File: maps
Created attachment 807804 [details] File: open_fds
Created attachment 807805 [details] File: proc_pid_status
It seem to have been something with Gdk or less likely with glib2. But I'm not sure as the backtrace lacks a lot of info.
Do you have information? Have there been firewall changes at that time?
There were no firewall changes at the time--no changes period. Thanks, Greg.
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.