*** This bug is a duplicate of bug 1811599 ***
https://bugs.launchpad.net/bugs/1811599
** This bug has been marked a duplicate of bug 1811599
When booting, the computer hangs at a purple screen and no login prompt is
ever displayed
--
You received this bug notification because you are a
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
Thanks John.
This now sounds like the kind of problem we should report to the
upstream developers. However to avoid confusing them with the previous
mistakes and discussions can you please log a new bug from the machine
by running this command?
ubuntu-bug gdm3
Then let us know the new bug ID.
Thanks Alex :)
This now sounds like the kind of problem we should report to the
upstream developers. However to avoid confusing them with the previous
mistakes and discussions can you please log a new bug from the machine
by running this command?
ubuntu-bug gdm3
Then let us know the new bug ID
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
Your new 'allpackages.txt' shows the same problem as before. To verify
the problem is fixed you should at least be able to run:
dpkg -l | grep oibaf
and get ZERO results.
I understand the evolution of this bug and your attempts to fix it. What
I am saying is that you have now broken the machin
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
Alternatively, just using the latest ISO build should also avoid the
problem:
http://cdimages.ubuntu.com/bionic/daily-live/current/bionic-desktop-
amd64.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Unfortunately 'allpackages.txt' shows you do still have PPAs from
"oibaf" installed. To check that more easily you should be able to run
something like:
dpkg -l | grep oibaf
If you are unable to remove/downgrade all those using 'ppa-purge' then I
can only recommend that you reinstall Ubuntu fro
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
Just run:
dpkg -l > allpackages.txt
and then send us the file 'allpackages.txt'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810630
Title:
Boot up is hung on a purple screen
To manage notifi
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
Oh! I failed to notice right at the beginning of this bug that you are
using unsupported graphics packages from a PPA. That is almost certainly
the problem. It also means this bug is 'Invalid' for standard Ubuntu.
Please remove the PPAs from your system using 'ppa-purge'. We can't
support PPAs. If
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
Thanks. I can't yet see any failures in failedboot.txt. What's strange
is that it claims to be using Xorg and rendering on the 1280x800 laptop
screen successfully.
1. Please check again that you followed the steps in comment #10
exactly, and redo them.
2. Please also run this command:
find /e
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
Even better, please:
1. Reproduce a failed boot, and then a successful boot immediately
after.
2. Run this command to collect the log from the previous failed boot:
journalctl -b-1 > failedboot.txt
and send us the resulting file 'failedboot.txt'.
--
You received this bug notification be
19 matches
Mail list logo
