8

Today I have updated from my Ubuntu 18.04 to 18.10 by software upgrade app ( coudn't wait till tomorrow 😆). It took a bit of time, but at the end of it I was asked to restart my PC. Upon restarting, I get to boot runtime.

The boot log on screen passed numerous processes like gnome manager and stopped on "Started bpfilter". I waited 15 min., but nothing changed. Tried to restart the PC manually two times, but the result was still the same.

The interesting bit for me, after the message, it seems like an instance of terminal is given to me, - I can freely write letters. Though commands like cd, ls are not working. Everything is simply echoed back

My GPU is NVidia GTX 1060, cpu intel i5-7500. I dual boot along with Windows 10.

What would be your recommendations to fix this or debug what could be wrong?

  • 1
    Hello and welcome to AU. My recommendation is to expand your question a little bit: did it happen directly after installation, update,... What did you try ? – Marc Vanhoomissen Oct 17 '18 at 14:07
  • 1
    Hello, thanks for the warm reply, I added a bit more info. If anything else is needed, please feel free to ask. 🙂 – Akimbas Oct 17 '18 at 14:37
8

Actually, scratch that. Do this: edit /etc/gdm3/custom.conf and uncomment the line:

#WaylandEnable=false

The issue also doesn't seem to appear in a fresh install of Ubuntu 18.10.

Go here and press the affects me button to raise awareness. Feel free to provide information/logs needed by the developers in the comments. Thank you.

Removing the nvidia proprietary drivers seems to fix the issue. Go into recovery mode by pressing Shift during boot and run sudo apt-get remove --purge nvidia-* Say goodbye to gaming, though. I have filled a bug in Launchpad. You might want to press the "affects me" button. Thank you.

  • 3
    Confirmed that the fix is working, thanks – Akimbas Oct 20 '18 at 17:21
  • 2
    Even though I had a fresh install of 18.10, after some update I started facing this issue. The fix worked for me too. Thanks. – Dhruva Sagar Dec 9 '18 at 2:14
  • I had this problem on a Hyper-V virtual machine instance of Ubuntu 8.10 and this fixed it, thanks. – nakedfanatic Jan 24 at 22:21
3

On Ubuntu 18.10. kernel 4.18.0-12-generic, GNOME Shell 3.30.1 - X11, since a Dec 9 update, login kept hanging on Started bpfilter -- I think a possible conflict between systemd and bpfilter (I think managed by the kernel.) The following suggested fixes had no effect on my system:

  1. Removing nVidia drivers (my laptop uses Intel graphics, no nVida drivers installed, so this recommendation didn't apply,)
  2. Reverting to previous kernel 4.18.0-11-generic,
  3. Disabling Wayland in gdm3,
  4. Switching to LightDM display manager (identical hang.) I tried SLiM because it claimed not to require systemd, and it now enables normal login for me. Debian-branded, but allows changing the login background to something generic.

My fix procedure:

In Recovery Mode, select <Enable Networking> (this allows APT to connect online while in Recovery Mode,) then select <Drop to Shell Prompt>. Run (as root -- enter whoami to verify)

apt update && apt install slim

to install SLiM. To switch the display manager to SLiM, in Recovery Mode run (as root):

dpkg-reconfigure gdm3

then select SLiM, then 'restart now'.


SLiM will probably be a temporary recourse; with Ubuntu's continuing development I think systemd will be integral, so I've kept GDM3 and LightDM installed, in case a future kernel or systemd update fixes this issue.

This boot hang seems to be an upstream issue reported by users on other distros besides Ubuntu as well, Arch Linux especially.

1

I just had the same set of symptoms with the best results from the previous post:

  1. Recovery Mode
  2. apt-get install slim
  3. dpkg-reconfigure gdm3
  4. reboot
  • 2
    This seems like a re-hash of the upvoted answer. – Charles Green Feb 8 at 17:08

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.