[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
I am using XPS 13 9360, it happens often that the login session goes without wayland. Here is the log I got from running journalctl /usr/bin/gnome-shell Dec 15 12:45:45 cico-XPS-13-9360 gnome-shell[883]: Failed to apply DRM plane transform 0: Permission denied Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: (EE) Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: Fatal server error: Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: (EE) wl_drm@4: error 0: authenicate failed Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: (EE) Dec 15 12:45:46 cico-XPS-13-9360 gnome-shell[883]: X Wayland crashed; aborting Dec 15 12:45:47 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage" Dec 15 12:45:47 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup" Dec 15 12:45:47 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfig Dec 15 12:45:48 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" Dec 15 12:45:48 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: [resource:///org/gnome/gjs/modules/tweener/tweener.js 540]: reference to undefined property "isSpecialProperty" Dec 15 12:45:48 cico-XPS-13-9360 gnome-shell[1030]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.Per Dec 15 12:45:48 cico-XPS-13-9360 org.gnome.Shell.desktop[1030]: Window manager warning: "XF86RFKill" is not a valid accelerator Dec 15 12:45:49 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 29]: reference to undefined property "MetaWindowX11" Dec 15 12:46:02 cico-XPS-13-9360 gnome-shell[1809]: Failed to read monitors config file '/home/cico/.config/monitors.xml': Logical monitor scales must be identical Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage" Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup" Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfig Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Adrian, thank you very much. Your advice saved me a lot of money. I unfortunately own an MSI GX70 notebook with two GPUS: Radeon HD 8650 G Richland and Radeon HA 8970 G Neptune. It wouldn't load without nomodest option in grub configuration. While fglrx lasted, it was bearable. After 16.04, however, nomodeset started to block installing amdgpu driver. With MUTTER_ALLOW_HYBRID_GPUS=1, however, the notebook booted without nomodeset, also it switched to integrated Radeon HD 8650 G Richland automatically. I will still have to figure out how to switch to the discrete GPU when it is required but the notebook is already getting to be usable again after one and a half years. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
I had the same problem with Intel + AMD tandem on a desktop. I solved it by adding in /etc/environment: MUTTER_ALLOW_HYBRID_GPUS=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1402283. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-12-07T07:42:06+00:00 mvetter wrote: Created attachment 1228916 failed_wayland_gnome_shell_log.txt (journalctl) Description of problem: On a system with two graphics cards (Intel integrated graphics controller and an AMD discrete card), gnome-shell crashes in wayland mode (returns to the gdm login screen). The machine is using the Intel integrated graphics for video output. The AMD card has no monitors attached to it. It's only used for GPGPU computing via OpenCL. When the AMD card is removed, gnome-shell works correctly in wayland mode. Version-Release number of selected component (if applicable): 3.22.2-2.fc25 How reproducible: Always. Steps to Reproduce: 1. install second graphics card 2. boot machine 3. gnome-shell fails in Wayland mode Actual results: gnome-shell does not work in Wayland mode when two graphics cards are present. Expected results: gnome-shell should work in Wayland mode, no matter how many video cards the system has. Additional info: kernel 4.8.11-300 extract from lspci: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland GL [FirePro W2100] journalctl log has: Dec 07 16:32:49 localhost.localdomain gnome-shell[]: Can't initialize KMS backend: could not find drm kms device Dec 07 16:32:49 localhost.localdomain gnome-session[2189]: gnome-session-binary[2189]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: Unrecoverable failure in required component org.gnome.Shell.desktop Dec 07 16:32:49 localhost.localdomain gdm-password][2164]: pam_unix(gdm-password:session): session closed for user tmp I've attached two logs: one for booting into gdm, and one for attempting to log in using gnome-shell. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/0 On 2016-12-07T07:43:50+00:00 mvetter wrote: Created attachment 1228917 failed_gdm_log.txt (journalctl) Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/1 On 2016-12-07T08:41:54+00:00 mvetter wrote: Same problem happens when the AMD card is swapped out for an Nvidia card. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/2 On 2016-12-12T17:34:01+00:00 sebby2k wrote: I can confirm this also happens on my system. Logging into Fedora 25 Gnome wayland session fails on Dell laptop with Intel Haswell CPU and discrete Radeon HD 8790M graphics. This used to work fine on F24 w/ 4.7.x kernel. Hardware name: Dell Inc. Latitude E6540/0725FP Version-Release number of selected component (if applicable): Name: kernel-core Arch: x86_64 Epoch : 0 Version : 4.8.11 Release : 300.fc25 Name: gnome-shell Arch: x86_64 Epoch : 0 Version : 3.22.2 Release : 2.fc25 Name: mutter Arch: i686 Epoch : 0 Version : 3.22.2 Release : 3.fc25 I ended up disabling radeon kms mode setting by adding radeon.modeset=0 to grub. With this kernel configuration, I can now start Gnome Wayland session successfully Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/3 On 2017-01-02T19:34:17+00:00 Carwyn wrote: Same with these two cards on F25: 0:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) nouveau is the primary with the i915 unused. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/4 On 2017-01-02T22:12:21+00:00 Carwyn wrote: Seems to be a similar problem to bug #1403512 Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/5 On 2017-05-04T08:09:10+00:00 Pavel wrote: Same here, workaround with radeon.modeset=0 helped with the
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
modeset=0 sounds similar to the workaround for bug 1705369. Although the symptoms are a bit different. ** Also affects: gdm3 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1402283 Importance: Unknown Status: Unknown ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
It worked! I switched my machine back to hybrid mode (so that both Intel and Nvidia cards are visible in lspci) and added the nouveau.modeset=0 kernel parameters. And now I am able to select the Ubuntu (wayland) option and indeed it works: XDG_SESSION_TYPE=wayland, and the About dialog shows "Intel® HD Graphics 530 (Skylake GT2)" as the Graphics card. Thanks! So the bug is indeed in gnome-shell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Daniel, thank you so much for your time investigating this, I appreciate it. The /etc/modprobe.d definitely exists: $ ls -la /etc/modprobe.d/ total 76 drwxr-xr-x 2 root root 4096 okt 23 11:51 . drwxr-xr-x 153 root root 12288 okt 23 11:51 .. -rw-r--r-- 1 root root 2507 júl 31 2015 alsa-base.conf -rw-r--r-- 1 root root 325 mar 13 2016 blacklist-ath_pci.conf -rw-r--r-- 1 root root 1603 mar 13 2016 blacklist.conf -rw-r--r-- 1 root root 210 mar 13 2016 blacklist-firewire.conf -rw-r--r-- 1 root root 697 mar 13 2016 blacklist-framebuffer.conf -rw-r--r-- 1 root root 156 júl 31 2015 blacklist-modem.conf lrwxrwxrwx 1 root root41 sep 5 2016 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.conf -rw-r--r-- 1 root root 583 mar 13 2016 blacklist-rare-network.conf -rw-r--r-- 1 root root 1077 mar 13 2016 blacklist-watchdog.conf -rw-r--r-- 1 root root 127 feb 7 2017 dkms.conf -rw-r--r-- 1 root root 154 nov 10 2015 intel-microcode-blacklist.conf -rw-r--r-- 1 root root 347 mar 13 2016 iwlwifi.conf -rw-r--r-- 1 root root 379 júl 28 2016 mdadm.conf -rw-r--r-- 1 root root 104 mar 13 2016 mlx4.conf -rw-r--r-- 1 root root68 dec 28 2015 osspd.conf -rw-r--r-- 1 root root30 mar 3 2016 vmwgfx-fbdev.conf I am typing this from my wayland-enabled session, and the journalctl also contains those lines: okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin kernel: new mount options do not match the existing superblock, will be ignored okt 23 08:41:32 mavi-vaadin anacron[1079]: Will run job `cron.daily' in 5 min. okt 23 08:41:32 mavi-vaadin anacron[1079]: Jobs will be executed sequentially okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin avahi-daemon[1078]: Found user 'avahi' (UID 113) and group 'avahi' (GID 122). okt 23 08:41:32 mavi-vaadin avahi-daemon[1078]: Successfully dropped root privileges. okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin avahi-daemon[1078]: avahi-daemon 0.6.32 starting up. okt 23 08:41:32 mavi-vaadin ModemManager[1080]: ModemManager (version 1.6.8) starting in system bus... okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: Error: can't open /lib/modules/4.13.0-16-generic/updates/dkms okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_ I have the root FS encrypted by LLVM/dmcrypt, and it couldn't have been mounted so soon, since it takes cca 2 seconds to enter my password. Could that be the reason of seeing those error messages? Anyways, since those messages are present and I'm able to run wayland, this leads me to believe that those lines are unconnected to this issue. Anyways, googling for the gnome-shell error message did in fact found something very interesting: https://bugzilla.redhat.com/show_bug.cgi?id=1402283 It seems that even on non-hybrid desktop systems with two completely separate graphic cards gnome-shell seemingly can't find drm kms device (even though there are two of those). So the error message may be misleading, since disabling kms on second card in fact works around this issue. I will try the same and disable KMS on nouveau and let you know. Thanks again for looking into this issue! ** Bug watch added: Red Hat Bugzilla #1402283 https://bugzilla.redhat.com/show_bug.cgi?id=1402283 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
I can see your system choosing to use X very early... It looks like you have a partially broken system (from upgrades/nvidia- installer/hacking/something else): okt 20 13:13:21 mavi-vaadin gpu-manager[1130]: /etc/modprobe.d is not a file okt 20 13:13:21 mavi-vaadin gpu-manager[1130]: /etc/modprobe.d is not a file okt 20 13:13:21 mavi-vaadin gpu-manager[1130]: /etc/modprobe.d is not a file okt 20 13:13:21 mavi-vaadin gpu-manager[1130]: /etc/modprobe.d is not a file okt 20 13:13:21 mavi-vaadin gpu-manager[1130]: Error: can't open /lib/modules/4.13.0-16-generic/updates/dkms okt 20 13:13:21 mavi-vaadin gpu-manager[1130]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf So you can try rebuilding that with: sudo apt install --reinstall kmod dkms Later in the log, your problem becomes more apparent: okt 20 13:13:28 mavi-vaadin gnome-shell[1666]: Can't initialize KMS backend: could not find drm kms device That will definitely mean Wayland is not an option. Try the above fix. And if that doesn't work then please log a bug on bugzilla.gnome.org mentioning that: okt 20 13:13:28 mavi-vaadin gnome-shell[1666]: Can't initialize KMS backend: could not find drm kms device when you have both: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) Subsystem: Lenovo HD Graphics 530 Kernel driver in use: i915 Kernel modules: i915 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1000M] (rev a2) Subsystem: Lenovo GM107GLM [Quadro M1000M] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4978285/+files/huhu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Sorry, make that the output of just: journalctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Ah, sorry. Please repeat the test but then also collect the output of: journalctl /usr/bin/gnome-shell and attach it here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
** Attachment added: "mutter log 3" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975773/+files/mutter-2156-debug-log-D3L47Y-nokeycode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Attaching mutter log; but removing lines such as these: KEYBINDINGS: Grabbing keybinding keycode 133 mask 0x0 on 0x15a Since it may reveal my password. ** Attachment added: "mutter log 2" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975772/+files/mutter-1742-debug-log-9BRH8Y-nokeycode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
** Attachment added: "mutter log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975771/+files/mutter-1662-debug-log-H7DC8Y -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Yes, please attach the log files. And yes, most hybrid laptops have the Intel GPU wired to the panel. The Nvidia GPU (if enabled) just shares rendered frames with the Intel GPU. And it's the same display system regardless of whether Nvidia is enabled or disabled, so there's never any interruption to the picture on-screen as Nvidia is powered up/down. It's also normal for the Nvidia GPU to have ownership of one of the HDMI/display ports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Correction: *those two cards are not completely separate but need to cooperate somehow (since Intel's connected to the panel while Nvidia's connected to HDMI, but they need to cooperate, for example when Intel needs to draw over HDMI when an external monitor is connected) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Thank you for your responses, and I apologize if I sounded rude - I didn't meant to. I rebooted in the hybrid mode and added the abovementioned lines into /etc/environment, unfortunately the /tmp/mutterlogs file is not created. There are other files though: $ ls -la /tmp/mutter* -rw--- 1 gdm gdm 468 okt 19 12:12 /tmp/mutter-1444-debug-log-BN1E8Y -rw--- 1 gdm gdm 77041 okt 19 12:12 /tmp/mutter-1521-debug-log-XFRL8Y -rw--- 1 mavi mavi 493891 okt 19 12:15 /tmp/mutter-1931-debug-log-POR97Y I'm not sure if they would be helpful to you. I have verified that the env variables are indeed set: $ echo $WAYLAND_DEBUG 1 I wondered that the file might be deleted by the auto-cleanup of /tmp, so I created world-writable /foo directory and set MUTTER_USE_LOGFILE=/foo/mutterlogs but nothing got created in /foo. Please let me know if you'd need the contents of those files. Yet they contain nothing wayland-specific: $ sudo cat /tmp/mutter* |grep -i wayl VERBOSE: Using _NET_WM_NAME for new title of 0x3a1 (Bug #17245): "Bug #1724583 “gdm3 in Ubuntu 17.10 doesn't list wayland sessions...” : Bugs : gdm3 package : Ubuntu - Chromium" VERBOSE: Ignoring WM_NAME "Bug #1724583 “gdm3 in Ubuntu 17.10 doesn't list wayland sessions...” : Bugs : gdm3 package : Ubuntu - Chromium" as _NET_WM_NAME is set cat of the first file: $ sudo cat /tmp/mutter-1444-debug-log-BN1E8Y VERBOSE: Mutter version 3.26.1 running on 19.10.2017 VERBOSE: Running in locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=sk_SK.UTF-8;LC_TIME=sk_SK.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=sk_SK.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=sk_SK.UTF-8;LC_NAME=sk_SK.UTF-8;LC_ADDRESS=sk_SK.UTF-8;LC_TELEPHONE=sk_SK.UTF-8;LC_MEASUREMENT=sk_SK.UTF-8;LC_IDENTIFICATION=sk_SK.UTF-8" with encoding "UTF-8" VERBOSE: Compiled with randr extension VERBOSE: Compiled with startup notification Perhaps it is as you say - GDM3 sees two graphic cards, assumes hybrid mode and simply disables Wayland right off the bat; perhaps we will need to wait until Mutter 3.27.1 is released. I was probably wrong: those two cards are not completely separate but need to cooperate somehow (since Intel's connected to the panel while Nvidia's connected to HDMI), and perhaps Mutter needs to do some magic to support that? More info at https://bugzilla.gnome.org/show_bug.cgi?id=785381 ** Bug watch added: GNOME Bug Tracker #785381 https://bugzilla.gnome.org/show_bug.cgi?id=785381 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
OK, please try adding these to your /etc/environment and reboot with the BIOS setup to enable hybrid: MUTTER_VERBOSE=1 MUTTER_DEBUG=1 MUTTER_USE_LOGFILE=/tmp/mutterlogs MUTTER_DEBUG_SM=1 MUTTER_DEBUG_BUTTON_GRABS=1 WAYLAND_DEBUG=1 Now do you get any useful information in /tmp/mutterlogs ? ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
I know sorry, but didn't explain myself well enough. You're right - changing the BIOS setting (or unplugging discrete graphics cards) is the solution right now. And soon in 18.04 you won't need to do either, when Mutter's hybrid support is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
GDM3 will certainly hide the Wayland options if any part of the Wayland start-up crashed. It catches the crash and just hides the option from you. So maybe we need to debug that and look for a hidden crash...? ** Changed in: gdm3 (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
I believe this is a bug in GDM3 detection algorithm which incorrectly disables Wayland support on a system which runs just fine with Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Thanks for the info on Hybrid mode - really nice! However, what I'd like is to run Ubuntu+Wayland on my Intel card only. So, I don't want to run it in hybrid mode, I don't want to run it on NVIDIA proprietary, just on the Intel card. KDE Plasma+Wayland runs fine and uses Intel only; GDM3 forces me to use Xorg for unknown reason. The only workaround is to "set the Discrete mode in BIOS" which only hides Intel card; then GDM3 allows me to run Wayland (on top of Nouveau). Works for me; yet I would still prefer to use just the Intel+Wayland configuration. Please, let me know how I can make myself more clear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Thanks. I know Wayland+KMS doesn't work with NVIDIA proprietary. However, I don't use NVIDIA proprietary drivers and I don't have them installed and I don't want to use Wayland on NVIDIA proprietary. Thus, your conclusion is not right. When I enable "Hybrid" mode in BIOS, I believe that both VGA cards (Intel and Nvidia) are made available to the system (as shown by dmesg); OS is free to use any of those. Typically Linux only uses Intel and ignores Nvidia in this mode - that is completely fine and that's what I want - to run Wayland on top of Intel. The problem is that Wayland doesn't work with the Intel-based graphic card for me, on this very laptop when both video cards are visible. Or perhaps GDM3 detects more than one graphic card and disables Wayland support. Or perhaps GDM3 detects Skylake Intel chipset and disables Wayland support. I don't know - GDM3 logs nothing usable to its log even when in debug mode, so it is unclear what is the reason behind disabling Wayland support. To sum it up: I want to use Wayland on Intel, but GDM3 won't allow me to do so, and it doesn't provide any hints as to why. KDE Plasma on Wayland *RUNS FINE* on this very configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
