Silently fails in Wayland session

Bug #1719945 reported by Chris Halse Rogers
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia-settings fails silently when started from the shell. When started from a terminal, it prints:

ERROR: Unable to load info from any available system

and then quits.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-settings 367.35-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 27 11:49:57 2017
InstallationDate: Installed on 2017-09-20 (7 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
SourcePackage: nvidia-settings
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Halse Rogers (raof) wrote :
Doug McMahon (mc3man)
Changed in nvidia-settings (Ubuntu):
status: New → Confirmed
Revision history for this message
Doug McMahon (mc3man) wrote :

While I can certainly confirm, what is the use case?
It would seem only useful when in a wayland session to switch from the intel profile to the nvidia one before rebooting to an xorg session. I guess that could save a little time/effort.

Revision history for this message
Chris Halse Rogers (raof) wrote : Re: [Bug 1719945] Re: Silently fails in Wayland session

It's certainly possible to log out, log in to an Xorg session, and then log out again/reboot to switch to NVIDIA. *If* you know that's what you need to do.

Since nvidia-settings silently fails *and* we default to Wayland if possible users who don't know this is what you need to do will find it very difficult to switch back from Intel.

Revision history for this message
Doug McMahon (mc3man) wrote :

Currently with hybrid systems a wayland session is presented when nvidia drivers are in use though the user is logged into wayland using the Intel gpu.
So the fact that while in wayland the user can't use nvidia-settings > prime profiles to *actually* switch back to the Intel gpu makes this bug more of an issue.

tags: added: rls-dd-incoming
removed: artful
Revision history for this message
Kristiyan Katsarov (katsar0v) wrote :

I see "ERROR: Unable to find display on any available system" when starting with Wayland. Is there and update on this issue?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.