Bug 1105718

Summary: intermittent problems with primus bridge in GNOME 3 and cinnamon desktop
Product: [Fedora] Fedora Reporter: Gary Gatling <gsgatlin>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ajax, jrimpo, pedrogfrancisco, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:59:35 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:
Embargoed:
Attachments:
Description Flags
This is basically the upstream commit from Jan 6th by Chris Wilson none

Description Gary Gatling 2014-06-06 19:36:59 UTC
Created attachment 903020 [details]
This is basically the upstream commit from Jan 6th by Chris Wilson

Description of problem:
Primus is part of a suite of software (bumblebee) that attempts to provide
support for optimus notebooks until there is more official support in the kernel and from NVIDIA corp for such machines.

https://github.com/amonakov/primus

When using the primus bridge to run certain applications on the NVIDIA card, sometimes the window does not function properly and you get a "black" window.
I have also seen the GNOME shell crash once.

The problem is intermittent. Its hard to say how much it fails. Like maybe 1 out of 3 times or 1 out of 5 times. Here is a screenshot of what it looks like:

http://i.imgur.com/zwOsEMg.png

(should be glxgears spinning in that window)

Evidently this problem has been fixed upstream and has to with SNA vs UXA...

https://bugs.freedesktop.org/show_bug.cgi?id=73282
http://lists.freedesktop.org/archives/xorg-commit/2014-January/035794.html

The patch did not apply for me pasting it from a web browser but after re-doing the patch and installing a patched package it does seem to fix the issue with the black window. So I have included it as a attachment.


Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.21.15-5.fc20

How reproducible:

Steps to Reproduce:
1. Install bumblebee on a optimus laptop as described here:

http://fedoraproject.org/wiki/Bumblebee

Only the closed source nvidia module is working at this time. And primus bridge only supports "nvidia" anyways.

2. log into GNOME or Cinnamon desktop.

3. Run a command like:

PRIMUS_VERBOSE=2 optirun -b primus glxgears -info

Over and over again closing the old window and eventually the window that opens is black and you have to CTRL-C to get back control of your terminal.

Actual results:

A window that is all black.

Expected results:

A window with spinning gears.

Additional info:

This has been opened as a github issue here:

https://github.com/amonakov/primus/issues/140

Thanks!

Comment 1 Jeremy Rimpo 2014-09-27 05:36:11 UTC
I can confirm that this patch applied to the current intel driver src package fixes this issue. The symptoms are even worse on a KDE system and can crash kwin - though there are still some random xorg server segfaults (which don't appear to cause any visible issue) when running anything primus.

It would be good to have an official fix for those of us with optimus laptops.

Comment 2 Fedora End Of Life 2015-05-29 12:02:54 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 20:59:35 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.