[Expired for nvidia-graphics-drivers-470 (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is this bug still present in Ubuntu 21.10? If you find slightly
different issues there then we should open new bugs for them.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: Confirmed =>
Sounds like the root cause here is the same as bug 1716857.
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Vulkan not
** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Confirmed
** Tags added: disco nvidia-drm.modeset
--
You received this bug notification because you are a member of Ubuntu
This still occurs in 19.04 with nvidia-driver-418.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
(Optimus)
To
The bug is still there on Ubuntu 18.04 with newer drivers and kernel:
nvidia-driver-418
linux-image-4.18.0-16-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Vulkan not working
I have the exact same bug. This one seems to be related:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Vulkan not
I have the same fail, since I updated Nvidia version (to 410), and then
even returning to 396, Vulkan doesn't work, with vulkaninfo appears in
terminal the same text as nastys.
But with "sudo vulkaninfo" Vulkan works.
PD: I have Ubuntu 18.04 with Gnome, and Nvidia's drivers.
--
You received
As a workaround one needs to run (after each reboot):
sudo vulkaninfo
and then all vulkan apps start to work properly until system is shut
down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Can be the same issue as
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800465
Only happening with GDM in ubuntu 18.04 with updated nvidia drivers and ubuntu
18.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: bionic nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
(Optimus)
To manage notifications
I can confirm this is still an issue.
My setup is:
Ubuntu 18.04
MSI GE60
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Intel HD 4600 + GeForce GTX 760M
nvidia-driver-396 (396.54-0ubuntu0~gpu18.04.1 from grphics-drivers PPA)
nvidia-prime for switching cards
With nvidia-drm.modeset=1 until some vulkan
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK. Sounds like there is a device (/dev/* file) that you're not getting
correct access to. And you can only get around that limitation by
running as root (which is not recommended, for security).
In this case we may find it's an nvidia driver (or installation) bug.
Although your original
I have found out just now that if I run anything Vulkan as root (e.g.
sudo vulkan-smoketest), IT WORKS! And if I then run it without sudo, IT
STILL WORKS!
At this point I have no idea what is going on, nor why this doesn't affect
lightdm nor sddm.
It seems the affected package is indeed
After some investigating, I have found that if I log out, switch to TTY then
run startx, I get the same issue. However I noticed that if I run sudo startx,
Vulkan works, and it still works after logging out and running startx as a
normal user, until the computer is rebooted. Then I tried
I know that VSync and PRIME Sync are not the same thing. With modeset
disabled, VSync IS enabled but there is tearing regardless, and I can
see that even just by dragging a window around the screen.
glxgears reports:
Running synchronized to the vertical refresh. The framerate should be
"VSync" and "PRIME Sync" are unrelated things. You need to ignore the
fact that they sound similar. You should be able to achieve perfect
VSync regardless of the "modeset" option. But it may be disabled by
default (by Nvidia) as alluded to earlier.
The "NV-GLX" error sounds expected... In a
I have also added WaylandEnabled=false to /etc/gdm3/custom.conf and
Vulkan still doesn't work. I also lost the option to log into Wayland
from the login screen.
@vanvugt Are you sure this isn't a bug in gdm3?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
nvidia-drm.modeset=1 is used for PRIME Sync. In a gist, it copies the
framebuffer from the dGPU to the iGPU without tearing. Without this,
VSync is not effective no matter what.
I have switched back to gdm3. In Xorg, OpenGL works as expected, with
the NVIDIA GPU (according to glxinfo), but Vulkan
There's probably no way GDM could cause this directly. But indirectly if
you are logging into a Wayland session in one case and Xorg in the
other, then that might be the main factor here.
Please try logging into both Xorg and Wayland sessions to see if one
works better.
Also, for Nvidia there
** Description changed:
+ Lenovo ideapad 510-15IKB
OS: Ubuntu 18.04 bionic
Kernel: x86_64 Linux 4.15.0-20-generic
DE: GNOME
CPU: Intel Core i5-7200U @ 4x 3.1GHz
GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus)
UEFI boot, Secure Boot disabled.
I installed the proprietary
23 matches
Mail list logo
