No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on)

[d a i s y]

On a machine with only one display (VGA), the kernel is reporting two:

grep . /sys/class/drm/*/enabled

   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled

ls /sys/class/drm

   card0 card0-LVDS-1 card0-VGA-1 renderD128 version

grep . /sys/class/drm/*/dpms

   /sys/class/drm/card0-LVDS-1/dpms:On
   /sys/class/drm/card0-VGA-1/dpms:On

which then triggers bug 1760849 and the login screen is never visible.

---

$ dpkg -s mutter
Package: mutter
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 101
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Version: 3.28.3-2~ubuntu18.04.2
Provides: x-window-manager
Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity
Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
Description: lightweight GTK+ window manager
 Mutter is a small window manager, using GTK+ and Clutter to do
 everything.
 .
 Mutter is the clutter-based evolution of Metacity, which, as the
 author says, is a "Boring window manager for the adult in you. Many
 window managers are like Marshmallow Froot Loops; Metacity is like
 Cheerios."
 .
 This package contains the core binaries.
Original-Maintainer: Debian GNOME Maintainers <email address hidden>

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.3-2~ubuntu18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 18 15:02:22 2019
InstallationDate: Installed on 2019-01-18 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

[d a i s y (daisyd)]

I've changed #WaylandEnable=false to WaylandEnable=false and reboot the system,
after splash there is nothing so I entered into VT with Ctrl+Alt+F2,
it shows a message, 'a start job is running for hold until boot process finishes up.'

I reviewed this bug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476 and installed haveged but does not solve the issue

[d a i s y (daisyd)]

I am running Ubuntu on SSD. I've done fresh installation of Ubuntu downloaded from here: http://cdimage.ubuntu.com/bionic/daily-live/current/ but no change
and tried all the previous solution of commenting out WaylandEnable=false and installing haveged.

SSD information:
/dev/sda:

ATA device, with non-removable media
 Model Number: SMARTSTATION
 Serial Number: 0208201520019
 Firmware Revision: 1.094.12
 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0

[d a i s y (daisyd)]

At last, I did switching of display manager from gdm to lightdm but after login, nothing appeared on screen, only Ubuntu 18.04 wallpaper.

[Daniel van Vugt (vanvugt)]

daisyd,

Please:

1. Run: dmesg > dmesg.txt

2. Run: journalctl > journalctl.txt

3. Run: lspci -k > lspcik.txt

4. Run: dpkg -l > dpkgl.txt

5. Send us all the above text files.

[Daniel van Vugt (vanvugt)]

Thanks.

Unfortunately I can only see problems caused by your changes so it's hard or even impossible to see the original problem.

