Problem after 17.04 to 17.10 upgrade

I tried first with a Question, and there is slightly more detail with it.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1730480/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

I tried - Temporary: Press 'Escape' key at the 3 second pause by Grub bootloader - without sucess.

The motherboard is a Gigabyte MA74GMT-S2 with an AMD64 cpu, and onboard graphics from an AMD740G.

During an attempt at a normal bootup, the system reaches the Ubuntu screen with the five dots. The dots change colour in sequence, and the mouse pointer appears. The the display shows /dev/sda1 ....etc... and then "flashes" showing what appears to be lines of white text with one "word" in red. The text appears for too short a time to be readable. The top line /dev/sda1 remains clearly visible and stable.

The sytem runs normally after a bootup with Grub. Except for the Stop Job at shut down.

This change was made by a bot.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8

Hi

Thank you for taking an interest in this. I am sorry, but the testing
you suggest seems to be too complicated for me.

However, I have watched the Grub boot up carefully - it scrolls past
quickly - but I have spotted, before the Recovery Menu, a line that I
think reads, in part, ... DM:RADEON_INIT [RADEON] ERROR .....

I can use the computer as it is, and will wait for the next linux
upgrade, and let you know what happens.

Thanks again,

George Herrick.

-----------------------

On Tue, 07 Nov 2017 21:32:54 -0000
Joseph Salisbury <email address hidden> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

This is an image of the line that is visible in the sequence between the Grub menu and the Recovery Menu.
Hope that helps.

This is after update to Linux 4.13.0.17

Computer will still not boot normally - the image attached shows part of the screen that displays/flashes continuously.

Grub boot still ok.

This is after update to Linux 4.13.0.19

Computer will still not boot normally - and still has error on power off.

Grub boot (recovery mode) still ok.

such issue is usually met in two cases:
- either the system has been dist-upgraded at least one time, and need a deep clean via gtkorphan & bleachbit (as root, but select the option carefully)
- or (in case the above method is not enough) there is some borked settings inside .local, or .config. To test, create and use a new user: if the new user does not met the problem you have described, then you can do a copy of these hidden dirs, and reboot (they will be recreated, but you will loose the custom settings indeed).

Thanks.

gtkorphan has not fixed it.

bleachbit looks "difficult". Any advice on what to select ? System perhaps ?

I have now run Bleachbit. That has not fixed the problem.

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