[Desktop-packages] [Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set (Optimus)
** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Description changed: OS: Ubuntu 18.04 bionic Kernel: x86_64 Linux 4.15.0-20-generic - DE: GNOME + 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 graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. - Other GNU/Linux distributions such as Manjaro don't seem to be affected - which is why I'm reporting this here. + Everything works fine if lightdm is used instead of gdm3. ** Summary changed: - Vulkan not working if nvidia-drm.modeset=1 is set (Optimus) + Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) ** Description changed: 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 graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. - Everything works fine if lightdm is used instead of gdm3. + Everything works as expected if lightdm is used instead of gdm3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) Status in gdm3 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: 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 graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. Everything works as expected if lightdm is used instead of gdm3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397676] Re: Numlock LED inverted when a modifier is pressed after logging in
** Description changed: When I'm logging in, numlock is working fine. After logging in, numlock and its led are ON. When I press a modifier key (Alt, CTRL, etc...) the LED turns OFF but numlock is still enabled. If I disable numlock, the LED remains OFF. Then it works normally. - I'm using Ubuntu 14.10 and lightdm '1.12.1-0ubuntu1'. + I'm using Ubuntu 14.10. It works fine with other environments (KDE, + GNOME, etc...). ** Package changed: lightdm (Ubuntu) = compiz (Ubuntu) ** Description changed: When I'm logging in, numlock is working fine. After logging in, numlock and its led are ON. When I press a modifier key (Alt, CTRL, etc...) the LED turns OFF but numlock is still enabled. If I disable numlock, the LED remains OFF. Then it works normally. - I'm using Ubuntu 14.10. It works fine with other environments (KDE, + I'm using Ubuntu 14.10. It does not affect other environments (KDE, GNOME, etc...). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1397676 Title: Numlock LED inverted when a modifier is pressed after logging in Status in compiz package in Ubuntu: New Bug description: When I'm logging in, numlock is working fine. After logging in, numlock and its led are ON. When I press a modifier key (Alt, CTRL, etc...) the LED turns OFF but numlock is still enabled. If I disable numlock, the LED remains OFF. Then it works normally. I'm using Ubuntu 14.10. It does not affect other environments (KDE, GNOME, etc...). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1397676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397676] [NEW] Numlock LED inverted when a modifier is pressed after logging in
Public bug reported: When I'm logging in, numlock is working fine. After logging in, numlock and its led are ON. When I press a modifier key (Alt, CTRL, etc...) the LED turns OFF but numlock is still enabled. If I disable numlock, the LED remains OFF. Then it works normally. I'm using Ubuntu 14.10 and lightdm '1.12.1-0ubuntu1'. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1397676 Title: Numlock LED inverted when a modifier is pressed after logging in Status in lightdm package in Ubuntu: New Bug description: When I'm logging in, numlock is working fine. After logging in, numlock and its led are ON. When I press a modifier key (Alt, CTRL, etc...) the LED turns OFF but numlock is still enabled. If I disable numlock, the LED remains OFF. Then it works normally. I'm using Ubuntu 14.10 and lightdm '1.12.1-0ubuntu1'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1397676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1307144] [NEW] 'unredirect fullscreen windows' causes tearing
Public bug reported: Ubuntu release: 14.04 Installed compiz version: 1:0.9.11+14.04.20140409-0ubuntu1 The option 'unredirect fullscreen windows', which is enabled by default in Compiz, causes tearing in games and other fullscreen OpenGL applications, even with 'sync to vblank' options enabled in ccsm, in the GPU settings and in the game. With this option disabled, VSync works as fine as should with 'unredirected fullscreen windows' enabled and there is no tearing (but this causes performance issues and the Unity panel shadow on top of the application). Tested with: - ASUS NVIDIA GTX 650-E-1GD5 with NVIDIA proprietary driver 331.38 (tested) (nvidia-331) - the same graphics card with NVIDIA proprietary driver 331.38 (nvidia-331-updates) - the same graphics card with Nouveau open source driver (xserver-xorg-video-nouveau) - Intel HD 4000 iGPU with default open source drivers ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: compiz tearing vblank vsync -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1307144 Title: 'unredirect fullscreen windows' causes tearing Status in “compiz” package in Ubuntu: New Bug description: Ubuntu release: 14.04 Installed compiz version: 1:0.9.11+14.04.20140409-0ubuntu1 The option 'unredirect fullscreen windows', which is enabled by default in Compiz, causes tearing in games and other fullscreen OpenGL applications, even with 'sync to vblank' options enabled in ccsm, in the GPU settings and in the game. With this option disabled, VSync works as fine as should with 'unredirected fullscreen windows' enabled and there is no tearing (but this causes performance issues and the Unity panel shadow on top of the application). Tested with: - ASUS NVIDIA GTX 650-E-1GD5 with NVIDIA proprietary driver 331.38 (tested) (nvidia-331) - the same graphics card with NVIDIA proprietary driver 331.38 (nvidia-331-updates) - the same graphics card with Nouveau open source driver (xserver-xorg-video-nouveau) - Intel HD 4000 iGPU with default open source drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1307144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