Please undo these changes (or just reinstall Ubuntu and don't redo them):

 * lightdm is installed. Please uninstall it.

 * The kernel is starting without modesetting support. Please remove 'nomodeset' from your kernel command line.

 * Xorg is using the Intel driver when it should be using modesetting instead. Please remove your xorg.conf config files. The modesetting driver should work after you have removed 'nomodeset' from your kernel command line.

 * GDM isn't trying to use Wayland. Please comment out WaylandEnable=false from /etc/gdm3/custom.conf. This should work after you have removed 'nomodeset' from your kernel command line and have mutter >= 3.28.3-2~ubuntu18.04.2

If you choose to reinstall then you will need to temporarily use the workaround from bug 1727356 again (WaylandEnable=false). But you should only need that prior to installing the fix: mutter >= 3.28.3-2~ubuntu18.04.2 Then you can comment it out again (#WaylandEnable=false).

So once you have undone ALL of those changes or reinstalled Ubuntu and updated, please:

1. Reproduce the problem of the login screen not appearing.

2. Reboot and start in recovery mode.

3. Run: journalctl -b-1 > prev_boot.txt
   and send us the resulting file 'prev_boot.txt'.

[Daniel van Vugt (vanvugt)]

Actually there's a simpler solution. Please try this:

Download the latest "daily" version of 18.04 and install that from scratch (wiping the previous install):
http://cdimages.ubuntu.com/bionic/daily-live/current/bionic-desktop-amd64.iso

You should then be completely free of bug 1727356 without needing to even update. But if the problem does still happen after that then please:

1. Reproduce the problem of the login screen not appearing (without using recovery mode).

2. Reboot and start in recovery mode.

3. Run: journalctl -b-1 > prev_boot.txt
   and send us the resulting file 'prev_boot.txt'.

[d a i s y (daisyd)]

Daniel van Vugt,

Before reporting this bug,

I'd already done fresh installation of bionic-desktop-amd64.iso : https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1812359/comments/3 as stated here.

All other steps lightdm, nomodeset, xorg.conf file I've done to solve the issue,
so now, undo all changes,
uninstall lightdm, remove nomodeset and xorg.conf file, changed #WaylandEnable=false to WaylandEnable=false

Login screen did not appear so reboot and start in recovery mode.
Output of journalctl -b-1 > prev_boot.txt

[d a i s y (daisyd)]

journalctl -b | grep Mutter
Jan 24 16:31:22 test gsd-xsettings[1034]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist

[Daniel van Vugt (vanvugt)]

Thanks. I can still see three potential problems in the log from comment #12:

1. The boot was attempted with Wayland disabled. Please ensure it is enabled by adding a hash: #WaylandEnable=false

2. The modesetting Xorg driver is being overridden by the intel driver, which shouldn't be used at all any more. Sounds like a priority problem:

Jan 24 16:26:04 test /usr/lib/gdm3/gdm-x-session[671]: (==) Matched intel as autoconfigured driver 0
Jan 24 16:26:04 test /usr/lib/gdm3/gdm-x-session[671]: (==) Matched intel as autoconfigured driver 1
Jan 24 16:26:04 test /usr/lib/gdm3/gdm-x-session[671]: (==) Matched modesetting as autoconfigured driver 2
Jan 24 16:26:04 test /usr/lib/gdm3/gdm-x-session[671]: (==) Matched fbdev as autoconfigured driver 3
Jan 24 16:26:04 test /usr/lib/gdm3/gdm-x-session[671]: (==) Matched vesa as autoconfigured driver 4

3. The intel Xorg driver has a version that sounds like it came from a PPA and did not come from Ubuntu:

ii xserver-xorg-video-intel 2:2.99.917+git1901211932.33ee0c~oibaf~b amd64 X.Org X server -- Intel i8xx, i9xx display driver

The correct and only version for bionic is 2:2.99.917+git20171229-1

To resolve #2 and #3, please ensure no PPAs are in use. Install 'ppa-purge' and use it to remove all PPAs. Then ensure you have the correct version:

xserver-xorg-video-intel = 2:2.99.917+git20171229-1

[d a i s y (daisyd)]

I did following:

1. Enable Wayland with #WaylandEnable=false

2. Remove ppa, purge xserver-xorg-video-intel, update apt list, and again install xserver-xorg-video-intel.

Now,

Package: xserver-xorg-video-intel
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 3183
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Version: 2:2.99.917+git20171229-1
Provides: xorg-driver-video
Depends: libc6 (>= 2.17), libdrm-intel1 (>= 2.4.38), libdrm2 (>= 2.4.25), libpciaccess0 (>= 0.8.0+git20071002), libpixman-1-0 (>= 0.30.0), libudev1 (>= 183), libx11-6, libx11-xcb1, libxcb-dri2-0, libxcb-dri3-0, libxcb-sync1, libxcb-util1 (>= 0.4.0), libxcb1, libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxinerama1, libxrandr2 (>= 2:1.2.99.2), libxrender1, libxshmfence1, libxss1, libxtst6, libxv1, libxvmc1, xorg-video-abi-23, xserver-xorg-core (>= 2:1.18.99.901)
Description: X.Org X server -- Intel i8xx, i9xx display driver
 This package provides the driver for the Intel i8xx and i9xx family
 of chipsets, including i810, i815, i830, i845, i855, i865, i915, i945
 and i965 series chips.
 .
 This package also provides XvMC (XVideo Motion Compensation) drivers
 for i810/i815 and i9xx and newer chipsets.
 .
 This package is built from the X.org xf86-video-intel driver module.
 .
 The use of this driver is discouraged if your hw is new enough (ca.
 2007 and newer). You can try uninstalling this driver and let the
 server use it's builtin modesetting driver instead.
Original-Maintainer: Debian X Strike Force <email address hidden>
Homepage: https://www.x.org/

3. Reboot system and no login screen

4. Reboot into recovery mode and did journalctl -b-1 > new_boot.txt

If you suggest me to do fresh installation again, I will.

[Daniel van Vugt (vanvugt)]

Thanks. That new log is nice and small. The errors of possible interest in order are:

Jan 25 09:26:05 test org.gnome.Shell.desktop[736]: glamor: EGL version 1.4 (DRI2):
Jan 25 09:26:05 test org.gnome.Shell.desktop[736]: Require OpenGL version 2.1 or later.
Jan 25 09:26:05 test org.gnome.Shell.desktop[736]: Failed to initialize glamor
Jan 25 09:26:05 test org.gnome.Shell.desktop[736]: Failed to initialize glamor, falling back to sw
...
Jan 25 09:26:18 test gnome-shell[736]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1468]: reference to undefined property "MetaWindowXwayland"

The first one ending in "falling back to sw" is sad news that things are not going to run very fast, but still they should run without crashing. Although I do wonder if Xwayland can run under those conditions...

The second one "reference to undefined property "MetaWindowXwayland"" I can't find many references to, but the most recent reference is bug 1790525, which is about old Intel GPUs and is not yet fixed in 18.04. In fact the fix for that only reached 19.04 a couple of hours ago so to test with that fix we will need to wait for some _future_ daily build of 19.04.

Next:

 * I have some old netbooks lined up to test when I have some free time over the coming days. Hopefully I will find the time and hopefully I will be able to reproduce the problem.

 * We should wait till some daily build of 19.04 (soon) contains the fix for bug 1790525 (mutter >= 3.30.2-5), and then try that.

 * Right now please try this: Enable debugging (at the bottom of /etc/gdm3/custom.conf) and then repeat the log collection steps.

[Daniel van Vugt (vanvugt)]

Also, it sounds like there's a chance this problem is caused by something crashing. Please follow these instructions to investigate that:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[d a i s y (daisyd)]

There are two files in /var/crash, I did, ubuntu-bug MYFILE.crash, after it run, it did not show anything. There are four files:

_usr_bin_gnome-shell.121.crash _usr_bin_Xwayland.121.crash
_usr_bin_gnome-shell.121.upload _usr_bin_Xwayland.121.upload
_usr_bin_gnome-shell.121.uploaded _usr_bin_Xwayland.121.uploaded

Where is newly-created bug? How do I get the id?

[Daniel van Vugt (vanvugt)]

> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

[https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment]

[d a i s y (daisyd)]

No, I could not see anything reported today: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

[d a i s y (daisyd)]

I've moved all files from /var/crash and reboot system, regenerate crash files.

Again trying to do ubuntu-bug _usr_bin_gnome-shell.121.crash but the same result, no further steps to report.

[d a i s y (daisyd)]

While reporting ubuntu-bug _usr_bin_Xwayland.121.crash, when I've clicked on show details,
It shows duplicate of bug https://bugs.launchpad.net/bug/1731911

[d a i s y (daisyd)]

I did further more steps,

1. Remove gdm3 and gnome-shell, while removing gnome-shell it was showing something 'polkit-1-auth-agent is not installed so not to remove'

2. Install gnome-shell, gdm3, policykit-1-gnome, also ubuntu-gnome-desktop and ubuntu-gnome-default-settings

3. Enable debugging gdm3 (/etc/gdm3/custom.conf file), Moved all files from /var/crash, and reboot the system. No login screen but no files in /var/crash

4. Reboot into recovery mode and run journalctl -b-1 > boot1.txt

[Alberto Salvia Novella (es20490446e)]

@ daisy

You subscribed me to this bug report, but I'm no longer involved in Ubuntu's development.

So I'm unsubscribing.

[d a i s y (daisyd)]

vanvugt,

I downloaded the latest "daily" version of 18.04 from here: http://cdimages.ubuntu.com/bionic/daily-live/current/bionic-desktop-amd64.iso, check m5dsum, it's same.

Before installation, I try without installing option, and after ubuntu logo, only blank default bionic wallpaper appear and nothing.

Previously Ubuntu installed because I've set nomodeset.

[Daniel van Vugt (vanvugt)]

Thanks for your efforts. Over the weekend I also set up Ubuntu 18.04 on some Pineview Atom netbooks, but only found bug 1727356.

Please generate a new log as the one in comment #27 is showing it's from recovery mode, and so is not showing the bug. You seem to have booted recovery mode twice in a row.

[d a i s y (daisyd)]

vanvugt,

Okay, I did normal boot, no login screen, could not entered into VT, so with telnet, I did journalctl -b-1 > boot2.txt

I still request only if you haven't consider comment #29 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1812359/comments/29, Please do. As I said, I've set nomodeset to install Ubuntu, without it I could not.

[Daniel van Vugt (vanvugt)]

Thanks but you seem to have made the same mistake again. That log is from recovery mode so is not useful:

Jan 29 09:40:28 test kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=1b38a9ba-d9c9-4b85-a152-b5f2cbc9aa98 ro recovery nomodeset

Using 'nomodeset' is a workaround, and one that will prevent normal graphics modes from working. So use it when you must, but if you do need it then that indicates a bug somewhere (this bug).

Now that you have debugging enabled, please repeat the steps in comment #11 and be careful to not send any logs that mention "recovery nomodeset" at the top.

[Daniel van Vugt (vanvugt)]

Also, please allow the system at least 15 minutes to boot before giving up. There might be something slowing it down dramatically making it look like it's hung when it's not. If that's true then we need to see it all in the log.

[Daniel van Vugt (vanvugt)]

Thanks.

There are two points of interest in that log I can see:

Jan 29 09:45:01 test /usr/lib/gdm3/gdm-x-session[656]: (II) intel(0): resizing framebuffer to 2732x768
Jan 29 09:45:01 test /usr/lib/gdm3/gdm-x-session[656]: (II) intel(0): switch to mode 1366x768@60.4 on LVDS1 using pipe 1, position (0, 0), rotation normal, reflection none
Jan 29 09:45:02 test /usr/lib/gdm3/gdm-x-session[656]: (II) intel(0): switch to mode 1366x768@59.8 on VGA1 using pipe 0, position (1366, 0), rotation normal, reflection none

and

Jan 29 09:45:51 test gnome-shell[931]: Skipping layers 1..n of your pipeline since the first layer is sliced. We don't currently support any multi-texturing with sliced textures but assume layer 0 is the most important to keep

Both of these suggest the problem is that gnome-shell is trying and failing to render across two screens (2732x768) because the code that's meant to handle that for older GPUs like this is not well tested (no developers use that kind of hardware).

As a workaround
~~~~~~~~~~~~~~~
Please just unplug your second monitor and leave it unplugged. The system should work fine with just a single monitor. In fact, please reinstall again without ever plugging in that second monitor and everything should just work.

As a permanent fix
~~~~~~~~~~~~~~~~~~
I think this is probably one of the bugs that Gert van der Kraats has been working on recently: bug 1790525 or bug 1795774. The fix for those has only been in 19.04 for a couple of days so please try live booting 19.04 (http://cdimages.ubuntu.com/daily-live/current/) and tell us if that seems to fix the problem.

[d a i s y (daisyd)]

@ Daniel van Vugt

Thanks, You're right. I'd just unplug the VGA, start the system and when plug in, I could see the screen. Well, I'm using smart station so I've to connect the external monitor(Dell) with VGA. It has HDMI port too, so connect the monitor (LG) with HDMI and it is working except the screen is not fitting.

Should I reinstall 18.04.1 with HDMI connected monitor and then connect to VGA. Would it make any difference?

I will give an update for 19.04 once it is downloaded.

[Daniel van Vugt (vanvugt)]

To avoid bug 1727356 you still need to avoid installing 18.04.1. Please only install

  Pre-release 18.04.2:
  http://cdimages.ubuntu.com/bionic/daily-live/current/
  (should work with no monitors connected)

or

  Pre-release 19.04:
  http://cdimages.ubuntu.com/daily-live/current/
  (might work with multiple monitors)

[d a i s y (daisyd)]

How can I install 18.04.2: http://cdimages.ubuntu.com/bionic/daily-live/current/ with no monitors connected. Would it be okay with laptop?

and 19.04: http://cdimages.ubuntu.com/daily-live/current/ downloading failed two times.

[d a i s y (daisyd)]

Okay, I did fresh installation of 18.04.2 downloaded from here: http://cdimages.ubuntu.com/bionic/daily-live/current/ in my laptop.
After than I installed SSD into smart station. Issue is same when VGA is connected.

You can check log if you want to find something.

Update for 19.04 will be given once it is downloaded.

[d a i s y (daisyd)]

Install 19.04 downloaded from here http://cdimages.ubuntu.com/daily-live/current/ and it has same issue like 18.04.2 whenever the external monitor connected to VGA, no login screen and blank default wallpaper.

[Daniel van Vugt (vanvugt)]

Thanks.

If 19.04 isn't working then that's the interesting one because that should have fixes for all the aforementioned bugs already...

On 19.04, can you please:

1. Collect a 'journalctl' log (like before) from 19.04 when the external monitor is connected and the problem appears?

2. Run: dpkg -l > dpkgl.txt
   and send us the file 'dpkgl.txt'.

[Daniel van Vugt (vanvugt)]

Also remember to keep the laptop open :) Because the login screen might only ever appear there.

Have you been keeping the laptop screen open?

[Daniel van Vugt (vanvugt)]

Finally, please take a photo of "no login screen and blank default wallpaper" so we can understand exactly what you are describing.

[d a i s y (daisyd)]

Okay,
First thing, Laptop is Dell and cpu architecture is Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz, I have used laptop just to install 18.04.2 and 'Try Ubuntu' for 19.04

after then remove ssd from laptop and install it in smart station in which this issue is occurred - CPU architecture for smart station Intel(R) Atom(TM) CPU D425 @ 1.80GHz

I've performed following steps:
1. Boot the system(smart station) when VGA connected (LG monitor which has both HDMI and VGA),
2. Remove VGA and connect the HDMI
3. Login when HDMI connected and then remove HDMI and again connect VGA

[Daniel van Vugt (vanvugt)]

Please also remember comments #43 and #44.

[d a i s y (daisyd)]

For 19.04, I am working on it because I found some strange issue with HDMI too after installing it.

Boot system connected with HDMI connected, first it shows only blank purple magenta and after a minute, only blank black screen. Power off the smart station, disconnected both HDMI, VGA, and boot the system and after completion of booting, connect the HDMI, it shows login screen. I will give you a log.

[Daniel van Vugt (vanvugt)]

Also remember to keep the laptop open :) Because the login screen might only ever appear on the laptop screen.

