[Group.of.nepali.translators] [Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04
** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu) Importance: Undecided => High ** Also affects: nvidia-settings (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-430 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-430 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-430 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1834603 Title: SRU request: Include the 430 driver in Ubuntu 18.04 Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in nvidia-graphics-drivers-430 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: In Progress Status in nvidia-graphics-drivers-430 source package in Xenial: In Progress Status in nvidia-settings source package in Xenial: In Progress Status in nvidia-graphics-drivers-430 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The nvidia packages in Ubuntu 18.04 do not support recent NVIDIA GPUs. ([10de:2191][10de:1f91][10de:1c91] [Test Case] 1) Enable the bionic-proposed repository, and install the nvidia-430 package 2) Restart and see if the system boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log [Regression Potential] Low, the packages are already in Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1834603/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1819077] Re: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompa
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: Fix Released => Fix Committed ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1819077 Title: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible- pointer-types]) Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] nvidia-340 (from xenial-proposed) breaks compatibility with linux-generic-hwe-16.04. [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update simply re-enables a patch that had been disabled in 340.107-0ubuntu0.16.04.1 _ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.15.0-46-generic Date: Fri Mar 8 01:23:53 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1202 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.107-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev:
[Group.of.nepali.translators] [Bug 1718839] Re: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointe
** No longer affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1718839 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror =incompatible-pointer-types] .fault = _fault,) Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Bug description: After installing new drivers when I restart, it shows crash report. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: nvidia-340 340.104-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 4.13.0-11-generic Date: Thu Sep 21 15:08:42 2017 DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu1:/var/lib/dkms/nvidia-340/340.104/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2017-04-03 (171 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageVersion: 340.104-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc4 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1718839/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1819077] Re: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer
This is not a duplicate, since it was caused by a driver in xenial- proposed that was accepted yesterday. ** This bug is no longer a duplicate of bug 1718839 nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .fault = _fault,) ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1819077 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]) Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Bug description: nvidia-340 (from xenial-proposed) does not work with kernel from linux-generic-hwe-16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.15.0-46-generic Date: Fri Mar 8 01:23:53 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1202 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.107-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 ve
[Group.of.nepali.translators] [Bug 1718839] Re: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointe
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Triaged ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1718839 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror =incompatible-pointer-types] .fault = _fault,) Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Bug description: After installing new drivers when I restart, it shows crash report. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: nvidia-340 340.104-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 4.13.0-11-generic Date: Thu Sep 21 15:08:42 2017 DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu1:/var/lib/dkms/nvidia-340/340.104/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2017-04-03 (171 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageVersion: 340.104-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc4 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1718839/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Confirmed => Triaged ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-361 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-361 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Triaged => Invalid ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Trusty) Status: New => In Progress ** No longer affects: nvidia-graphics-drivers-361 (Ubuntu) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Trusty) Status: In Progress => Invalid ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Xenial) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: In Progress Status in nvidia-graphics-drivers-340 source package in Trusty: In Progress Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: In Progress Status in nvidia-graphics-drivers-304 source package in Xenial: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: In Progress Bug description: NA ProblemType: Package DistroReleas
[Group.of.nepali.translators] [Bug 1771814] Re: NVIDIA CVE-2018-6249 CVE-2018-6253
** Description changed: The 384.130 NVIDIA driver has security fixes for NVIDIA CVE-2018-6249 CVE-2018-6253. + + Here is the PPA with the relevant nvidia packages for 14.04, 16.04, and 17.10: + https://launchpad.net/~albertomilone/+archive/ubuntu/nvidia-security-1 ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1771814 Title: NVIDIA CVE-2018-6249 CVE-2018-6253 Status in nvidia-graphics-drivers-384 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 source package in Trusty: In Progress Status in nvidia-graphics-drivers-384 source package in Xenial: In Progress Status in nvidia-graphics-drivers-384 source package in Artful: In Progress Bug description: The 384.130 NVIDIA driver has security fixes for NVIDIA CVE-2018-6249 CVE-2018-6253. Here is the PPA with the relevant nvidia packages for 14.04, 16.04, and 17.10: https://launchpad.net/~albertomilone/+archive/ubuntu/nvidia-security-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1771814/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1717151] Re: driver installation might not build initramfs then cause dark screen after switching to nvidia
** Also affects: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Zesty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Zesty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Zesty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1717151 Title: driver installation might not build initramfs then cause dark screen after switching to nvidia Status in OEM Priority Project: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-384 source package in Xenial: In Progress Status in nvidia-graphics-drivers-384 source package in Zesty: In Progress Status in nvidia-graphics-drivers-384 source package in Artful: In Progress Bug description: Note: without fix be landed , nvidia driver online update could be failed. nvidia-375.postinst not always build initramfs by default: " ALTERNATIVE=$(readlink /etc/alternatives/x86_64-linux-gnu_gl_conf) if [ "$ALTERNATIVE" = "/usr/lib/nvidia-375/ld.so.conf" ]; then # Update initramfs so that the blacklist ends up in the initramfs if [ -x /usr/sbin/update-initramfs ]; then /usr/sbin/update-initramfs -u " it the case of user who are using intel then update driver from nvidia-375.20 to nvidia-375.82 will get screen dark after prime-select nvidia later. syslog: " NVRM: loading NVIDIA UNIX x86_64 Kernel Module 375.20 Tue Nov 15 16:49:10 PST 2016 (using threaded interrupts) .. NVRM: API mismatch: the client has the version 375.82, but NVRM: this kernel module has the version 375.20. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. " The root cause is the nvidia kernel module in initramfs not be updated in this case. impacted issues: LP: #1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1717151/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1732206] Re: nvidia-graphics-drivers deferred DKMS feature does not work in xenial
** Also affects: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Zesty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Zesty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Zesty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Tags added: argos originate-from-1698183 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1732206 Title: nvidia-graphics-drivers deferred DKMS feature does not work in xenial Status in HWE Next: New Status in nvidia-graphics-drivers-384 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-384 source package in Xenial: In Progress Status in nvidia-graphics-drivers-384 source package in Zesty: In Progress Status in nvidia-graphics-drivers-384 source package in Artful: In Progress Bug description: The nvidia-graphics-drivers (https://github.com/tseliot/nvidia- graphics-drivers/tree/375-xenial) deferred DKMS feature does not work in xenial. With upstart, doing a touch of the /tmp/do_not_build_dkms_module file indicates to defer building the kernel modules, then install the nvidia driver packages, which creates an upstart script to build the modules later. Upon reboot the upstart script would then do the DKMS build. This no longer works in xenial. The code was never updated for the transition from upstart to systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1732206/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1731873] [NEW] Backport amdgpu-pro support
Public bug reported:
SRU Request:
[Impact]
Support for the amdgpu-pro driver has been available in Artful since May 2017.
We need to backport the code to the other stable releases.
[Test Case]
1) Enable the -proposed repository, and install the new "ubuntu-drivers-common"
2) Make sure the amdgpu-pro packages are installed (if not, install
them, and restart your system).
3) Check that power saving mode is supported:
amdgpu-pro-px --ispx
If it returns true, then it is supported by the hardware.
4) Set power saving mode:
sudo amdgpu-pro-px --mode powersaving
5) Restart your computer and check that the "Enabling power saving mode
for amdgpu-pro" line is in your /var/log/gpu-manager.log.
6) Install the mesa-utils package:
sudo apt install mesa-utils
7) Check the output of the following command (which should mention Intel):
glxinfo | grep OpenGL
[Regression Potential]
Low, as the feature is disabled by default, unless users set power saving
manually.
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: Fix Released
** Affects: ubuntu-drivers-common (Ubuntu Xenial)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Affects: ubuntu-drivers-common (Ubuntu Zesty)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Also affects: ubuntu-drivers-common (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Zesty)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Zesty)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Zesty)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1731873
Title:
Backport amdgpu-pro support
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Xenial:
In Progress
Status in ubuntu-drivers-common source package in Zesty:
In Progress
Bug description:
SRU Request:
[Impact]
Support for the amdgpu-pro driver has been available in Artful since May
2017. We need to backport the code to the other stable releases.
[Test Case]
1) Enable the -proposed repository, and install the new
"ubuntu-drivers-common"
2) Make sure the amdgpu-pro packages are installed (if not, install
them, and restart your system).
3) Check that power saving mode is supported:
amdgpu-pro-px --ispx
If it returns true, then it is supported by the hardware.
4) Set power saving mode:
sudo amdgpu-pro-px --mode powersaving
5) Restart your computer and check that the "Enabling power saving
mode for amdgpu-pro" line is in your /var/log/gpu-manager.log.
6) Install the mesa-utils package:
sudo apt install mesa-utils
7) Check the output of the following command (which should mention Intel):
glxinfo | grep OpenGL
[Regression Potential]
Low, as the feature is disabled by default, unless users set power saving
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1731873/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode
I forgot to mention the package in artful-proposed. ** Also affects: ubuntu-drivers-common (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Artful) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Artful) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Artful) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1728547 Title: SRU: Add support for keeping the dGPU on in power saving mode Status in HWE Next: New Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Xenial: In Progress Status in ubuntu-drivers-common source package in Zesty: In Progress Status in ubuntu-drivers-common source package in Artful: In Progress Bug description: SRU Request: [Impact] Some systems don't play well when the dGPU is disabled. It should still be possible to use the Intel iGPU without disabling the dGPU. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the nvidia packages are installed, and enable power saving mode: sudo prime-select intel 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Install the mesa-utils package: sudo apt install mesa-utils 5) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default. This is only for hardware specific workarounds. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
** Also affects: ubuntu-drivers-common (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Zesty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Zesty) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Zesty) Importance: Undecided => Critical -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia Status in HWE Next: Incomplete Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Incomplete Status in ubuntu-drivers-common source package in Zesty: In Progress Bug description: SRU Request: [Impact] Different GPUs may require different options in the xorg.conf file. Currently this is not possible, since the options have been hardcoded in gpu-manager to configure the system automatically. This new (backported) feature allows users to tell gpu-manager to use their own custom xorg.confs for their NVIDIA GPUs. [Test Case] 1) Enable the xenial-proposed repository, and install the ubuntu-drivers-common and the nvidia-prime packages. 2) Install the nvidia driver. 3) Place your configuration file(s) in the /usr/share/gpu-manager.d directory. If you are using a non-hybrid system, you can create the /usr/share /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share /gpu-manager.d/hybrid-power-saving, depending on the power profile you intend to apply your settings to. 4) Restart the system and see if it boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log 5) Make sure that the /etc/X11/xorg.conf matches the file you specified in 3) [Regression Potential] Low, the above mentioned changes are already in Artful, and will not affect the system's behaviour unless new configuration files are put in the /usr/share/gpu-manager.d/ directory. __ This feature has been implemented for Intel (ex. gpumanager_uxa), which is parsing kernel parameter to add option in xorg.conf (commit ff3a4e54). And now Nvidia also need this feature to add Option "nvidiaXineramaInfo" "off" to fix some issues. Btw, I'm thinking it might be a more flexible to have a config file which user could add all options as they want so that we could prevent keeping change gpu-manager when some more options are needed in the future. Needed by LP: #1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1667198] Re: gpu-manager should also support reading kernel parameter to adding options in xorg.conf for Nvidia
** Also affects: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support reading kernel parameter to adding options in xorg.conf for Nvidia Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: In Progress Bug description: This feature has been implemented for Intel (ex. gpumanager_uxa), which is parsing kernel parameter to add option in xorg.conf (commit ff3a4e54). And now Nvidia also need this feature to add Option "nvidiaXineramaInfo" "off" to fix some issues. Btw, I'm thinking it might be a more flexible to have a config file which user could add all options as they want so that we could prevent keeping change gpu-manager when some more options are needed in the future. needed by : lp#1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1667198/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers
** Also affects: nvidia-graphics-drivers-375 (Ubuntu) Importance: Undecided Status: New ** No longer affects: nvidia-drivers-ubuntu ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers Status in gdm: Unknown Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-375 package in Ubuntu: Triaged Status in gnome-shell source package in Xenial: Triaged Status in gnome-shell source package in Yakkety: Triaged Status in nvidia-graphics-drivers-375 source package in Yakkety: New Bug description: To fix this now without waiting for the Stable Release Update = Install xserver-xorg-legacy Impact == Many users are unable to use their computers after installing the NVIDIA proprietary drivers to Ubuntu GNOME. Specifically, the log in screen does not load. The problem is that many of nvidia-* driver packages do not depend on xserver-xorg-legacy which is needed for gdm/gnome-shell to work Test Case = 1. Check that gnome-shell depends on xserver-xorg-legacy. 2. Optionally, if you have an affected computer, set gdm as the default login manager (sudo apt install gdm3; sudo dpkg-reconfigure gdm3; sudo reboot). Does the login screen show up? And can you log in to gnome (sudo apt install gnome-shell)? Regression Potential Low. Installing a missing dependency should cause no issues; if it does, something is very broken already. Other Info == The most minimal fix here for 16.04 LTS and 16.10 is to just have gnome-shell depend on xserver-xorg-legacy. Updating all the nvidia-* packages in Ubuntu and the PPAs would be a lot more trouble; although that would still be a good idea so that this gnome-shell dependency could be dropped in future Ubuntu releases. xserver-xorg-legacy is a very small package. gdm3 depends on gnome-shell. Original Bug Report === Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.n
[Group.of.nepali.translators] [Bug 1677327] Re: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1677327 Title: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Bug description: ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz We need to backport build fixes for 4.9/4.10 kernels. /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function ‘os_lock_user_pages’: /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast [-Wint-conversion] page_count, write ? FOLL_WRITE : 0, user_pages, NULL); ^ In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0: /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected ‘int’ but argument is of type ‘struct page **’ static inline long NV_GET_USER_PAGES(unsigned long start, ^ /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few arguments to function ‘NV_GET_USER_PAGES’ ret = NV_GET_USER_PAGES((unsigned long)address, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1677327/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1647036] Re: Client does not ACK auth/assoc responses from Cisco AP3800
** Also affects: bcmwl (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: bcmwl (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu) Status: Triaged => In Progress ** Changed in: bcmwl (Ubuntu Trusty) Status: New => Triaged ** Changed in: bcmwl (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1647036 Title: Client does not ACK auth/assoc responses from Cisco AP3800 Status in bcmwl package in Ubuntu: In Progress Status in bcmwl source package in Trusty: Triaged Status in bcmwl source package in Xenial: Triaged Bug description: This client does not ACK Assoc Responses from a Cisco 3800. Traces attached. - Model:Dell XPS13 9343 - OS Version:Ubuntu 14.04.5 LTS - WNIC:Broadcom BCM4352 rev. 03 driver version 6.30.223.248 - SSID:user.wifi (WPA2/dot1x ) - MAC address:c4:8e:8f:f5:4a:7f -Cisco AP : 3800 (wave 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1647036/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1615058] Re: gpu-manager fails to unload NVIDIA modules
** Also affects: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => Fix Released ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1615058 Title: gpu-manager fails to unload NVIDIA modules Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Triaged Bug description: I am using Ubuntu 16.04.1 LTS on a Clevo P65XSE-A with a Intel HD 5500 (I think!?) and a GTX 970m When using a new NVIDIA driver from the graphics ppa https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa I noticed when switching back to the Intel card via "sudo prime-select intel", the NVIDIA card stays on. When launching gpu-manager via terminal it tells me it can't unload nvidia_modeset and nvidia_drm modules. Should probably use libkmod2 like bumblebee https://github.com/Bumblebee-Project/Bumblebee/pull/762 Unloading nvidia-uvm with "no" parameters rmmod: ERROR: Module nvidia_uvm is not currently loaded Unloading nvidia-modeset with "no" parameters rmmod: ERROR: Module nvidia_modeset is in use by: nvidia_drm Unloading nvidia with "no" parameters rmmod: ERROR: Module nvidia is in use by: nvidia_modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1615058/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1582439] Re: nvidia-prime depends upon gdm instead of gdm3
** Also affects: nvidia-prime (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-prime (Ubuntu Xenial) Status: New => Triaged ** Changed in: nvidia-prime (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: nvidia-prime (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1582439 Title: nvidia-prime depends upon gdm instead of gdm3 Status in Ubuntu GNOME: Triaged Status in nvidia-prime package in Ubuntu: Triaged Status in nvidia-prime source package in Xenial: Triaged Bug description: https://github.com/tseliot/nvidia-prime/pull/4 [Impact] - Triaged as High for its impact on Ubuntu GNOME. - Users who install nvidia-prime currently will get lightdm installed, which triggers a nasty debconf prompt asking them to choose whether to use lightdm or gdm3. - However, there is no explanation given about what are the advantages or disadvantages of each choice. (For instance, GNOME Shell does not integrate as well with lightdm; I'm guessing Unity has a similar issue with gdm3). Users may easily not know which one is installed by default on their system or which is recommended in their situation. [Test Case] 1. From Ubuntu GNOME 16.04 LTS, install nividia-prime 2. Is lightdm installed? Are you asked to choose which display manager to use? [Regression Potential] None, this simply adds gdm3 as a supported alternative dependency. [Original Report] Trying to install nvidia-prime on an ubuntu-gnome system tries to pull in a bunch of unity stuff, because it lists as dependencies: Depends: lightdm (>= 1.9.1) | gdm | kdm | sddm, bbswitch-dkms, pciutils, lsb-release, lsb-base (>= 4.1+Debian11ubuntu7) It should depend on gdm3 in addition, since gdm is a transitional package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-prime (not installed) Uname: Linux 4.5.4-040504-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 16 19:17:25 2016 InstallationDate: Installed on 2016-05-15 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1582439/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia
I spoke with Michael, and we are going to reject the patch for the nvidia packages in xenial-proposed (already reverted in Yakkety), as he has a better plan now (so that we don't run into LP: #1589006). For this reason I am closing the tasks for the nvidia drivers for now. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Fix Released => Invalid ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: Fix Committed => Invalid ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: Fix Released => Invalid ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Xenial) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1588192 Title: GL interfaces seem wedged for Krita on nvidia Status in Snappy: In Progress Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-361 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Xenial: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: Invalid Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Bug description: Krita snap segfaults. I'm running nvidia proprietary drivers on Dell XPS 15. mark@mark-XPS-15-9550:~$ snap install krita 97.84 MB / 97.84 MB [=] 100.00 % 362.82 KB/s Name Version Rev Developer krita 3.0-snap10 1krita mark@mark-XPS-15-9550:~$ krita QCoreApplication::arguments: Please instantiate the QApplication object first krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl krita.lib.pigment: Features supported: krita.lib.pigment: "SSE2" --- yes krita.lib.pigment: "SSSE3"--- yes krita.lib.pigment: "SSE4.1" --- yes krita.lib.pigment: "AVX " --- yes libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Segmentation fault (core dumped) mark@mark-XPS-15-9550:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1588192/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1589520] [NEW] Add dconf keys for disabling multitouch gestures
Public bug reported: Not an actual solution to LP: #1264795 (which should probably be fixed in the driver), but a simply way for users to disable gestures in dconf. ** Affects: unity (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: unity (Ubuntu Xenial) Importance: Medium Status: Triaged ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Also affects: unity (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Xenial) Status: New => Incomplete ** Changed in: unity (Ubuntu Xenial) Status: Incomplete => Triaged ** Changed in: unity (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1589520 Title: Add dconf keys for disabling multitouch gestures Status in unity package in Ubuntu: In Progress Status in unity source package in Xenial: Triaged Bug description: Not an actual solution to LP: #1264795 (which should probably be fixed in the driver), but a simply way for users to disable gestures in dconf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1589520/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia
** Changed in: nvidia-graphics-drivers-361 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-361 (Ubuntu Xenial)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided => Critical
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => Critical
** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1588192
Title:
GL interfaces seem wedged for Krita on nvidia
Status in Snappy:
In Progress
Status in nvidia-graphics-drivers-304 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-361 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
In Progress
Status in nvidia-graphics-drivers-361 source package in Xenial:
In Progress
Bug description:
Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
XPS 15.
mark@mark-XPS-15-9550:~$ snap install krita
97.84 MB / 97.84 MB
[=]
100.00 % 362.82 KB/s
Name Version Rev Developer
krita 3.0-snap10 1krita
mark@mark-XPS-15-9550:~$ krita
QCoreApplication::arguments: Please instantiate the QApplication object first
krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
krita.lib.pigment: Features supported:
krita.lib.pigment: "SSE2" --- yes
krita.lib.pigment: "SSSE3"--- yes
krita.lib.pigment: "SSE4.1" --- yes
krita.lib.pigment: "AVX " --- yes
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Segmentation fault (core dumped)
mark@mark-XPS-15-9550:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1588192/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1586933] Re: gpu-manager's drm output detection affects boot time
** Also affects: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1586933 Title: gpu-manager's drm output detection affects boot time Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Xenial: In Progress Bug description: Rather than calling drm directly, gpu-manager should simply check the outputs connector status by using the sysfs filesystem (e.g. /sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that is already available. This should make gpu-manager a bit less resource intensive, especially on boot. The attached perf shows the problem in gpu-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1586933/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package
** Also affects: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1320868 Title: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Xenial: Triaged Bug description: $sudo apt-get remove nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done Package 'nvidia-current' is not installed, so not removed The following package was automatically installed and is no longer required: linux-image-generic Use 'apt-get autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up nvidia-331 (331.38-0ubuntu7) ... INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Traceback (most recent call last): File "/usr/bin/quirks-handler", line 65, in operation_status = main(options) File "/usr/bin/quirks-handler", line 44, in main quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, path=quirks_path) File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in __init__ self._system_info = self.get_system_info() File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in get_system_info return quirk_info.get_dmi_info() File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in get_dmi_info 'class', 'dmi', 'id', item)).read().strip() File "/usr/lib/python3.4/codecs.py", line 313, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte dpkg: error processing package nvidia-331 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nvidia-331 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1575960] Re: gpu-manager: get_alternative_link() NEVER checks for a correct alternative
** Also affects: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Critical => High ** Changed in: ubuntu-drivers-common (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1575960 Title: gpu-manager: get_alternative_link() NEVER checks for a correct alternative Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Xenial: In Progress Bug description: I suppose this is a fairly significant bug, since it renders gpu-manager virtually useless. I found it in ubuntu-drivers-common 0.4.17 (which is the current version in Ubuntu 16.04), and I do not know whether it is also present in other versions. -- Symptoms -- For some reason, on my machine I frequently insert and remove my nvidia graphics adapter. My processor has an intel HD graphics adapter as well, so I rely on gpu-manager to detect my hardware configuration during boot, and update alternatives appropriately. However, since I upgraded to Ubuntu 16.04, reconfiguring my hardware makes me unable to boot to desktop. However, reverting to previous hardware configuration solves the issue. -- Analysis and proposed solution -- A quick check of symbolic links at /etc/ld.so.conf.d/x86_64-linux- gnu_GL.conf and similar confirms that when I change my hardware configuration, no changes are done to the targets of these links. Reading through gpu-manager.log I can see that it detects my hardware correctly, but it fails to configure alternatives, because: Error: no alternative found for nvidia Warning: no EGL alternative found for nvidia Further investigation shows that the problem is with the get_alternative_link() function, as it always returns NULL, regardless of my current hardware configuration, and function arguments. The get_alternative_link() function works by querying the list of available alternatives by running `update-alternatives` command with `--list` argument. The command is prepared by: snprintf(command, sizeof(command), "update-alternatives --list %s_%s_conf", alternative_pattern, arch_path); For example, when looking for "gl" alternatives for architecture "x86_64-linux-gnu", the resulting command will be: update-alternatives --list gl_x86_64-linux-gnu_conf This command always returns an empty list, and that is correct. The command is clearly malformed, the intention was to run another command, namely: update-alternatives --list x86_64-linux-gnu_gl_conf (note the order of "gl" vs "x86_64_linux_gnu") Indeed the `snprintf` used to prepare the command has it's arguments swapped. Therefore I propose to substitute the mentioned source code with: snprintf(command, sizeof(command), "update-alternatives --list %s_%s_conf", arch_path, alternative_pattern); Applying the proposed change reliably fixes the bug symptoms I experienced. -- Additional comment -- For your convenience, I attached to this bug report a patch file that applies the proposed solution; the patch is intended for ubuntu-drivers-common 0.4.17 source. As far as I can tell, due to these swapped arguments gpu-manager always looks for unexisting alternatives, and therefore there is no scenario in which it would correctly configure alternatives. I suppose in this case gpu-manager always fails to serve its purpose. I find it astonishing that nobody noticed this issue yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1575960/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
