Bug 1133665

Summary: [abrt] xfce4-notifyd: gdk_x_error(): xfce4-notifyd killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Robbie Harwood <rharwood>
Component: xfce4-notifydAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: christoph.wickert, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0f4fb93ab95f3bc11b8ae08e422404792ee9e830
Whiteboard: abrt_hash:744f3ef44403e94bf154d2e763f190a0fe9735c1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 12:03:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Robbie Harwood 2014-08-25 18:29:21 UTC 
Description of problem:
I do not know what caused this problem.

Version-Release number of selected component:
xfce4-notifyd-0.2.4-4.fc22

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/lib64/xfce4/notifyd/xfce4-notifyd
crash_function: gdk_x_error
executable:     /usr/lib64/xfce4/notifyd/xfce4-notifyd
kernel:         3.17.0-0.rc1.git3.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 gdk_x_error at /lib64/libgdk-x11-2.0.so.0
 #3 _XError at /lib64/libX11.so.6
 #4 handle_error at /lib64/libX11.so.6
 #5 handle_response at /lib64/libX11.so.6
 #6 _XEventsQueued at /lib64/libX11.so.6
 #7 XPending at /lib64/libX11.so.6
 #8 gdk_event_check at /lib64/libgdk-x11-2.0.so.0
 #9 g_main_context_check at /lib64/libglib-2.0.so.0
 #10 g_main_context_iterate.isra at /lib64/libglib-2.0.so.0
 #12 gtk_main at /lib64/libgtk-x11-2.0.so.0
Comment 1 Robbie Harwood 2014-08-25 18:29:24 UTC 
Created attachment 930615 [details]
File: backtrace
Comment 2 Robbie Harwood 2014-08-25 18:29:25 UTC 
Created attachment 930616 [details]
File: cgroup
Comment 3 Robbie Harwood 2014-08-25 18:29:25 UTC 
Created attachment 930617 [details]
File: core_backtrace
Comment 4 Robbie Harwood 2014-08-25 18:29:26 UTC 
Created attachment 930618 [details]
File: dso_list
Comment 5 Robbie Harwood 2014-08-25 18:29:27 UTC 
Created attachment 930619 [details]
File: environ
Comment 6 Robbie Harwood 2014-08-25 18:29:28 UTC 
Created attachment 930620 [details]
File: limits
Comment 7 Robbie Harwood 2014-08-25 18:29:30 UTC 
Created attachment 930621 [details]
File: maps
Comment 8 Robbie Harwood 2014-08-25 18:29:30 UTC 
Created attachment 930622 [details]
File: open_fds
Comment 9 Robbie Harwood 2014-08-25 18:29:31 UTC 
Created attachment 930623 [details]
File: proc_pid_status
Comment 10 Robbie Harwood 2014-08-25 18:29:32 UTC 
Created attachment 930624 [details]
File: var_log_messages
Comment 11 Jaroslav Reznik 2015-03-03 16:14:27 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 12 Fedora End Of Life 2016-07-19 12:03:26 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.