Have you been keeping the laptop screen open?

[d a i s y (daisyd)]

I've not connected laptop and lcd monitor together with either HDMI or VGA?

[d a i s y (daisyd)]

1. I did not get what are you saying for laptop, both 18.04.2 and 19.04 working well in laptop with SSD installed

2. For SSD installed in smart station- 19.04 (VGA connected), No login screen and stuck at Ubuntu logo.

[Daniel van Vugt (vanvugt)]

Comment #57 is an image. Please remember to attach a log instead :)

Also, I have been thinking that the Intel Atom D425 was a laptop. Not just because that's more common, but also because the log in comment #35 mentions it is trying to render to a laptop screen (LVDS) and a VGA monitor at the same time:

Jan 29 09:45:01 test /usr/lib/gdm3/gdm-x-session[656]: (II) intel(0): switch to mode 1366x768@60.4 on LVDS1 using pipe 1, position (0, 0), rotation normal, reflection none
Jan 29 09:45:02 test /usr/lib/gdm3/gdm-x-session[656]: (II) intel(0): switch to mode 1366x768@59.8 on VGA1 using pipe 0, position (1366, 0), rotation normal, reflection none

If the Atom D425 machine is not a laptop then I think this explains a lot...

If your Atom D425 machine only ever has one screen and that screen is the VGA monitor then the above log shows the main issue here -- Ubuntu thinks you have two screens when you only have one. And if it thinks you have two screens then it's likely trying to put the login screen on that LVDS display which doesn't exist --> bug 1760849.

