Bug 1324686

Summary: Stereo cannot be enabled under GNOME 3.14.0
Product: Red Hat Enterprise Linux 7 Reporter: ctichenor
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: jkachuck, tpelka, vbenes, vsharapo
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-22 17:49:00 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:
Bug Depends On:    
Bug Blocks: 1276412    
Attachments:
Description Flags
NVIDIA Bug Report log from Fedora 23 configuration. none

Description ctichenor 2016-04-07 01:32:31 UTC
Created attachment 1144505 [details]
NVIDIA Bug Report log from Fedora 23 configuration.

Description of problem:
Stereo will not activate under RHEL 7.2 or RHEL 7.1 after GNOME update.

Version-Release number of selected component (if applicable):
Issue introduced between gnome-session 3.8.4 and 3.14.0

How reproducible:
100% of the time

Steps to Reproduce:
1. Install the NVIDIA driver
2. Configure stereo mode 10 via `sudo nvidia-xconfig --stereo=10`
3. Restart gdm
4. Run `glxgears -stereo`

Actual results:
Stereo does not activate, and there is no notification that stereo is activating.

Expected results:
A notification that stereo is being enabled appears onscreen, then stereo activates.

Additional info:
Issue does not occur under other window managers, and issue does not appear to be resolved under Fedora 23 (GNOME 3.18.4). NVIDIA driver 361.28 was used in my most recent testing, but earlier driver versions also exhibit this issue. This may also occur on other stereo modes (stereo mode 4 would likely be easiest to use without a 3D Vision-capable display), but this was not tested.

Comment 2 Ray Strode [halfline] 2016-04-22 17:49:00 UTC
I believe this regression is being tracked by bug 1305076

*** This bug has been marked as a duplicate of bug 1305076 ***