Bug 1149685

Summary: [abrt] virt-manager: _gdk_x11_display_error_event(): python2.7 killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Jiří Martínek <jirinek>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: berrange, crobinso, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/827b74ca4ba3a74448e4f7bbc5ec7e2a4b74e35d
Whiteboard: abrt_hash:80860c4c12c84a2ae2b4dd429c8e9d12071da58b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-06 16:20:02 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 Jiří Martínek 2014-10-06 13:10:02 UTC 
Description of problem:
I was connected to virtual guest (Vista 32bit) using RDP (KRDC). Then I tried to reconnect to it with Virtual Manager using Spice protocol and it crashed. I tried it two or three times more, but it didn't happend again.

Version-Release number of selected component:
virt-manager-1.0.1-4.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/python2.7
kernel:         3.16.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2557
 #5 handle_error at xcb_io.c:213
 #6 handle_response at xcb_io.c:325
 #9 _gdk_x11_display_send_xevent at gdkmain-x11.c:359
 #10 _gdk_x11_display_send_selection_notify at gdkselection-x11.c:329
 #11 _gtk_selection_request at gtkselection.c:2517
 #12 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130
 #13 _g_closure_invoke_va at gclosure.c:840
 #16 gtk_widget_event_internal at gtkwidget.c:7168
 #17 gtk_widget_event at gtkwidget.c:6830
Comment 1 Jiří Martínek 2014-10-06 13:10:06 UTC 
Created attachment 944251 [details]
File: backtrace
Comment 2 Jiří Martínek 2014-10-06 13:10:07 UTC 
Created attachment 944252 [details]
File: cgroup
Comment 3 Jiří Martínek 2014-10-06 13:10:09 UTC 
Created attachment 944253 [details]
File: core_backtrace
Comment 4 Jiří Martínek 2014-10-06 13:10:10 UTC 
Created attachment 944255 [details]
File: dso_list
Comment 5 Jiří Martínek 2014-10-06 13:10:12 UTC 
Created attachment 944256 [details]
File: environ
Comment 6 Jiří Martínek 2014-10-06 13:10:13 UTC 
Created attachment 944257 [details]
File: limits
Comment 7 Jiří Martínek 2014-10-06 13:10:15 UTC 
Created attachment 944258 [details]
File: maps
Comment 8 Jiří Martínek 2014-10-06 13:10:16 UTC 
Created attachment 944259 [details]
File: open_fds
Comment 9 Jiří Martínek 2014-10-06 13:10:17 UTC 
Created attachment 944260 [details]
File: proc_pid_status
Comment 10 Jiří Martínek 2014-10-06 13:10:21 UTC 
Created attachment 944261 [details]
File: var_log_messages
Comment 11 Cole Robinson 2014-10-06 16:20:02 UTC 
Looks like something deep in gtk, hard to figure out based on a single instance. FAF shows only one hit too. Closing as INSUFFICIENT_DATA, but if other hits start rolling in we can reopen