But it's not just the above bugs you are experiencing. If your Atom D425 machine doesn't have a built-in laptop monitor (LVDS) then there is clearly a bug in the Intel Xorg driver for trying to drive that screen. It seems there is no EDID but (unsurprisingly) can't tell that there's really no screen there at all.

Jan 29 09:45:30 test gsd-color[1080]: unable to get EDID for xrandr-LVDS1: unable to get EDID for
output

IF it is true that the Atom D425 machine is not a laptop, and it does not have a built-in screen, then I think the next step is to find out if it is the kernel misdetecting the non-existent LVDS screen, or the Xorg driver.

Next, please run this command and send us the output:

  grep . /sys/class/drm/*/enabled

Also, the log in comment #41 seems to show the system isn't starting in that case because of a crash:

Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: (EE)
Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: Fatal server error:
Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: (EE) wl_drm@4: error 0: authenicate failed
Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: (EE)
Jan 29 16:29:18 test gnome-shell[672]: X Wayland crashed; exiting
Jan 29 16:29:18 test gnome-session[628]: gnome-session-binary[628]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 29 16:29:18 test gnome-session-binary[628]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 29 16:29:18 test gnome-session-binary[628]: Unrecoverable failure in required component org.gnome.Shell.desktop

That would be the same crash mentioned in comments #23 and #24. So we will need to debug that too. Please look in /var/crash for crash files and if found send them by running:

  ubuntu-bug YOURFILE.crash

Unfortunately I can't access bug 1731911 that you mentioned in comment #24. Was that a typo?

[Daniel van Vugt (vanvugt)]

Oh, now I can access bug 1731911 and it's a red herring so forget that one...

Please run:

  grep . /sys/class/drm/*/enabled

