vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10

Bug #1725236 reported by Christopher Crouzet
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I'm using a Dell XPS 9560 with a Geforce 1050.

Back on 17.04 (libvulkan-dev-1.0.42.0, nvidia-375) I could run vulkaninfo and my own Vulkan applications without a problem but, after switching to 17.10 (libvulkan-dev-1.0.61.1, nvidia-384), running vulkaninfo now results in the error attached. In other words, I cannot run any Vulkan-based application anymore.

I have tried using Vulkan's SDK 1.0.42.2 from LunarG's website without success.

I have been tempted to try rolling back to nvidia-375 but not being so familiar with Linux, I am a bit worried that things might go wrong.

Tags: nvidia vulkan
Revision history for this message
Christopher Crouzet (zcrou) wrote :
Revision history for this message
Christopher Crouzet (zcrou) wrote :

Here are some further investigations, if it can help:

- I have upgraded from 17.04 to 17.10 rather than doing a fresh install
- by default, the file /usr/share/vulkan/icd.d/nvidia_icd.json has its ICD's library_path set to libGL.so.1. If I change the value to libGLX_nvidia.so.0 instead, I can run vulkaninfo again without any problem
- `echo $XDG_SESSION_TYPE` returns x11. At the login screen, when clicking the cogwheel icon, I am not given the choice to use Wayland so I am using 'Gnome on Xorg' instead

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Confirmed
Revision history for this message
Lennart Blanco (cokebuttle) wrote :

I see same problem running Ubuntu 16.04 with Geforce GTX 1060 card, that is vulkan programs failing with VK_ERROR_INCOMPATIBLE_DRIVER.

Attaching output of the vulkaninfo just in case.

Replacing libGL.so.1 with libGLX_nvidia.so.0 in nvidia_icd.json also solves the issue for me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.