Can't boot using Xorg, only Wayland works on Ubuntu 18.04
I recently updated to Ubuntu 18.04 and cannot boot using Xorg only Wayland. I have tried reinstalling xorg, reinstalling nvidia drivers, setting |WaylandEnable=false| in |/etc/gdm/custom.conf| but whenever trying to login using Xorg I get a frozen screen and mouse. I am using the latest nvidia-390 driver. My laptop has a dual graphics card ie. Intel and Nvidia. I would be fine staying with Wayland however it seems unstable and a dual monitor setup isn't working. Any thoughts what I can do to get this working so I can use Xorg . Thanks, Jim
On 2018-05-14 12:09 AM, Jim Ruxton via talk wrote:
I recently updated to Ubuntu 18.04 and cannot boot using Xorg only Wayland. I have tried reinstalling xorg, reinstalling nvidia drivers, setting |WaylandEnable=false| in |/etc/gdm/custom.conf| but whenever trying to login using Xorg I get a frozen screen and mouse.
On my 18.04 system, gdm is running under Xwayland no matter what session I choose. So I'd suggest commenting out the WaylandEnable=false unless the gdm login isn't visible on your system. Also, the first time I explicitly chose "GNOME on Xorg" at the password "cog", I got a blank screen with just a mouse cursor. On reboot, GNOME is happily running on Xorg ($DESKTOP_SESSION is "gnome-xorg") — but Xwayland's still running too. Xorg is supposed to be the default for new installations under 18.04, and I was definitely running it under 17.10. I was surprised to find that after the upgrade I'd been pushed over to Xwayland. Stewart
Thanks Stewart.
I recently updated to Ubuntu 18.04 and cannot boot using Xorg only Wayland. I have tried reinstalling xorg, reinstalling nvidia drivers, setting |WaylandEnable=false| in |/etc/gdm/custom.conf| but whenever trying to login using Xorg I get a frozen screen and mouse. On my 18.04 system, gdm is running under Xwayland no matter what session I choose. So I'd suggest commenting out the WaylandEnable=false unless
On 2018-05-14 12:09 AM, Jim Ruxton via talk wrote: the gdm login isn't visible on your system. If I don't comment out WaylandEnabled = false I can't even get to the login screen so yes I have to comment this out.
Also, the first time I explicitly chose "GNOME on Xorg" at the password "cog", I got a blank screen with just a mouse cursor. On reboot, GNOME is happily running on Xorg ($DESKTOP_SESSION is "gnome-xorg") — but Xwayland's still running too.
Xorg is supposed to be the default for new installations under 18.04, and I was definitely running it under 17.10. I was surprised to find that after the upgrade I'd been pushed over to Xwayland. I am in the same boat, was using Xorg on 17.10 but cannot get it to work in 18.04. Maybe the only way to get it back is a clean install?
Jim
On 2018-05-16 12:16 PM, Jim Ruxton via talk wrote:
Thanks Stewart.
I recently updated to Ubuntu 18.04 and cannot boot using Xorg only Wayland. I have tried reinstalling xorg, reinstalling nvidia drivers, setting |WaylandEnable=false| in |/etc/gdm/custom.conf| but whenever trying to login using Xorg I get a frozen screen and mouse. On my 18.04 system, gdm is running under Xwayland no matter what session I choose. So I'd suggest commenting out the WaylandEnable=false unless
On 2018-05-14 12:09 AM, Jim Ruxton via talk wrote: the gdm login isn't visible on your system. If I don't comment out WaylandEnabled = false I can't even get to the login screen so yes I have to comment this out.
Also, the first time I explicitly chose "GNOME on Xorg" at the password "cog", I got a blank screen with just a mouse cursor. On reboot, GNOME is happily running on Xorg ($DESKTOP_SESSION is "gnome-xorg") — but Xwayland's still running too.
Xorg is supposed to be the default for new installations under 18.04, and I was definitely running it under 17.10. I was surprised to find that after the upgrade I'd been pushed over to Xwayland. I am in the same boat, was using Xorg on 17.10 but cannot get it to work in 18.04. Maybe the only way to get it back is a clean install?
I ran into the same issue - blank screen, with and without wayland. If I switch to KDE everything works. I'll dig around for bugs about it. Cheers, Jamon
On 2018-05-16 12:16 PM, Jim Ruxton via talk wrote:
Thanks Stewart.
I recently updated to Ubuntu 18.04 and cannot boot using Xorg only Wayland. I have tried reinstalling xorg, reinstalling nvidia drivers, setting |WaylandEnable=false| in |/etc/gdm/custom.conf| but whenever trying to login using Xorg I get a frozen screen and mouse. On my 18.04 system, gdm is running under Xwayland no matter what session I choose. So I'd suggest commenting out the WaylandEnable=false unless
On 2018-05-14 12:09 AM, Jim Ruxton via talk wrote: the gdm login isn't visible on your system. If I don't comment out WaylandEnabled = false I can't even get to the login screen so yes I have to comment this out.
Also, the first time I explicitly chose "GNOME on Xorg" at the password "cog", I got a blank screen with just a mouse cursor. On reboot, GNOME is happily running on Xorg ($DESKTOP_SESSION is "gnome-xorg") — but Xwayland's still running too.
Xorg is supposed to be the default for new installations under 18.04, and I was definitely running it under 17.10. I was surprised to find that after the upgrade I'd been pushed over to Xwayland. I am in the same boat, was using Xorg on 17.10 but cannot get it to work in 18.04. Maybe the only way to get it back is a clean install?
https://bugs.launchpad.net/ubuntu/bionic/+source/gdm3/+bug/1766137 looks relevant - with a link to https://bugzilla.gnome.org/show_bug.cgi?id=795940
I recently updated to Ubuntu 18.04 and cannot boot using Xorg only Wayland. I have tried reinstalling xorg, reinstalling nvidia drivers, setting |WaylandEnable=false| in |/etc/gdm/custom.conf| but whenever trying to login using Xorg I get a frozen screen and mouse. On my 18.04 system, gdm is running under Xwayland no matter what session I choose. So I'd suggest commenting out the WaylandEnable=false unless the gdm login isn't visible on your system. If I don't comment out WaylandEnabled = false I can't even get to the login screen so yes I have to comment this out. Also, the first time I explicitly chose "GNOME on Xorg" at the password "cog", I got a blank screen with just a mouse cursor. On reboot, GNOME is happily running on Xorg ($DESKTOP_SESSION is "gnome-xorg") — but Xwayland's still running too.
Xorg is supposed to be the default for new installations under 18.04, and I was definitely running it under 17.10. I was surprised to find that after the upgrade I'd been pushed over to Xwayland. I am in the same boat, was using Xorg on 17.10 but cannot get it to work in 18.04. Maybe the only way to get it back is a clean install? https://bugs.launchpad.net/ubuntu/bionic/+source/gdm3/+bug/1766137 looks relevant - with a link to https://bugzilla.gnome.org/show_bug.cgi?id=795940 Thank you I looked at this however there is no discussion with that bug to suggest a problem with logging in on Xorg vs Wayland so it appears to be a different issue. jim
| From: Jim Ruxton via talk <talk@gtalug.org> | I recently updated to Ubuntu 18.04 and cannot boot using Xorg only Wayland. If you can ssh into the machine you might be able to discover what's going on. There are also various log files that might give a hint.
On 2018-05-16 04:04 PM, D. Hugh Redelmeier via talk wrote:
If you can ssh into the machine you might be able to discover what's going on.
I did the full 18.04 upgrade on an older laptop with dual Intel/Nvidia graphics. It's hard-locking on trying to start gdm, and won't even talk over ethernet or respond to Magic SysRq. Stewart
On 2018-05-16 04:04 PM, D. Hugh Redelmeier via talk wrote:
If you can ssh into the machine you might be able to discover what's going on. I did the full 18.04 upgrade on an older laptop with dual Intel/Nvidia graphics. It's hard-locking on trying to start gdm, and won't even talk over ethernet or respond to Magic SysRq. If I could ssh in via Ethernet while it is crashed what should I look for? My card is also dual Intel/Nvidia. Magic SysRq works for me as a way to reboot the machine. I have filed a bug report with Bugzilla. If i get any results there I will post them here. Maybe you want to add to
On 2018-05-18 07:10 PM, Stewart C. Russell via talk wrote: the Bug report? https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771661 Jim
Stewart --- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
| From: Jim Ruxton via talk <talk@gtalug.org> | If I could ssh in via Ethernet while it is crashed what should I look for? My | card is also dual Intel/Nvidia. Magic SysRq works for me as a way to reboot | the machine. I have filed a bug report with Bugzilla. If i get any results | there I will post them here. Maybe you want to add to the Bug report? | https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771661 I don't run Ubuntu, so this is just guess-work. 1) I detest running a proprietary driver. You could just use the Intel driver. That might well work. What have you got to lose? 2) Is bumblebee still the way to support these intel/nvidia chimera systems? 3) guess: GDM probably is wayland-only. Can you switch to LightDM, for example? That's what Ubuntu used to use. ==== when SSHed into your hung system 4) see what processes are running (ps) 5) see what the last bunch of lines from dmesg say. The problem may well be reported there. 6) I think ubuntu now uses journald. So look at the output of "journalctl -b". Focus on the last page or two of output, but do scan it all. 7) look at the most recent file in your home directory "ls -latr'. You might find an X error log. ~/.xsession-errors, I think 8) anywhere else the clues lead you.
Today I got Xorg loading.I did the following: sudo apt-get purge nvidia* sudo apt install nvidia-kernel-source-396 sudo apt install nvidia-driver-396 Unfortunately this still didn't work at this point so I removed /etc/X11/xorg.conf Then I booted into Gnome with Xorg. Removing Xorg.conf may have been the trick all along. I may not have needed to update the nvidia drivers . I tried regenerating xorg.conf with nvidia-xconfig . Again using this generated xorg.conf I couldn't boot into Xorg so removed it again. Unfortunately using the nvidia card I still cant run dual monitors. I don't see my HDMI monitor with either nvidia-settings or the gnome display settings. Using nvidia prime if I select the intel card I can use dual monitors. Super frustrating that I can't see the second monitor using nvida but at least I got Xorg booting. I hope this helps you Stewart. Cheers, Jim On 2018-05-18 07:10 PM, Stewart C. Russell via talk wrote:
On 2018-05-16 04:04 PM, D. Hugh Redelmeier via talk wrote:
If you can ssh into the machine you might be able to discover what's going on. I did the full 18.04 upgrade on an older laptop with dual Intel/Nvidia graphics. It's hard-locking on trying to start gdm, and won't even talk over ethernet or respond to Magic SysRq.
Stewart --- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
On 2018-05-23 02:37 AM, Jim Ruxton via talk wrote:
Today I got Xorg loading.
Yay! Me too - I think we must have been working on it about the same time. Yes, I've found many of the same shortcomings you did in the current setup, but I'm confident that Ubuntu will get the upstream patch applied soon. Like you, I did: sudo apt-get purge nvidia* but I also saw this in .xsession-errors dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments which led me to this Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731614 which made me try: sudo apt-remove --purge gdm3 sudo apt install lightdm ubuntu-session Rebooting got me to the lightdm prompt, which worked for login. I think I'm running in unaccelerated fallback mode, but I have working graphics now. Thanks for the help! Stewart
Thanks for the update. Great you got things working on your end as well. Have you tried a second monitor by any chance to see if that is working for you? Jim
Today I got Xorg loading. Yay! Me too - I think we must have been working on it about the same time. Yes, I've found many of the same shortcomings you did in the current setup, but I'm confident that Ubuntu will get the upstream patch applied soon.
Like you, I did:
sudo apt-get purge nvidia*
but I also saw this in .xsession-errors
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments
which led me to this Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731614
which made me try:
sudo apt-remove --purge gdm3 sudo apt install lightdm ubuntu-session
Rebooting got me to the lightdm prompt, which worked for login. I think I'm running in unaccelerated fallback mode, but I have working graphics now.
Thanks for the help!
Stewart
Hi Jim -
Have you tried a second monitor by any chance to see if that is working for you?
Yes, it does. It's using the Nouveau open source driver, which — while a little slower than the Nvidia proprietary driver — also runs a lot cooler. This is on a ~2013 vintage Samsung i7 quad core laptop which tends to run hot. cheers, Stewart
Have you tried a second monitor by any chance to see if that is working for you? Yes, it does. It's using the Nouveau open source driver, which — while a little slower than the Nvidia proprietary driver — also runs a lot cooler. This is on a ~2013 vintage Samsung i7 quad core laptop which tends to run hot.
Thanks Stewart. I posted something on the Nvidia Developer Forum and am working there with someone to get this working correctly. Hopefully something will come of it but it sounds like Ubuntu will have to release a patch. Here is the link https://devtalk.nvidia.com/default/topic/1035768/linux/ubuntu-18-04-can-t-se...
participants (4)
-
D. Hugh Redelmeier -
Jamon Camisso -
Jim Ruxton -
Stewart C. Russell