Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-390 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I was carrying out this testcase for proprietary Nvidia drivers testing: http://
After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC.
On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message:
(1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit).
(2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit).
I rebooted after waiting 15 minutes as I was tired of waiting.
This is my display hardware:
*-display
description: VGA compatible controller
product: GM206 [GeForce GTX 960]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nouveau latency=0
resources: irq:125 memory:
Link to the testcase revision Edit result
My PC is a:
product: XPS 8900 (06B8)
vendor: Dell Inc.
width: 64 bits
affects: | ubuntu-tf101 → nvidia-graphics-drivers-390 (Ubuntu) |
Changed in nvidia-graphics-drivers-390 (Ubuntu): | |
status: | Incomplete → New |
Changed in nvidia-graphics-drivers-390 (Ubuntu): | |
status: | New → Confirmed |
Thanks for your report.
Could you please attach the journal from the boot that failed?
You can get a list of the boots with the command: journalctl --list-boots
Then the journal of a given boot with: journalctl -b [id]
Where id is correspond to the id of the boot returned by list-boots
Thanks.