Description of problem: Starting fedmsg Version-Release number of selected component: python-2.7.3-13.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/gnome-clocks crash_function: _gdk_x11_display_error_event executable: /usr/bin/python2.7 kernel: 3.6.7-5.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2416 #6 handle_error at xcb_io.c:212 #8 XIQueryDevice at XIQueryDevice.c:60 #9 translate_hierarchy_event at x11/clutter-device-manager-xi2.c:411 #10 clutter_device_manager_xi2_translate_event at x11/clutter-device-manager-xi2.c:725 #11 clutter_backend_real_translate_event at ./clutter-backend.c:572 #12 clutter_x11_handle_event at x11/clutter-event-x11.c:199 #13 gtk_clutter_filter_func at ./gtk-clutter-embed.c:231 #14 gdk_event_apply_filters at gdkeventsource.c:81 #15 gdk_event_source_translate_event at gdkeventsource.c:195
Created attachment 652503 [details] File: backtrace
Created attachment 652504 [details] File: cgroup
Created attachment 652505 [details] File: core_backtrace
Created attachment 652506 [details] File: dso_list
Created attachment 652507 [details] File: environ
Created attachment 652508 [details] File: limits
Created attachment 652509 [details] File: maps
Created attachment 652510 [details] File: open_fds
Created attachment 652511 [details] File: proc_pid_status
Thanks for filing this bug report. Looking at attachment 652503 [details] I see that the error happened in thread 1: an XI_BadDevice message was received from the X server. Various other threads are running, so my hunch is that more than one thread tried to communicate with the X server, leading to the "conversation" with the server getting garbled - though that's just a hunch. Reassigning from "python" to "gnome-clocks"
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.