and send us the output.

Please also don't mention your laptop any more as that is not what this bug is about. This bug is about the Atom D425 machine only.

[d a i s y (daisyd)]

Note1: Atom D425 machine only has one screen and that screen is the VGA monitor.
----

For comment #23 and #24, after then I reinstalled Ubuntu as mentioned here: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1812359/comments/40

Now there is Ubuntu 19.04 installed,
I've done
   grep . /sys/class/drm/*/enabled

and attaching two files:

1. journalctl -b-1 > 19.04_boot1.txt
2. dpkg -l > dpkgl.txt

----

FYI, I've installed Ubuntu 18.04.2 and 19.04 in two different disk(so I don't need to do re-installation every time, only one disk installed in Atom D425 machine at a time ), so I can give any time you need any of log.

[Daniel van Vugt (vanvugt)]

Please run:

  grep . /sys/class/drm/*/enabled

and send us the output. :)

[Daniel van Vugt (vanvugt)]

In the log of comment #62 I can only see the Xwayland crash that is bug 1731911. That probably means gnome-shell started crashing or shutting down earlier so we will need you to search for evidence of the 'gnome-shell' process crashing by following these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[d a i s y (daisyd)]

I did,

Please check: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1813897

[Daniel van Vugt (vanvugt)]

Please run:

  grep . /sys/class/drm/*/enabled

and send us the output. :)

[Daniel van Vugt (vanvugt)]

Please also run:

  ls /sys/class/drm

and send us the output.

[Daniel van Vugt (vanvugt)]

Please also run:

  grep . /sys/class/drm/*/dpms

