Hey Daniel, The other thing I noticed in the the boot logs are a seemingly futile loop:
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/usr/share/gdm/greeter/autostart' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/var/lib/gdm3/.config/autostart' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/usr/share/gdm/greeter/gnome/autostart' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/usr/local/share/gnome/autostart' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/usr/share/gnome/autostart' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/etc/xdg/autostart' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/var/lib/gdm3/.local/share/applications' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/usr/share/gdm/greeter/applications' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/usr/local/share/applications' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in '/usr/share/applications' Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]: gnome-session-binary[1430]: DEBUG(+): GsmUtil: found in XDG dirs: '/etc/xdg/autostart/org.gnome.SettingsDaemon.Housekeeping.desktop' This appears first at 11:38:36 in the first boot log, and then repeats over and over and over until the machine turns off. The same loop appears in longhangprevboot2.txt and starts at 12:21:55. What is the machine trying to do here? I suspect that this is what's happening in the background when the computer hangs, and it may even describe why it does not record the whole boot sequence for the 20 minutes after it hangs. Thoughts? I have not used Ubuntu 16.04, nor Lubuntu 18.04.1. I'll download Lubuntu and see how that works out. But, I am a little concerned about getting it to install correctly. Whenever I try to get the computer to recognize the CD image and to boot from it, I have to spam "1" and "Enter" over and over and sometimes it works. Have you run into this issue before? Alex On Tue, Jan 22, 2019 at 8:05 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > You're right - those logs are apparently from short boots. > > longhangprevboot.txt lasted less than 2 minutes and only 2 seconds > between GLSL errors and the machine beginning to shutdown. > > longhangprevboot2.txt lasted 2 minutes and again was only 4 seconds > between GLSL errors and the machine beginning shutting down. > > Maybe that's a hint at a bigger problem if the system clock is running > slower than reality..? > > Do older releases like Ubuntu 16.04 work on it? How about Lubuntu > 18.04.1? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1811599 > > Title: > When booting, the computer hangs at a purple screen and no login > prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950] > > Status in gdm3 package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > After a fresh install of Ubuntu 18.04.1, on its first boot, the > computer hung at a purple screen. No login prompt was ever displayed. > After holding the power button, the computer boot into Ubuntu without > difficulty. I applied the workaround described in bug 1727356, > uncommenting WaylandEnable=False and rebooted the machine, but it > again hung at the purple screen. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gdm3 3.28.3-0ubuntu18.04.3 > 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: Sun Jan 13 10:59:26 2019 > InstallationDate: Installed on 2019-01-11 (2 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > ProcEnviron: > TERM=xterm-256color > PATH=(custom, no user) > XDG_RUNTIME_DIR=<set> > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions > -- Alexander A Theiler, MHS, MS, PA-C CAQ in Emergency Medicine -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1811599 Title: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950] Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu 18.04.1, on its first boot, the computer hung at a purple screen. No login prompt was ever displayed. After holding the power button, the computer boot into Ubuntu without difficulty. I applied the workaround described in bug 1727356, uncommenting WaylandEnable=False and rebooted the machine, but it again hung at the purple screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 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: Sun Jan 13 10:59:26 2019 InstallationDate: Installed on 2019-01-11 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
