When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

[Alexander A Theiler]

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

[Daniel van Vugt (vanvugt)]

Please:

1. Boot into recovery mode and enable (uncomment) debugging in /etc/gdm3/custom.conf
2. Reboot into normal mode and reproduce the hang.
3. Reboot again into recovery mode and run:

   journalctl -b-1 > prev_boot.txt

   and then send us the file 'prev_boot.txt'.

[Alexander A Theiler (serkhan)]

I received an error from Launchpad stating that the previous file I sent
was too large (14 MB) and could not be delivered, and so I repeated the
above steps again. Here's another failed boot log, and for some reason,
it's much, much smaller (836 KB).

Alex

On Tue, Jan 15, 2019 at 10:35 AM Alex Thëil <email address hidden> wrote:

> Here you are. Please see attached.
>
> Alex
>
> On Mon, Jan 14, 2019 at 7:05 PM Daniel van Vugt <
> <email address hidden>> wrote:
>
>> Please:
>>
>> 1. Boot into recovery mode and enable (uncomment) debugging in
>> /etc/gdm3/custom.conf
>> 2. Reboot into normal mode and reproduce the hang.
>> 3. Reboot again into recovery mode and run:
>>
>> journalctl -b-1 > prev_boot.txt
>>
>> and then send us the file 'prev_boot.txt'.
>>
>> ** Changed in: gdm3 (Ubuntu)
>> Status: New => Incomplete
>>
>> --
>> 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
>>
>> Status in gdm3 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
>

--
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine

[Daniel van Vugt (vanvugt)]

Alex,

The log in comment #3 is from recovery mode, not what we need.

Please follow the steps in comment #2 again, but before sending 'prev_boot.txt' try compressing it to make it smaller:

  xz prev_boot.txt

and then send us 'prev_boot.txt.xz'

[Alexander A Theiler (serkhan)]

Here it is.

Alex

On Tue, Jan 15, 2019 at 7:20 PM Daniel van Vugt <
<email address hidden>> wrote:

> Alex,
>
> The log in comment #3 is from recovery mode, not what we need.
>
> Please follow the steps in comment #2 again, but before sending
> 'prev_boot.txt' try compressing it to make it smaller:
>
> xz prev_boot.txt
>
> and then send us 'prev_boot.txt.xz'
>
> --
> 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
>
> Status in gdm3 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

[Daniel van Vugt (vanvugt)]

That boot seems to be starting from 11 Jan. Does it also include debug enabled per comment #2?

Regardless, it's a little too old and unnecessarily large. Please follow the steps in comment #2 more carefully and do it again.

[Alexander A Theiler (serkhan)]

My apologies, I've been out of town for a few days. Here is the updated
version, which was just created, with debugging enabled.

Please see attached.

Alex

On Tue, Jan 15, 2019 at 11:45 PM Daniel van Vugt <
<email address hidden>> wrote:

> That boot seems to be starting from 11 Jan. Does it also include debug
> enabled per comment #2?
>
> Regardless, it's a little too old and unnecessarily large. Please follow
> the steps in comment #2 more carefully and do it again.
>
> --
> 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
>
> Status in gdm3 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

[Daniel van Vugt (vanvugt)]

Please try again. The log in comment #7 is from recovery mode :(

I think you forgot step 2 in comment #2.

[Alexander A Theiler (serkhan)]

Hey Daniel,

I'm honestly not sure what I'm doing wrong. Here's precisely what I'm
doing. Tell me where I'm messing up:

First, I booted into recovery mode by hitting Esc on bootup, and selecting
boot into recovery mode. The computer then boots, and reaches a point at
which it I have multiple options, the first one being continue into a
regular boot, and a then there are a few others, like "drop into root."

In the previous email, with the previous file, after booting into recovery
mode, I then selected "continue regular boot" and then I edited the
/etc/gdm3/custom.conf to enable debugging. I then rebooted and reproduced
the hang. I then rebooted into recovery mode, and then continued booting
into normal mode. I then sent the files, were were apparently wrong.

