Sure thing.
This is now reported at bug 1811599.
Thanks again for all your help. Greatly appreciated.
Alex
On Sun, Jan 13, 2019 at 12:41 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Thanks Alex :)
>
> This now sounds like the kind of problem we should report to the
> upstream
Ok, so I totally reinstalled Ubuntu 18.04.1. On its first fresh boot ever,
it hung at the purple screen, before a login screen should have been
displayed. I was able to use the workaround for bug 1727356 by
uncommenting "WaylandEnable=false" and again rebooted. It still hung at
the purple screen
I understand. Thank you very much for all the help. I did not realize
PPAs were so dangerous and will certainly avoid them in the future.
Thanks again
Alex
On Thu, Jan 10, 2019 at 11:00 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Your new 'allpackages.txt' shows the same pro
Thank you for the help.
In fact, the first bug I found, after a fresh install of Ubuntu 18.04.1,
was actually that the computer was hanging at the purple screen on boot. I
attempted to fix this problem by installing video driver PPAs and setting
"nomodeset" on grub. I mistakenly thought this fix
Thanks. Here it is.
On Wed, Jan 9, 2019 at 9:00 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Just run:
>
> dpkg -l > allpackages.txt
>
> and then send us the file 'allpackages.txt'.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> ht
Thank you for the guidance. I actually installed these PPA's early on, in
an effort to get around hanging at the purple screen on boot.
I was unable to use ppa-purge. Perhaps my syntax was wrong? Instead, I
have removed all the PPAs through Software & Updates. Or was there just
one PPA that nee
1. Please see attached for another documented failed boot, saved as
failedboot2.txt.
2. There were no files named xorg.conf in /etc
3. Custom.conf is attached as well.
Thank you
Alex
On Tue, Jan 8, 2019 at 10:58 PM Alex Thëil
wrote:
> Comment 10 being the reproduce a failed boot, then succes
Comment 10 being the reproduce a failed boot, then successful boot and save
the failed boot log?
On Tue, Jan 8, 2019 at 8:55 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Thanks. I can't yet see any failures in failedboot.txt. What's strange
> is that it claims to be using Xorg and
Great idea. I didn't know you could get the recording from boots that were
done previously.
I reproduced a failed boot, and then a successful boot. Please find
attached "failedboot.txt" and just for fun, I recorded the successful boot
as well. It is attached as "successfulboot.txt"
Also find a
