Ubuntu 18.10 stuck on "Started bpfilter" while booting

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.


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.


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