After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 777985 - mutter should refuse to initialize in wayland mode if the nvidia binary driver is in use
mutter should refuse to initialize in wayland mode if the nvidia binary drive...
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2017-01-31 13:46 UTC by Hans de Goede
Modified: 2021-07-05 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hans de Goede 2017-01-31 13:46:29 UTC
Just like we currently fallback to Xorg on optimus laptops with outputs connected to both GPUs we should likewise fallback to Xorg if the nvidia binary driver is used (on 1 or or more GPUs), otherwise the user just gets a black screen.

I know that people are working on nvidia binary driver support, but until that is stable it seems like a good idea to detect the nvidia binary driver and fallback to xorg, at least for 3.22.x
Comment 1 Hans de Goede 2017-01-31 15:30:10 UTC
Also see: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9f6383547e

Where users are getting a black screen due to use of the nvidia driver and there being no fallback.
Comment 2 Rui Matos 2017-01-31 17:52:05 UTC
master might need some adjustments, bug AFAICT, on 3.22.x we should already be exiting the process with an error code which should cause gdm to immediately fall back to using X. The failure should be one of:

a) failing to find a drm kms device
b) if a) succeeds, failing to create a gbm device with the retrieved kms fd
c) if b) succeeds, failing to initialize cogl/clutter due to nvidia's eglGetDisplay() failing since we pass it the gbm device

a) and b) should succeed on optimus systems but c) should fail.
Comment 3 Hans de Goede 2017-02-01 09:12:24 UTC
Ok I've asked the  "anonymous" commenter on:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-9f6383547e

To file a separate bug for his problem (the fallback does not seem to work for him).  I believe this can be closed then.
Comment 4 GNOME Infrastructure Team 2021-07-05 13:46:25 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.