Bug 1188182

Summary: [abrt] vino: XQueryExtension(): vino-server killed by SIGSEGV
Product: [Fedora] Fedora Reporter: lejeczek <peljasz>
Component: vinoAssignee: Søren Sandmann Pedersen <sandmann>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: debarshir, dvacek, jorti, liblit, peljasz, sandmann, vkngbrsrkr
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5cc45d601dd299b00eb780b9f220813a2379058a
Whiteboard: abrt_hash:71e50e3172c346f84137b4107c8bba4f87158975
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 12:45:23 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description lejeczek 2015-02-02 09:44:20 UTC 
Description of problem:
activated destkop sharing and logged in to gnome@wayland

Version-Release number of selected component:
vino-3.15.4-1.fc22

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/libexec/vino-server
crash_function: XQueryExtension
executable:     /usr/libexec/vino-server
kernel:         3.19.0-0.rc6.git3.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 XQueryExtension at QuExt.c:43
 #1 get_xinput_base at XTest.c:79
 #2 find_display at XTest.c:83
 #3 XTestQueryExtension at XTest.c:101
 #4 vino_input_init at server/vino-input.c:761
 #5 name_acquired at server/vino-main.c:152
 #6 do_call at gdbusnameowning.c:215
 #7 request_name_cb at gdbusnameowning.c:327
 #8 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #9 g_dbus_connection_call_done at gdbusconnection.c:5508
Comment 1 lejeczek 2015-02-02 09:44:22 UTC 
Created attachment 987027 [details]
File: backtrace
Comment 2 lejeczek 2015-02-02 09:44:23 UTC 
Created attachment 987028 [details]
File: cgroup
Comment 3 lejeczek 2015-02-02 09:44:25 UTC 
Created attachment 987029 [details]
File: core_backtrace
Comment 4 lejeczek 2015-02-02 09:44:26 UTC 
Created attachment 987030 [details]
File: dso_list
Comment 5 lejeczek 2015-02-02 09:44:27 UTC 
Created attachment 987031 [details]
File: environ
Comment 6 lejeczek 2015-02-02 09:44:28 UTC 
Created attachment 987032 [details]
File: exploitable
Comment 7 lejeczek 2015-02-02 09:44:29 UTC 
Created attachment 987033 [details]
File: limits
Comment 8 lejeczek 2015-02-02 09:44:30 UTC 
Created attachment 987034 [details]
File: maps
Comment 9 lejeczek 2015-02-02 09:44:31 UTC 
Created attachment 987035 [details]
File: open_fds
Comment 10 lejeczek 2015-02-02 09:44:32 UTC 
Created attachment 987036 [details]
File: proc_pid_status
Comment 11 lejeczek 2015-02-02 09:44:33 UTC 
Created attachment 987037 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 16:48:51 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 13 Fedora End Of Life 2016-07-19 12:45:23 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.