Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

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

I can confirm this bug, it's happened to me when trying to use that driver, however the later driver series works fine.

Thanks for posting the solution to the typo. Gratitude.... kudos Alex (and anyone else if you have contributed to this solution).

I found the file /usr/share/vulkan/icd.d/nvidia_icd.json and from it replaced the string "libGL.so.1" with "libGLX_nvidia.so.0" and Vulkan works again.

My system had upgraded to this driver at the start of this week. I had a new system installed 1 day ago and have the same issue. Hope the Maintainer can quickly correct the typo to avoid unnecessary user panic attacks.

I have just uploaded a fix for 17.04 to the following PPA:
https://launchpad.net/~albertomilone/+archive/ubuntu/deleteme-nvidia

Can you test it, please?

Looks like that's working here, thanks!

Thanks for testing.

The fix seems to break Wayland. I need to investigate the problem before I
SRU the fix.

On 26 Oct 2017 12:11, "Alex Smith" <email address hidden> wrote:

Looks like that's working here, thanks!

--
You received this bug notification because you are a bug assignee.
https://bugs.launchpad.net/bugs/1726809

Title:
  Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/
1726809/+subscriptions

Launchpad-Notification-Type: bug
Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-graphics-drivers-384;
component=restricted; status=In Progress; importance=High; assignee=
<email address hidden>;
Launchpad-Bug-Information-Type: Public
Launchpad-Bug-Private: no
Launchpad-Bug-Security-Vulnerability: no
Launchpad-Bug-Commenters: albertomilone asmith-feral janitor liamdawe
sunbear-c22
Launchpad-Bug-Reporter: Alex Smith (asmith-feral)
Launchpad-Bug-Modifier: Alex Smith (asmith-feral)
Launchpad-Message-Rationale: Assignee
Launchpad-Message-For: albertomilone

Hello Alex, or anyone else affected,

Accepted nvidia-graphics-drivers-384 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/384.90-0ubuntu0.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Alex, or anyone else affected,

Accepted nvidia-graphics-drivers-384 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/384.90-0ubuntu0.17.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Alex, or anyone else affected,

Accepted nvidia-graphics-drivers-384 into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/384.90-0ubuntu3.17.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

This bug was fixed in the package nvidia-graphics-drivers-384 - 384.90-0ubuntu4

---------------
nvidia-graphics-drivers-384 (384.90-0ubuntu4) bionic; urgency=medium

  * debian/rules,
    debian/templates/nvidia-graphics-drivers.links.in,
    debian/templates/nvidia-graphics-drivers.links32.in:
    - Ship the correct (non GLVND) libGL and libEGL libraries (LP: #1726809).

 -- Alberto Milone <email address hidden> Mon, 30 Oct 2017 16:01:58 +0100

I've confirmed that the nvidia-384 package in zesty-proposed is working as expected (both GL and Vulkan apps work correctly).

Thanks!

Hi!

I updated my drive to version 384.90-0ubuntu3.17.10.1. but the error continues to pop up.

ERROR: [loader] Code 0 : loader_scanned_icd_add: Attempt to retrieve either 'vkGetInstanceProcAddr' or 'vk_icdGetInstanceProcAddr' from ICD libGL.so.1 failed.
Cannot create Vulkan instance.
/build/vulkan-L06RNr/vulkan-1.0.61.1+dfsg1/demos/vulkaninfo.c:704: failed with VK_ERROR_INCOMPATIBLE_DRIVER

Thanks!

I reinstalled the mesa-vulkan-drivers, now it's working!
Thank you!

This bug was fixed in the package nvidia-graphics-drivers-384 - 384.90-0ubuntu3.17.10.1

---------------
nvidia-graphics-drivers-384 (384.90-0ubuntu3.17.10.1) artful-proposed; urgency=medium

  * debian/rules,
    debian/templates/nvidia-graphics-drivers.links.in,
    debian/templates/nvidia-graphics-drivers.links32.in:
    - Ship the correct (non GLVND) libGL and libEGL libraries (LP: #1726809).

 -- Alberto Milone <email address hidden> Mon, 30 Oct 2017 16:01:58 +0100

The verification of the Stable Release Update for nvidia-graphics-drivers-384 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package nvidia-graphics-drivers-384 - 384.90-0ubuntu0.17.04.2

---------------
nvidia-graphics-drivers-384 (384.90-0ubuntu0.17.04.2) zesty-proposed; urgency=medium

  * debian/rules,
    debian/templates/nvidia-graphics-drivers.links.in,
    debian/templates/nvidia-graphics-drivers.links32.in:
    - Ship the correct (non GLVND) libGL and libEGL libraries (LP: #1726809).

 -- Alberto Milone <email address hidden> Mon, 30 Oct 2017 17:32:58 +0100

I can confirm that the fix works in xenial too.

This bug was fixed in the package nvidia-graphics-drivers-384 - 384.90-0ubuntu0.16.04.2

---------------
nvidia-graphics-drivers-384 (384.90-0ubuntu0.16.04.2) xenial-proposed; urgency=medium

  * debian/rules,
    debian/templates/nvidia-graphics-drivers.links.in,
    debian/templates/nvidia-graphics-drivers.links32.in:
    - Ship the correct (non GLVND) libGL and libEGL libraries (LP: #1726809).

 -- Alberto Milone <email address hidden> Mon, 30 Oct 2017 17:49:28 +0100

This needs to be ported to nvidia-387, which still has this bug. The problem is to locate where to report the isssue.