Just wanted to follow up with some good news and maybe something you
folks can use to help fix this one should it ever come around on the
guitar? :)
I found I was able to get Gnome to start up correctly on boot if I just
add this line to the [daemon] section of /etc/gdm3/custom.conf:
WaylandEnable=false
I added that as a comment to https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1796614
If I have more time I'd love to dig into the C code and figure out what
about Wayland detection is failing - the Alienware 17 R5 has the Nvidia
GTX 1080 as well as the Intel graphics chipset for longer batter life
when not gaming / doing high end 3D. I wonder if the Wayland detection
is getting fouled up on that?
Anyway, I am loving 18.10 now that I have the issues ironed out. Once
again thank you for all the work you do on both the software and the
community!
-Chris
On Fri, Oct 12, 2018, at 3:35 PM, Will Cooke wrote:
> Hi Christopher. Yes, we think this bug is fixed, but the "only
> getting> a flashing cursor" problem is a different bug. We're still working on> it right now. Most of the work is happening on the upstream bug
> https://gitlab.gnome.org/GNOME/gdm/issues/428#note_338918 and it's
> associated cnages
> https://gitlab.gnome.org/GNOME/gdm/merge_requests/37>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1796614).
> https://bugs.launchpad.net/bugs/1795637
>
> Title:
> No login screen when booting Cosmic due to plymouth racing with the> rest of the boot process and not releasing DRM devices in time
>
> Status in gdm3 package in Ubuntu:
> Invalid
> Status in plymouth package in Ubuntu:
> Fix Released
> Status in gdm3 source package in Cosmic:
> Invalid
> Status in plymouth source package in Cosmic:
> Fix Released
>
> Bug description:
> Booting a fresh install of Cosmic from the ISO generated 1 Oct 2018> doesnt present a log in screen. Switching to tty2 and then
> back to 1> makes the log in screen appear.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.10
> Package: gdm3 3.30.1-1ubuntu1
> ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
> Uname: Linux 4.18.0-8-generic x86_64
> ApportVersion: 2.20.10-0ubuntu11
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Oct 2 13:23:42 2018
> InstallationDate: Installed on 2018-10-02 (0 days ago)
> InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64
> (20181001)> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile..etc.gdm3.custom.conf: 2018-10-02T13:15:45.550495
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+subscriptions
Hi Will!
Just wanted to follow up with some good news and maybe something you custom. conf:
folks can use to help fix this one should it ever come around on the
guitar? :)
I found I was able to get Gnome to start up correctly on boot if I just
add this line to the [daemon] section of /etc/gdm3/
WaylandEnable=false
I added that as a comment to /bugs.launchpad .net/ubuntu/ +source/ gdm3/+bug/ 1796614
https:/
If I have more time I'd love to dig into the C code and figure out what
about Wayland detection is failing - the Alienware 17 R5 has the Nvidia
GTX 1080 as well as the Intel graphics chipset for longer batter life
when not gaming / doing high end 3D. I wonder if the Wayland detection
is getting fouled up on that?
Anyway, I am loving 18.10 now that I have the issues ironed out. Once
again thank you for all the work you do on both the software and the
community!
-Chris
On Fri, Oct 12, 2018, at 3:35 PM, Will Cooke wrote: /gitlab. gnome.org/ GNOME/gdm/ issues/ 428#note_ 338918 and it's /gitlab. gnome.org/ GNOME/gdm/ merge_requests/ 37> /bugs.launchpad .net/bugs/ 1795637 ature: Ubuntu 4.18.0-8.9-generic 4.18.7 .etc.gdm3. custom. conf: 2018-10- 02T13:15: 45.550495 /bugs.launchpad .net/ubuntu/ +source/ gdm3/+bug/ 1795637/ +subscriptions
> Hi Christopher. Yes, we think this bug is fixed, but the "only
> getting> a flashing cursor" problem is a different bug. We're still working on> it right now. Most of the work is happening on the upstream bug
> https:/
> associated cnages
> https:/
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1796614).
> https:/
>
> Title:
> No login screen when booting Cosmic due to plymouth racing with the> rest of the boot process and not releasing DRM devices in time
>
> Status in gdm3 package in Ubuntu:
> Invalid
> Status in plymouth package in Ubuntu:
> Fix Released
> Status in gdm3 source package in Cosmic:
> Invalid
> Status in plymouth source package in Cosmic:
> Fix Released
>
> Bug description:
> Booting a fresh install of Cosmic from the ISO generated 1 Oct 2018> doesnt present a log in screen. Switching to tty2 and then
> back to 1> makes the log in screen appear.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.10
> Package: gdm3 3.30.1-1ubuntu1
> ProcVersionSign
> Uname: Linux 4.18.0-8-generic x86_64
> ApportVersion: 2.20.10-0ubuntu11
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Oct 2 13:23:42 2018
> InstallationDate: Installed on 2018-10-02 (0 days ago)
> InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64
> (20181001)> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile.
>
> To manage notifications about this bug go to:
> https:/