1

I'm currently running dual boot Ubuntu 17.10 GNOME. I updated my splash screen theme to one of plymouth's. About 3-7 seconds in to the loading, My splash screen seems to be getting interrupted by the following messages:

[    9.503563] systemd[1]: bluetooth.service: Service lacks both ExecStart= and
[   23.132055] usb 2-5: device descriptor read/64, error -110

Here's my /etc/default/grub file:

GRUB_DEFAULT="saved"
#GRUB_HIDDEN_TIMEOUT="0"
GRUB_HIDDEN_TIMEOUT_QUIET="true"
GRUB_TIMEOUT="7"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash"
GRUB_CMDLINE_LINUX=""
GRUB_BACKGROUND="/boot/grub/zebra.png"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="1366x768"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

export GRUB_MENU_PICTURE="/home/qorka/Pictures/Plasma.png"
export GRUB_COLOR_NORMAL="white/black"
export GRUB_COLOR_HIGHLIGHT="light-magenta/black"


GRUB_SAVEDEFAULT="true"

GRUB_FONT="/boot/grub/unicode.pf2"

Not exactly sure where the issue is or if this is fixable.

10
  • The first message is already way past the Grub/Plymouth stage. It says that there is something wrong with the Bluetooth service file, which is by default located in /lib/systemd/system/bluetooth.service. Your system complains that it is missing an ExecStart= statement, which I can confirm ought to be there. Please take a look at that file and tell us what you find.
    – Jos
    Mar 13, 2018 at 12:23
  • I had commented out the ExecStart line to permanently disable bluetooth. Could that be the issue?
    – qorka
    Mar 13, 2018 at 12:28
  • Yes, that must be it. The command for that is sudo systemctl disable bluetooth.
    – Jos
    Mar 13, 2018 at 12:30
  • About the other error message, see here.
    – Jos
    Mar 13, 2018 at 12:34
  • I don't have a USB plugged in, so that's pretty weird. I've been seeing that error for quite some time now too.
    – qorka
    Mar 13, 2018 at 12:38

0

You must log in to answer this question.

Browse other questions tagged .