and send us the output.

[d a i s y (daisyd)]

grep . /sys/class/drm/*/enabled

   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled

ls /sys/class/drm

   card0 card0-LVDS-1 card0-VGA-1 renderD128 version

grep . /sys/class/drm/*/dpms

   /sys/class/drm/card0-LVDS-1/dpms:On
   /sys/class/drm/card0-VGA-1/dpms:On

[Daniel van Vugt (vanvugt)]

Great! I think I understand the problem now.

The problem is that the Linux kernel is telling us there are two displays:

  LVDS - a laptop display that does not exist
  VGA - your real monitor

And then due to bug 1760849, gdm3 is putting the login screen on that laptop display which doesn't really exist.

A fix for bug 1760849 would suffice. But let's keep this bug open and make this bug just about the kernel bug of reporting an LVDS output which doesn't exist.

[Daniel van Vugt (vanvugt)]

Next, please try some newer kernels (you only have kernel 4.18 with Ubuntu 19.04) from here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

and then use the simple test of:

  grep . /sys/class/drm/*/enabled

to tell us if a newer kernel has changed things.

[d a i s y (daisyd)]

If I consider 4.19, then which of these files I need to install,

  linux-headers-4.19.0-041900_4.19.0-041900.201810221809_all.deb
  linux-headers-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-headers-4.19.0-041900-lowlatency_4.19.0-041900.201810221809_amd64.deb
  linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-image-unsigned-4.19.0-041900-lowlatency_4.19.0-041900.201810221809_amd64.deb
  linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-modules-4.19.0-041900-lowlatency_4.19.0-041900.201810221809_amd64.deb

For currently installed 19.04,
  uname -r
  4.18.0-11-generic

[Daniel van Vugt (vanvugt)]

Generally for each version you try you need to install all the packages _except_ the "lowlatency" ones.

So:

  linux-headers-4.19.0-041900_4.19.0-041900.201810221809_all.deb
  linux-headers-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

[d a i s y (daisyd)]

grep . /sys/class/drm/*/enabled

  /sys/class/drm/card0-LVDS-1/enabled:enabled
  /sys/class/drm/card0-VGA-1/enabled:enabled

