[Ubuntu-x-swat] [Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
*** This bug is a duplicate of bug 1841718 *** https://bugs.launchpad.net/bugs/1841718 was fixed for me with common Ubuntu updates related to bug #1841718. ** This bug has been marked a duplicate of bug 1841718 [radeon] Rendering of combo boxes and tooltips is broken -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860268/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1861043] Re: Xorg freeze
Thanks. Yes the messages about "Memory pressure relief" sound unusual. I've never seen that before. Don't worry about the inability to switch VTs. That's not part of the bug, that's just because switching VTs is the responsibility of the currently active display server. If Xorg has frozen then you also won't be able to switch VTs. Next, please monitor the memory usage of your processes before the next freeze happens, with something like: ps auxw --sort -rss | head so we can identify if and what is using too much memory. In case the issue is gnome-shell like it sounds, please also ensure you have uninstalled all third-party gnome-shell extensions except for the standard Ubuntu ones. ** Tags added: nvidia ** Summary changed: - Xorg freeze + [nvidia] System freeze ** Package changed: xorg-server (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861043 Title: [nvidia] System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1861043/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
I can't find any existing reports of that secondary crash, but ideally it would not usually be part of the fix here... I guess it's OK if the secondary crash was impossible without the first fix. If it wasn't then ideally a new bug should be opened to describe that and both bugs mentioned in the patch. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
This debdiff for Focal fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start). ** Patch added: "refreshed debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323933/+files/xorg-server_1.20.6-1ubuntu2.debdiff ** Patch removed: "xorg-server-iglx.diff" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323631/+files/xorg-server-iglx.diff ** Patch removed: "debdiff for bionic" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323649/+files/xorg-server_1.19.6-1ubuntu4.4.debdiff ** Patch removed: "debdiff for eoan" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323650/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff ** Patch removed: "debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323651/+files/xorg-server_1.20.6-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
The refreshed patches fix both crashes. The first change is upstream commit e1fa3be [1] and the second change is from upstream PR 388 [2]. @Sponsors, this is now good to go from my point of view. [1] https://gitlab.freedesktop.org/xorg/xserver/commit/e1fa3beb2fe2519e69f859f0acdc68e5a770de27 [2] https://gitlab.freedesktop.org/xorg/xserver/merge_requests/388 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
This debdiff for Eoan fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start). ** Patch added: "refreshed debdiff for eoan" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323932/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
This debdiff for Bionic fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start). ** Patch added: "refreshed debdiff for bionic" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323931/+files/xorg-server_1.19.6-1ubuntu4.4.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1861043] Re: Xorg freeze
Here's the prevboot. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+attachment/5323859/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861043 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1860042] Re: openCL application gives error after update
check libclc-amdgcn instead in any case, this has been verified on eoan already, bionic needs to be verified too -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libclc in Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1860042/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1860042] Re: openCL application gives error after update
wrong package, this is not related to mesa -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libclc in Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1860042/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1860522] Re: Mesa 19.2.8 stable release
Installed from the proposed repository the version 19.2.8-0ubuntu0~19.10.1 Works great on: Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-29-generic OS Type: 64-bit Processors: 4 × AMD A8-6500T APU with Radeon(tm) HD Graphics Memory: 7.0 GiB of RAM Thanks for backporting the update! ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860522 Title: Mesa 19.2.8 stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1860042] Re: openCL application gives error after update
The eoan-proposed repository didn't work for me. This is what apt-cache says: mesa-opencl-icd: Installed: 19.2.8-0ubuntu0~19.10.1 Candidate: 19.2.8-0ubuntu0~19.10.1 Version table: *** 19.2.8-0ubuntu0~19.10.1 500 500 http://ca.archive.ubuntu.com/ubuntu eoan-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 19.2.8-0ubuntu0~19.10.1~ppa1 500 500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu eoan/main amd64 Packages 19.2.1-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libclc in Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1860042/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
** Changed in: xorg-server Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-340 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.108-0ubuntu0.18.04.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1854485/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1861294] [NEW] Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu
Public bug reported: Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake 3x8 GT2). I had chrome, slack and vmware-player running in Gnome. While doing some git clone, screen+mouse+keyboard froze for 2 minutes after which xorg and everything else recovered. I saw this in dmesg: kernel: show_signal_msg: 2 callbacks suppressed kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000] kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller kernel: nvme nvme0: 12/0/0 default/read/poll queues While writing this bug report, the system froze again, and this time it didn't recover. After a cold reset I didn't see any other GpuWatchdog messages in journalctl. Ubuntu applied a BIOS firmware update before the first freeze, so my BIOS was updated as part of the cold reset I did. Not sure if this is relevant to reproducing the freeze. ** Affects: intel-gpu-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1861294 Title: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1861294/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-340 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.108-0ubuntu0.19.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-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1854485/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1631715] Re: Password required twice returning from suspend
Stephen, do you use xfce4-screensaver? Is the other lock screen from light-locker. You do not have to use both. Check your autostarts. Purging light-locker changes power manager settings UI, but there is still checkbox for locking. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1631715 Title: Password required twice returning from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1631715/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1631715] Re: Password required twice returning from suspend
I'm seeing this issue for the first time in Ubuntu 19.10 (eoan). Both the screensaver and the power manager have preferences for locking. I see this issue when both are enabled. Under: Screensaver Preferences -> Lock Screen, I see: Enable Lock Screen: Y/N Lock Screen with Screensaver: Y/N Lock the screen after the screensaver is active for ___ minutes Lock Screen with System Sleep: Y/N Under: Xfce Power Manager -> Security, I see: Light Locker: Automatically lock the session: Never/When screensaver is activated/When screensaver is deactivated Delay locking after screensaver for [1 to 61] minutes [Check] Lock screen when system is going to sleep If I disable everything in one of those two places, I don't get the double locking. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1631715 Title: Password required twice returning from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1631715/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: nvidia-settings (Ubuntu Eoan) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu Eoan) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu) Status: New => Fix Released ** Description changed: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: - * New upstream release: - - Added support for the following GPU: - Quadro T2000 with Max-Q Design - - Added support for the __GL_SYNC_DISPLAY_DEVICE environment - variable for Vulkan applications. - - Fixed a bug that caused applications running directly on a - display (such as VR HMDs) to tear when a G-SYNC or G-SYNC - Compatible monitor is plugged in the system. - - Fixed a bug in an error handling path that could cause a kernel - crash while loading nvidia.ko. - - Fixed driver installation failure on Oracle Linux 7.7 systems, - where the NVIDIA kernel module failed to build with error - "unknown type name 'vm_fault_t'". - * Changes from the 440.36 series: + * New upstream release: + - Added support for the following GPU: + Quadro T2000 with Max-Q Design + - Added support for the __GL_SYNC_DISPLAY_DEVICE environment + variable for Vulkan applications. + - Fixed a bug that caused applications running directly on a + display (such as VR HMDs) to tear when a G-SYNC or G-SYNC + Compatible monitor is plugged in the system. + - Fixed a bug in an error handling path that could cause a kernel + crash while loading nvidia.ko. + - Fixed driver installation failure on Oracle Linux 7.7 systems, + where the NVIDIA kernel module failed to build with error + "unknown type name 'vm_fault_t'". + * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
The new crash backtrace: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7fb60370c899 in __GI_abort () at abort.c:79 #2 0x560aacd068c0 in OsAbort () at ../../../../os/utils.c:1351 #3 0x560aacd0c4f9 in AbortServer () at ../../../../os/log.c:879 #4 0x560aacd0d35a in FatalError (f=f@entry=0x560aacd40230 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #5 0x560aacd03c09 in OsSigHandler (unused=, sip=0x7ffd89b28470, signo=11) at ../../../../os/osinit.c:156 #6 OsSigHandler (signo=11, sip=0x7ffd89b28470, unused=) at ../../../../os/osinit.c:110 #7 0x7fb6038ef540 in () at /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x560aacd02cf3 in ResetCurrentRequest (client=client@entry=0x560aae67f0c0) at ../../../../os/io.c:560 #9 0x560aacccfa66 in DRI2WaitSwap (client=0x560aae67f0c0, pDrawable=) at ../../../../../../hw/xfree86/dri2/dri2.c:1082 #10 0x7fb6033fa5f1 in __glXDRIcontextWait (baseContext=, cl=0x560aae67f1d8, error=0x7ffd89b28aa8) at ../../../../glx/glxdri2.c:291 #11 0x7fb6033f29c7 in __glXForceCurrent (cl=0x560aae67f1d8, tag=tag@entry=1, error=error@entry=0x7ffd89b28aa8) at ../../../../glx/glxext.c:621 #12 0x7fb6033ee900 in xorgGlxMakeCurrent (client=0x560aae67f0c0, tag=1, drawId=, readId=0, contextId=, newContextTag=0) at ../../../../glx/glxcmds.c:616 #13 0x560aaccd378a in GlxFreeClientData (client=0x560aae67f0c0) at ../../../../glx/vndext.c:168 #14 0x560aacba838c in _CallCallbacks (pcbl=pcbl@entry=0x560aacdb2538 , call_data=call_data@entry=0x7ffd89b28b50) at ../../../../dix/dixutils.c:743 #15 0x560aacba2273 in CallCallbacks (call_data=0x7ffd89b28b50, pcbl=0x560aacdb2538 ) at ../../../../include/callback.h:83 #16 CloseDownClient (client=0x560aae67f0c0) at ../../../../dix/dispatch.c:3473 #17 0x560aacd045f1 in ospoll_wait (ospoll=0x560aad403a10, timeout=) at ../../../../os/ospoll.c:651 #18 0x560aaccfd3b3 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #19 0x560aacba2ca7 in Dispatch () at ../../../../include/list.h:220 #20 0x560aacba6f94 in dix_main (argc=12, argv=0x7ffd89b299b8, envp=) at ../../../../dix/main.c:276 #21 0x7fb60370e1e3 in __libc_start_main (main=0x560aacb90a00 , argc=12, argv=0x7ffd89b299b8, init=, fini=, rtld_fini=, stack_end=0x7ffd89b299a8) at ../csu/libc-start.c:308 #22 0x560aacb90a3e in _start () -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
There are, thankfully, seemingly no regressions in unrelated areas :-) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
I've built this locally and tested it. While it improves matters, it is still incomplete to get IGLX working fully - there is a new crash at the point you close the IGLX-using application instead of immediately upon starting it. This fix is still warranted, however, because it does improve things. I'm going to go back to bisecting Xorg upstream to see if I can identify the new crash. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1853758] Re: Forcing incompatible Nvidia drivers
Check https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-418/+bug/1838875 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1853758 Title: Forcing incompatible Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1853758/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1853758] Re: Forcing incompatible Nvidia drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1853758 Title: Forcing incompatible Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1853758/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1823758] Re: Release upgrade didn't update nvidia driver
It is false, transitional package are used even while the next branch would make the user unable to use the GPU due to nVidia dropping support for it. Example with 418 and 430. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1823758 Title: Release upgrade didn't update nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1823758/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1827944] Re: Kernel 5.1 is unsupported (and nvidia-418.56 error) [error: initialization of `vm_fault_t (*)(struct vm_fault *)' {aka `unsigned int (*)(struct vm_fault *)'} from inc
Kernel 5.3 officially released by Canonical does not work with 418.56 from this PPA. Branch 430 does not support my GPU. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827944 Title: Kernel 5.1 is unsupported (and nvidia-418.56 error) [error: initialization of `vm_fault_t (*)(struct vm_fault *)' {aka `unsigned int (*)(struct vm_fault *)'} from incompatible pointer type `int (*)(struct vm_fault *)'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827944/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1859105] Re: nvidia-dkms-418 package post-installation script: subprocess returned error exit status 10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1859105 Title: nvidia-dkms-418 package post-installation script: subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1859105/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1853758] Re: Forcing incompatible Nvidia drivers
The problem comes from the 418 package being a transitional package to 430 in the PPA, maintainers not rolling back 418 package to actual driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1853758 Title: Forcing incompatible Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1853758/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1838878] Re: Branch 430 does not support K1100M
Any news on rolling back 418 to it's own branch ? There are updates to the 418 branch that were never released by the ppa : The PPA had the 418.56, while nVidia released the 418.88 version. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1838878 Title: Branch 430 does not support K1100M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1838878/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1838875] Re: nVidia GPU drivers 430 does not support K1100M
Any news on rolling back 418 to it's own branch ? There are updates to the 418 branch that were never released by the ppa : The PPA had the 418.56, while nVidia released the 418.88 version. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1838875 Title: nVidia GPU drivers 430 does not support K1100M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1838875/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp