Bug 1044964 - xvfb-run segfault when xvfb killed by SIGTERM
Summary: xvfb-run segfault when xvfb killed by SIGTERM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-utils
Version: 6.6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Olivier Fourdan
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 994246 1075802 1172231
TreeView+ depends on / blocked
 
Reported: 2013-12-19 10:41 UTC by Siddharth
Modified: 2019-10-10 09:13 UTC (History)
6 users (show)

Fixed In Version: xorg-x11-utils-7.5-14.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1310021 (view as bug list)
Environment:
Last Closed: 2016-05-10 19:16:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0736 0 normal SHIPPED_LIVE X.Org client libraries bug fix and enhancement update 2016-05-10 22:28:32 UTC

Description Siddharth 2013-12-19 10:41:51 UTC 
Description of problem:
xvfb-run with xwininfo segfault after killing Xvfb with signal 15

Version-Release number of selected component (if applicable):
xorg-x11-utils-7.5-6.el6

How reproducible:
always

Steps to Reproduce:
1.open terminal and run xvfb-run
~ ]$ xvfb-run xwininfo
2.it will wait for some window to capture
3.now open another terminal and send SIGTERM to Xvfb
~ ]$ kill -15 <proc-id-Xvfb>

Actual results:
the xwininfo segfault

Expected results:
the xwininfo should not segfault

Additional info:
Comment 19 errata-xmlrpc 2016-05-10 19:16:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0736.html
Note You need to log in before you can comment on or make changes to this bug.