Black screen with messages after new install 17.10

Bug #1719191 reported by corrado venturini on 2017-09-24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)

Bug Description

I installed Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) on my PC from an USB key . The installation run without errors but after the message 'Installation complete ... restart now' i saw just a black screen with only 3 messages:

Couldn't get size: 0x800000000000000e
MODSIGN: Couldn't get UEFI db list
Couldn't get size: 0x800000000000000e
and nothing else.

After a while I pressed the power-off button and at power-on the system started ok.

I have a multi-boot on an UEFI disk:
corrado@corrado-aa-0919-p9:~$ sudo lsblk -o NAME,LABEL,SIZE,FSTYPE,UUID,MOUNTPOINT
[sudo] password for corrado:
loop0 81,4M squashfs /snap/core/2898
loop1 135,4M squashfs /snap/gimp/25
sda 931,5G
├─sda1 256M vfat 1BE3-7FBC /boot/efi
├─sda2 8G swap c2e53ec7-5ac9-4a78-b45c-0b4dac1e3796 [SWAP]
├─sda3 32G ext4 07575f68-3368-4342-8698-25c6b4f98bb9
├─sda4 32G ext4 acf3839b-7ed0-4e48-a751-729226005018
├─sda5 32G ext4 018125f1-5d18-4014-8c98-05895917cecd
├─sda6 p6-aa-0701 32G ext4 813c705f-7625-4cb3-9f00-76d7985e09e1
├─sda7 32G ext4 865207ab-c82c-4903-b3ce-a15c2142aa4a
├─sda8 p8-aa-0626 32G ext4 fd85e65b-51be-4c4b-b48a-41f17df345e0
├─sda9 32G ext4 405e72ac-f610-4e04-84cb-2720b3fa0b90 /
├─sda10 p10-xeni 32G ext4 f8d52995-0139-40e5-b332-56e711eff4cb
├─sda11 dati1 128G ext4 036ea265-8c5e-41a9-9375-c5ea71a11cfa /media/corrado/dati1
├─sda12 dati2 256G ext4 c7ae5473-33be-4517-a653-06e2b137871f
└─sda13 dati3 283,3G ext4 4bac0904-c00b-4453-bdd0-3c0df42d1ec2
sr0 1024M

I have the same problem installing on a different partition from DVD.
I had also the same problem installing a preceding daily on a different hardware (my HP laptop)

After install I have not done anything on this partition (I'm working from another one) so i may provide all the logs to help diagnose the problem.

corrado@corrado-aa-0919-p9:~$ inxi -Fx
System: Host: corrado-aa-0919-p9 Kernel: 4.13.0-11-generic x86_64 bits: 64 gcc: 7.2.0
           Desktop: Gnome 3.26.0 (Gtk 3.22.21-0ubuntu1) Distro: Ubuntu Artful Aardvark (development branch)
Machine: Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x serial: N/A UEFI: American Megatrends v: F3 date: 04/24/2013
CPU: Dual core Intel Core i3-4130 (-HT-MCP-) arch: Haswell rev.3 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13568
           clock speeds: max: 3400 MHz 1: 3392 MHz 2: 3392 MHz 3: 3392 MHz 4: 3392 MHz
Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.3 ) driver: i915 Resolution: 1680x1050@59.88hz
           OpenGL: renderer: Mesa DRI Intel Haswell version: 4.5 Mesa 17.2.1 Direct Render: Yes
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.13.0-11-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 94:de:80:7e:90:a7
Drives: HDD Total Size: 1000.2GB (6.0% used)
           ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 32G used: 4.7G (16%) fs: ext4 dev: /dev/sda9
           ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: N/A
Info: Processes: 239 Uptime: 1:42 Memory: 1260.3/7859.8MB Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.121) inxi: 2.3.37

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 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 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
tags: added: artful

I have no idea about the package, the problem occurs at end of installation, system is not yet started. I see only a black screen as from attachment. May you suggest where i can look? thanks.

affects: ubuntu → ubiquity (Ubuntu)

At end install of recent daily (0926 and 0930) I have the following messages and then ... nothing more. After hardware power-off and restart the system works fine.

[ 0.000000] [Firmware bug]: TSC_DEADLINE disabled due to Errata: please update microcode to version 0x52 (or later)
[ 4.094635] Couldn't get size: 0x800000000000000e
[ 4.094648] MODSIGN: Couldn't get UEFI db list
[ 4.096356] Couldn't get size: 0x800000000000000e

The problem and the message about Firmware bug occurs on all 3 my PC's all with Intel CPU.

The last 3 messages appear also at each boot:

10:40:03 gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
10:39:37 colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
10:39:20 gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
10:39:19 NetworkManager: ((src/devices/nm-device.c:1452)): assertion '<dropped>' failed
10:39:16 avahi-daemon: chroot.c: open() failed: No such file or directory
10:39:07 kernel: Couldn't get size: 0x800000000000000e
10:39:07 kernel: MODSIGN: Couldn't get UEFI db list
10:39:07 kernel: Couldn't get size: 0x800000000000000e

it seems a common problem also if nobody sign up on my bug.

still same problem installing Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)

Doug McMahon (mc3man) wrote :

This *could* be another variation of this bug, in any event it's well known that the odds of successfully exiting a live session with gdm3 are slim to none. Also noted that the below won't be fixed in 17.10.

Problem disappeared installing Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171108)

Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Mariusz Kubański (spass) wrote :

Unfortunately I can confirm this issue on 18.04 Bionic Daily too. amd64 UEFI install on Dell E6410 laptop, alongside Windows 7.

tags: added: bionic
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing

I'm experiencing this on ubuntu-18.04-live-server-amd64.iso, trying to install to FreeBSD's bhyve virtualmachine. Host system is FreeNAS-11.1-U4

I'm starting my VM with the following command:
$ bhyve -H -w -c 1 -m 1024 -s 0:0,hostbridge -s 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -s 3,virtio-net,tap8,mac=00:a0:98:1d:50:33 -s 29,fbuf,vncserver,tcp=,w=1280,h=1024,, -s 30,xhci,tablet -s 4,virtio-blk,/dev/zvol/storage/vms/myvmdisk -s 5,ahci-cd,/mnt/storage/ubuntu-18.04-live-server-amd64.iso 15_myvm

if I leave it long enough, eventually I get "INFO: task kworker/0:1:32 blocked for more than 120 seconds. Not tainted 4.15.0-20-generic #21-ubuntu"

Phillip Susi (psusi) on 2018-06-08
affects: ubiquity (Ubuntu) → grub2-signed (Ubuntu)

Old problem about Ubuntu 17.10. Changed status to invalid.

Changed in grub2-signed (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers