System hangs after "Reached target Final Step" on "Starting reboot ..."

Bug #1770926 reported by Kerem Gümrükcü
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

After installing a fresh 18.04 x64 Lubuntu on a older Samsung R60 Plus laptop that was running an outdated Windows XP, i found out on my first reboot attempt after the installation had finished, that the entire system hang with a black screen and a frozen cursor at the upper left screen. I had to force shutdown the system with holding the power button. To investigate on that issue, i put "nosplash debug --verbose" to the grub command line and found out, that it get stuck/freeze at the final stage "Reached target Final Step" and the last message "Starting reboot ...". Using a reboot with -f (force) flag instantly freezes the entire system within the running system, no matter from GUI or Console and needs to be shut down by forcing the hardware from power button to turn off. The same is for shutdown commands: They all hang at the final stage. Updating to the latest kernel wont change anything. I also checked the 16.04 X64 and 17.10 X64 variants with the latest kernels and they hang at the exactly same final message on the shutdown/reboot screen. Using grub command line with acpi=force wont change anything and the system still get stuck at that final stage. I am not sure whether this is a kernel bug or some faulting script or possibly a system specific issue tied to the Samsung R60 Plus laptop, but the issue persists on 16.04, 17.10 and latest 18.04.

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/1770926/+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.]

tags: added: bot-comment
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.