[Daniel van Vugt (vanvugt)]

Thanks. Please test v5.0 too, and then that's enough.

[Daniel van Vugt (vanvugt)]

Oops. Please also run this:

grep . /sys/class/drm/*/status

[d a i s y (daisyd)]

$ uname -r
   4.20.0-042000-generic
grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected

[d a i s y (daisyd)]

$ uname -r
   5.0.0-050000rc4-generic
grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected

[Daniel van Vugt (vanvugt)]

Thanks. That's definitely a kernel bug (or a hardware fault, but let's hope a kernel bug).

I can now finally hand this over to the kernel people. Although it might also be helpful if you report the bug upstream here:

  https://bugzilla.kernel.org/enter_bug.cgi

with a new title like:

  "i915 reports a nonexistent LVDS output (as connected and on)"

and the details:

grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected
grep . /sys/class/drm/*/dpms
   /sys/class/drm/card0-LVDS-1/dpms:On
   /sys/class/drm/card0-VGA-1/dpms:On

then tell us the new bug ID.

[d a i s y (daisyd)]

Okay thanks,

Here I found something new in Ubuntu 18.04.2,
I thought about to install kernel 4.15.0-43, login screen appeared but resolution issue and not network adapter, neither ethernet nor wireless, so just leave it

Then for kernel 4.15.0-45-generic, I've disabled wayland
During booting, ubuntu logo appeared (seems like when we set nomodeset), then splash divided into two(ubuntu logo left and right side) and after a minute login screen appeared,

but after login, just a wallpaper and nothing like it's freezing, same issue.

Please check a log if you can find something new.

[Daniel van Vugt (vanvugt)]

We don't need any more logs as this bug is fully understood.

Although it sounds like you might now be experiencing bug 1795760. Also there are other related bugs to that like bug 1790525 or bug 1795774. Plus there is the original bug 1727356. Those last three are all fixed in 19.04 so please don't use 18.04 any more - it doesn't have enough fixes for your hardware.

The other bug you are experiencing is bug 1760849. So the unresolved bugs you are experiencing in 19.04 are bug 1812359, bug 1760849 and maybe 1795760.

But to avoid confusion we should really only talk about bug 1812359 here. And you should only use Ubuntu 19.04 because 18.04 contains a little too many of those bugs.

If you would like to speed up the resolution of this problem (bug 1812359) then please follow the steps in comment #81.

[daisy.rose021 (daisy.rose021-linux-kernel-bugs)]

I've installed Ubuntu 19.04 on a NETBOX nT-435/535 and no login screen displayed whenever the VGA is connected to LG monitor.

[daisy.rose021 (daisy.rose021-linux-kernel-bugs)]

Created attachment 280927
LVDS & VGA status

[d a i s y (daisyd)]

I've reported a bug,

  https://bugzilla.kernel.org/show_bug.cgi?id=202487

[kai.heng.feng (kai.heng.feng-linux-kernel-bugs)]

Please file i915 bugs to https://bugs.freedesktop.org

[daniel.van.vugt (daniel.van.vugt-linux-kernel-bugs)]

Are you sure about that? This is a kernel bug, not a Mesa bug.

What Freedesktop project would it be assigned to?

[kai.heng.feng (kai.heng.feng-linux-kernel-bugs)]

Yes I am sure.

Product: DRI
Component: DRM/Intel

[daniel.van.vugt (daniel.van.vugt-linux-kernel-bugs)]

daisy,

Please report the bug on: https://bugs.freedesktop.org
with
Product: DRI
Component: DRM/Intel

[jani.nikula (jani.nikula-linux-kernel-bugs)]

For several years now the one and only place to file drm/i915 bug has been
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel