Version-Release number of selected component: xfce4-settings-4.10.1-2.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: xfsettingsd --display :0.0 --sm-client-id 2c36f6830-99ca-4cd7-9959-b77f7e1da3d0 crash_function: handle_error executable: /usr/bin/xfsettingsd kernel: 3.10.4-300.fc19.x86_64 runlevel: N 5 uid: 1338 Truncated backtrace: Thread no. 1 (8 frames) #4 handle_error at xcb_io.c:213 #5 handle_response at xcb_io.c:325 #7 _XiGetExtensionVersionRequest at XGetVers.c:93 #8 _XiGetExtensionVersion at XGetVers.c:116 #9 XGetExtensionVersion at XGetVers.c:71 #10 xfce_pointers_helper_init at pointers.c:129 #11 g_type_create_instance at gtype.c:1917 #12 g_object_constructor at gobject.c:1855 Potential duplicate: bug 867455
Created attachment 783757 [details] File: backtrace
Created attachment 783758 [details] File: cgroup
Created attachment 783760 [details] File: core_backtrace
Created attachment 783761 [details] File: dso_list
Created attachment 783762 [details] File: environ
Created attachment 783763 [details] File: limits
Created attachment 783764 [details] File: maps
Created attachment 783765 [details] File: open_fds
Created attachment 783766 [details] File: proc_pid_status
Created attachment 783767 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
I was starting F19 the first time after "fedup" from F18. At login time the abrt report was generated.
It occurred upon login after upgrade from Fedora18 to Fedora19. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: xfsettingsd --display :0.0 --sm-client-id 2a8e9c4f9-4920-4e24-b578-69e9b5eed268 crash_function: handle_error executable: /usr/bin/xfsettingsd kernel: 3.10.3-300.fc19.x86_64 package: xfce4-settings-4.10.1-2.fc19 reason: Process /usr/bin/xfsettingsd was killed by signal 5 (SIGTRAP) uid: 500
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.