Here are two more files. Since /etc/gdm3/custom.conf already had debugging
enabled, I did not reboot the computer into recovery mode. I simply
rebooted the machine, let it boot as normal and hang while loading as it
usually does. I then rebooted the machine, tapped Esc, and selected "boot
into recovery mode." It paused after booting for a few seconds, and gave me
a few options. This time, I chose "drop into root" and ran the command
"journalctl -b-1 > prev_boot.txt" but I'm not sure where it saved. I then
selected for the computer to boot as normal, out of recovery mode. When I
entered Ubuntu, I ran two commands, "journalctl -b-1 > prev_boot.txt" and
attached it here. I also ran "journalctl -b >prev_boot2.txt." Between the
two boot records, I hope one is correct. Prev_boot.txt is extremely large
again for some reason, and in the logs, it says the boot sequence started
on 1/11/19, which is absurd. What's going on with that? Strangely,
prev_boot2.txt is much smaller but also states that the boot sequence took
over a week.

Sorry for the lengthy email. Where am I messing up on recording the boot?

Sincerely,

Alex

On Sun, Jan 20, 2019 at 7:40 PM Daniel van Vugt <
<email address hidden>> wrote:

> Please try again. The log in comment #7 is from recovery mode :(
>
> I think you forgot step 2 in comment #2.
>
> --
> 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
>
> Status in gdm3 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...

[Daniel van Vugt (vanvugt)]

I suspect the mistake is that you are not manually un-selecting recovery mode, so it is always rebooting in the same mode as last time, so is always in recovery mode.

Either that or the non-recovery mode boots are failing to record a log at all. But I suspect it's more likely you're stuck in recovery mode even after rebooting.

Try selecting a kernel at startup that is not recovery mode. Then reproduce the hang, and then reboot into recovery mode...

[Daniel van Vugt (vanvugt)]

Although you have provided some logs that are not in recovery mode, those logs span multiple days so are not helpful in pinpointing the immediate problem.

When sending logs in future please ensure they don't mention "recovery nomodeset", AND that the earliest and oldest dates in the log file are the same day within a few minutes of each other. That should be guaranteed by following the steps in comment #2 closely.

[Alexander A Theiler (serkhan)]

Hey Daniel,

You were right - the computer was stuck in recovery mode. I manually
booted it into normal mode and then restarted it and re-produced a hang. I
then rebooted into recovery mode and recorded that boot with journalctl
-b-1 > prevboot.txt. Please see attached.

The log states that the boot began on 1/11/19 and continues until 1/21/19.
However, if you look at the log itself, the only data recorded is from
today, 1/21/19. I don't know where it's getting 1/11/19 from. So, despite
the log at the top stating that the boot record spans several days, the
record itself only reflects one day. And the file is appropriately small.
I sincerely hope this is what you're looking for, despite incorrect dates.
Can you take a look?

Thanks a ton,

Alex

On Sun, Jan 20, 2019 at 10:40 PM Daniel van Vugt <
<email address hidden>> wrote:

> Although you have provided some logs that are not in recovery mode,
> those logs span multiple days so are not helpful in pinpointing the
> immediate problem.
>
> When sending logs in future please ensure they don't mention "recovery
> nomodeset", AND that the earliest and oldest dates in the log file are
> the same day within a few minutes of each other. That should be
> guaranteed by following the steps in comment #2 closely.
>
> --
> 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
>
> Status in gdm3 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

[Daniel van Vugt (vanvugt)]

Thanks, that log is good. The only real error I can see is that your GPU doesn't support some feature gnome-shell is trying to use:

