Bug 1324686 - Stereo cannot be enabled under GNOME 3.14.0
Summary: Stereo cannot be enabled under GNOME 3.14.0
Keywords:
Status: CLOSED DUPLICATE of bug 1305076
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-session
Version: 7.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1276412
TreeView+ depends on / blocked
 
Reported: 2016-04-07 01:32 UTC by ctichenor
Modified: 2016-04-22 17:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-22 17:49:00 UTC
Target Upstream Version:


Attachments (Terms of Use)
NVIDIA Bug Report log from Fedora 23 configuration. (231.89 KB, application/x-gzip)
2016-04-07 01:32 UTC, ctichenor
no flags Details

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 ***


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