[Bug 1810815] Re: Boot splash screen is empty in Ubuntu 18.04 with nvidia proprietary driver

uframer uframer at gmail.com
Mon Jan 7 17:10:01 UTC 2019 

Plymouth logs in syslog are:

Jan  7 21:35:56 purple-warthog plymouthd[610]: [main.c:1973]                               check_verbosity:redirecting debug output to /dev/tty1
Jan  7 21:35:56 purple-warthog plymouth[636]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jan  7 21:35:56 purple-warthog plymouth[636]: [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
Jan  7 21:35:56 purple-warthog kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7115997a-b8fb-468a-8215-d9bf792ec77f ro quiet splash vt.handoff=1 plymouth:debug
Jan  7 21:35:56 purple-warthog plymouth[636]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jan  7 21:35:56 purple-warthog plymouth[636]: [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
Jan  7 21:35:56 purple-warthog plymouth[636]: [./ply-boot-client.c:810]        ply_boot_client_detach_from_event_loop:detaching from event loop
Jan  7 21:35:56 purple-warthog systemd[1]: Starting Show Plymouth Boot Screen...
Jan  7 21:35:56 purple-warthog systemd[1]: Started Show Plymouth Boot Screen.
Jan  7 21:35:56 purple-warthog systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Jan  7 21:35:56 purple-warthog systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Jan  7 21:35:56 purple-warthog plymouth[1105]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jan  7 21:35:56 purple-warthog plymouth[1105]: [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
Jan  7 21:35:56 purple-warthog plymouth[1105]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jan  7 21:35:56 purple-warthog plymouth[1105]: [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
Jan  7 21:35:56 purple-warthog plymouth[1105]: [./ply-boot-client.c:810]        ply_boot_client_detach_from_event_loop:detaching from event loop
Jan  7 21:35:56 purple-warthog systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Jan  7 21:35:56 purple-warthog kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7115997a-b8fb-468a-8215-d9bf792ec77f ro quiet splash vt.handoff=1 plymouth:debug
Jan  7 21:35:58 purple-warthog systemd[1]: Received SIGRTMIN+21 from PID 627 (plymouthd).
Jan  7 21:35:58 purple-warthog plymouth[1519]: [ply-event-loop.c:1060]   ply_event_loop_handle_disconnect_for_source:calling disconnected_handler 0x5637043ac650 for fd 6
Jan  7 21:35:58 purple-warthog plymouth[1519]: [./plymouth.c:421]                                 on_disconnect:disconnect
Jan  7 21:35:58 purple-warthog plymouth[1519]: [ply-event-loop.c:1064]   ply_event_loop_handle_disconnect_for_source:done calling disconnected_handler 0x5637043ac650 for fd 6
Jan  7 21:35:58 purple-warthog plymouth[1519]: [ply-event-loop.c:1144]   ply_event_loop_free_destinations_for_source:freeing destination (0, (nil), 0x5637043ac650) of fd 6
Jan  7 21:35:58 purple-warthog plymouth[1519]: [./ply-boot-client.c:810]        ply_boot_client_detach_from_event_loop:detaching from event loop
Jan  7 21:35:59 purple-warthog /usr/lib/gdm3/gdm-x-session[1764]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7115997a-b8fb-468a-8215-d9bf792ec77f ro quiet splash vt.handoff=1 plymouth:debug
Jan  7 21:36:11 purple-warthog /usr/lib/gdm3/gdm-x-session[2318]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7115997a-b8fb-468a-8215-d9bf792ec77f ro quiet splash vt.handoff=1 plymouth:debug

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1810815

Title:
  Boot splash screen is empty in Ubuntu 18.04 with nvidia proprietary
  driver

Status in plymouth package in Ubuntu:
  New

Bug description:
  I have a PC with duo 1080Ti cards and with nvidia proprietary driver
  (from CUDA repo) installed. During booting, plymouth splash screen is
  empty.

  The driver I used is:

      ye at purple-warthog:~/Downloads$ cat /etc/apt/sources.list.d/cuda.list
      deb http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /

      ye at purple-warthog:~/Downloads$ LC_ALL='C' apt search "^nvidia" |
  grep installed

      WARNING: apt does not have a stable CLI interface. Use with
  caution in scripts.

      cuda-nsight-compute-10-0/unknown,now 10.0.130-1 amd64 [installed,automatic]
      cuda-nvtx-10-0/unknown,now 10.0.130-1 amd64 [installed,automatic]
      libnccl-dev/unknown,now 2.3.4-1+cuda10.0 amd64 [installed]
      libnccl2/unknown,now 2.3.4-1+cuda10.0 amd64 [installed]
      libnvidia-cfg1-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      libnvidia-compute-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      libnvidia-decode-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      libnvidia-fbc1-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      libnvidia-gl-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      libnvidia-ifr1-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      nvidia-compute-utils-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      nvidia-dkms-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      nvidia-driver-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      nvidia-kernel-common-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      nvidia-kernel-source-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      nvidia-prime/bionic-updates,bionic-updates,now 0.8.8.2 all [installed,automatic]
      nvidia-settings/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      nvidia-utils-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]
      xserver-xorg-video-nvidia-410/unknown,now 410.79-0ubuntu1 amd64 [installed,automatic]

  And the plymouth version is:

      ye at purple-warthog:~/Downloads$ LC_ALL='C' apt search "^plymouth" |
  grep installed

      WARNING: apt does not have a stable CLI interface. Use with
  caution in scripts.

      plymouth/bionic-updates,now 0.9.3-1ubuntu7.18.04.1 amd64 [installed]
      plymouth-label/bionic-updates,now 0.9.3-1ubuntu7.18.04.1 amd64 [installed]
      plymouth-theme-ubuntu-logo/bionic-updates,now 0.9.3-1ubuntu7.18.04.1 amd64 [installed]
      plymouth-theme-ubuntu-text/bionic-updates,now 0.9.3-1ubuntu7.18.04.1 amd64 [installed]
      plymouth-x11/bionic-updates,now 0.9.3-1ubuntu7.18.04.1 amd64 [installed]

  To get more details, I appended "plymouth:debug" to kernel command
  line. The content of the generated "/var/log/plymouth-debug.log" is
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: plymouth 0.9.3-1ubuntu7.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan  8 00:57:35 2019
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  InstallationDate: Installed on 2018-05-09 (243 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7115997a-b8fb-468a-8215-d9bf792ec77f ro quiet splash vt.handoff=1 plymouth:debug
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7115997a-b8fb-468a-8215-d9bf792ec77f ro quiet splash vt.handoff=1 plymouth:debug
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0407
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X399-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0407:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810815/+subscriptions

More information about the foundations-bugs mailing list