Jan 21 10:25:58 HackBook gnome-shell[1919]: Shader compilation failed:
                                            0:44(42): warning: `cogl_texel0' used uninitialized
                                            0:72(36): error: could not implicitly convert operands to arithmetic operator
                                            0:72(18): error: operands to arithmetic operators must be numeric
Jan 21 10:25:58 HackBook gnome-shell[1919]: Failed to link GLSL program:
                                            error: linking with uncompiled/unspecialized shader
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:384: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:399: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:409: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:796: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:823: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:827: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:831: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-buffer-gl.c:198: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Jan 21 10:25:58 HackBook gnome-shell[1919]: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
Jan 21 10:26:02 HackBook /usr/lib/gdm3/gdm-wayland-session[1368]: gnome-session-binary[1372]: DEBUG(+): GsmSystemd: received logind signal: PrepareForShutdown
Jan 21 10:26:02 HackBook gnome-session-binary[1372]: DEBUG(+): GsmSystemd: received logind signal: PrepareForShutdown

But that GLSL trouble might not be the real problem. If you look at the timestamps you can see there is only 4 seconds between the GLSL errors and the machine being told to shut down. So I suspect you're not waiting long enough for the machine to start up and killing it in the middle of the start-up process (which seems very slow, but still seems to be working). Please try waiting 15 minutes next time and send us a fresh log from that.

[Daniel van Vugt (vanvugt)]

Note to developers: This system seems to have an Intel GMA 950 GPU. Limited to OpenGL 1.4? So it is much older than the CPUs that bug 1727356 was about. Still, this system should start up eventually even if using software rendering.

[Daniel van Vugt (vanvugt)]

Alex,

It's unclear how long this bug will take to get resolved, if at all. Even if you find the machine does start up after 15 minutes or so, it might not perform well enough to be usable.

If you would like to use Ubuntu on it then maybe the lighter weight Lubuntu is a better solution right now:

http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso

[Alexander A Theiler (serkhan)]

Hey Daniel,

Yeah, at the beginning of this all, I thought it was taking a long time to
boot as well, but even after letting the system sit at the purple screen
for quite some time, it never went anywhere. I had a though that my
ancient laptop might simply be too old to properly run Ubuntu, but I was
optimistic. What's strange is that after it crashes, it boots entirely
normally, and runs very well without any lag or video issues at all.

I'll chalk this up to being a bug related to my system being quite old.

Do you still want that new boot log after 15 minutes of waiting?

Thanks

Alex

On Mon, Jan 21, 2019 at 8:40 PM Daniel van Vugt <
<email address hidden>> wrote:

> Alex,
>
> It's unclear how long this bug will take to get resolved, if at all.
> Even if you find the machine does start up after 15 minutes or so, it
> might not perform well enough to be usable.
>
> If you would like to use Ubuntu on it then maybe the lighter weight
> Lubuntu is a better solution right now:
>
> http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1
> -desktop-amd64.iso
> <http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso>
>
> --
> 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

[Daniel van Vugt (vanvugt)]

Yes please for a new log.

This bug is almost certainly fixable. We just need a complete log, and then a lot of patience to wait for some upstream developer to get around to figuring it out.

If you can't wait and want to use the machine now then Lubuntu might be a better option:
http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso

[Alexander A Theiler (serkhan)]

Hey Daniel,

I've recorded two long hangs for you and your team to analyze.

Please find attached longhangprevboot.txt and longhangprevboot2.txt.

The only difference between the two is that longhangprevboot.txt followed
the following timeline:
normal mode -> restart to long hang -> restart to recovery mode and record
previous boot

Whereas, longhangprevboot2.txt followed the following:
normal mode -> restart to long hang -> restart to normal mode and record
previous boot

I let both of these boots hang for about 20 minutes before restarting the
machine. Strangely, both logs don't seem to reflect that. Unless they do,
and I simply didn't interpret the data correctly. Ideas?

Thanks

Alex

On Mon, Jan 21, 2019 at 9:00 PM Daniel van Vugt <
<email address hidden>> wrote:

> Yes please for a new log.
>
> This bug is almost certainly fixable. We just need a complete log, and
> then a lot of patience to wait for some upstream developer to get around
> to figuring it out.
>
> If you can't wait and want to use the machine now then Lubuntu might be a
> better option:
>
> http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso
>
> --
> 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

[Daniel van Vugt (vanvugt)]

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?

[Alexander A Theiler (serkhan)]

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 <
<email address hidden>> 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 old...

[Daniel van Vugt (vanvugt)]

Those repeated messages are probably just a consequence of still having debugging turned on. Maybe now is a good time to try with debugging turned off in /etc/gdm3/custom.conf so as to generate smaller logs.

> 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?

No I haven't ever heard of that. Usually on a Macbook you just hold the Option key at startup to select a boot device. Maybe you are seeing a quirk of the old model or maybe you are experiencing a hardware fault.

In fact, if you can't get any Linux to work reliably then hardware faults start to become a more realistic explanation. But I don't see any solid evidence of a hardware fault yet.

[Daniel van Vugt (vanvugt)]

I think this might be related to bug 1790525 or bug 1812359. So keep an eye on those.

[Launchpad Janitor (janitor)]

[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]