Bug 1321914

Summary: Several crashes exhibited when using Bluejeans plugin
Product: Red Hat Enterprise Linux 7 Reporter: Tim Waugh <twaugh>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: qguo, tpelka
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:40:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xorg-x11-drv-intel-bluejeans-crash.patch none

Description Tim Waugh 2016-03-29 11:26:51 UTC 
Created attachment 1141205 [details]
xorg-x11-drv-intel-bluejeans-crash.patch

Description of problem:
Original report against Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=1226390

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.99.917-8.20150615.el7.x86_64
xorg-x11-server-Xorg-1.17.2-10.el7.x86_64
See https://bugzilla.redhat.com/show_bug.cgi?id=1226390#c24

How reproducible:
I think this is 100% reproducible using an older version of the Bluejeans plugin (link in bug #1226390).

Steps to Reproduce:
1. Dial-in in bluejeans conference.
2. Other person starts sharing screen.
3. Other person stops sharing screen. At this point my server crashes.

Actual results:
X crash

Expected results:
No X crash

Additional info:
In bug #1226390 I attached a patch which fixes 3 different causes of Bluejeans crashes that I found. I'll attach it here as well.
Comment 2 RHEL Program Management 2020-12-15 07:40:41 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.