Bug 1321914 - Several crashes exhibited when using Bluejeans plugin
Summary: Several crashes exhibited when using Bluejeans plugin
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-drv-intel
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-29 11:26 UTC by Tim Waugh
Modified: 2020-12-15 07:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:40:41 UTC
Target Upstream Version:


Attachments (Terms of Use)
xorg-x11-drv-intel-bluejeans-crash.patch (3.41 KB, patch)
2016-03-29 11:26 UTC, Tim Waugh
no flags Details | Diff

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.


Note You need to log in before you can comment on or make changes to this bug.