[Kernel-packages] [Bug 2051298] [NEW] GPU not available in snap
Public bug reported: with 545 the GPU is no longer available to snaps. Try e.g. launching firefox and look at about:support. ** Affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-545 in Ubuntu. https://bugs.launchpad.net/bugs/2051298 Title: GPU not available in snap Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: with 545 the GPU is no longer available to snaps. Try e.g. launching firefox and look at about:support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2051298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored
re-read the initial description. So if I get "[0.00] Secure boot MOKSBState disabled", this is exactly what I want? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571691 Title: linux: MokSBState is ignored Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Ubuntu-4.4.0-20.36 was released with signed module enforcement enabled, but contained no way of disabling secure boot for DKMS. Without these kernel patches it is possible to get your machine in an unbootable state, especially if you don't have a fallback kernel. This patch set implements the ability to disable secure boot on demand from user space (with some password shennaigans). If one boots in secure boot mode and then installs a third party module (such as DKMS), then a dialog is displayed giving the user an option to disable secure boot, thereby also disabling module signature verification. Patch 1/2 is a scaffold patch of which only the GUID macros are actually used. The rest of the code is fenced by CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series. Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3 simply prints a bit more informative state information. Information regarding secure boot and signed module enforcement will appear in the kernel log thusly: 'Secure boot enabled' - normal secure boot operation with signed module enforcement. 'Secure boot MOKSBState disabled' - UEFI Secure boot state has been over-ridden by MOKSBState. No signed module enforcement. In the absense of a 'Secure boot' string assume that secure boot is disabled or does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored
1. asks for a password 2. Setting SB State Failed 3. nothing says I should reboot 4. upon reboot configuration screen pops up and asks random characters from the password entered before 5. allows me to disable verification in case the above is the correct user story, I have the following remark: this seems to disable all verification after shim. Before the change the kernel was still verified and only the the modules were not. Therefore I would say things were more secure before. Is it possible to just disable signed module enforcement again? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571691 Title: linux: MokSBState is ignored Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Ubuntu-4.4.0-20.36 was released with signed module enforcement enabled, but contained no way of disabling secure boot for DKMS. Without these kernel patches it is possible to get your machine in an unbootable state, especially if you don't have a fallback kernel. This patch set implements the ability to disable secure boot on demand from user space (with some password shennaigans). If one boots in secure boot mode and then installs a third party module (such as DKMS), then a dialog is displayed giving the user an option to disable secure boot, thereby also disabling module signature verification. Patch 1/2 is a scaffold patch of which only the GUID macros are actually used. The rest of the code is fenced by CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series. Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3 simply prints a bit more informative state information. Information regarding secure boot and signed module enforcement will appear in the kernel log thusly: 'Secure boot enabled' - normal secure boot operation with signed module enforcement. 'Secure boot MOKSBState disabled' - UEFI Secure boot state has been over-ridden by MOKSBState. No signed module enforcement. In the absense of a 'Secure boot' string assume that secure boot is disabled or does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored
I have issues with this on trusty. The log says "Secure boot enabled" and consequently the nvidia DKMS module can not be loaded. At which point should I have been asked to select the secure boot behavior? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571691 Title: linux: MokSBState is ignored Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Ubuntu-4.4.0-20.36 was released with signed module enforcement enabled, but contained no way of disabling secure boot for DKMS. Without these kernel patches it is possible to get your machine in an unbootable state, especially if you don't have a fallback kernel. This patch set implements the ability to disable secure boot on demand from user space (with some password shennaigans). If one boots in secure boot mode and then installs a third party module (such as DKMS), then a dialog is displayed giving the user an option to disable secure boot, thereby also disabling module signature verification. Patch 1/2 is a scaffold patch of which only the GUID macros are actually used. The rest of the code is fenced by CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series. Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3 simply prints a bit more informative state information. Information regarding secure boot and signed module enforcement will appear in the kernel log thusly: 'Secure boot enabled' - normal secure boot operation with signed module enforcement. 'Secure boot MOKSBState disabled' - UEFI Secure boot state has been over-ridden by MOKSBState. No signed module enforcement. In the absense of a 'Secure boot' string assume that secure boot is disabled or does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1272765] Re: Xbox 360 wireless controller light continues blinking after sync with receiver
try this: https://github.com/paroj/xpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272765 Title: Xbox 360 wireless controller light continues blinking after sync with receiver Status in linux package in Ubuntu: Fix Released Bug description: I'm trying to use an Xbox 360 wireless gamepad with Ubuntu 13.10 64-bit (I've confirmed that this bug affects 14.04 as well). For background, the 360 wireless controller uses a receiver (also made by Microsoft) that plugs into a PC via USB. The controller syncs with the receiver by pressing a button on both. The "xpad" driver in the kernel seems to support most of its functionality just fine, but the light on the controller continues flashing forever after syncing with the receiver. Having a constant blinking light on one's controller is annoying and makes the user experience feel sloppy. As best I can tell, the version of the xpad driver in the mainline kernel hasn't been touched in a few years. Valve, creators of Steam and SteamOS, have done work on the driver recently and have fixed this bug. (Ubuntu PPA for this driver here: https://launchpad.net/~mdeslaur/+archive/steamos ) It would be really nice if 14.04 and all future versions of Ubuntu could use Valve's version of this driver, as it's the version being actively maintained. Without it, gamers trying out Ubuntu will get a low impression of Ubuntu's polish and support for gaming. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpl2694 F pulseaudio /dev/snd/controlC1: jpl2694 F pulseaudio /dev/snd/controlC0: jpl2694 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=d1b7d2f8-4929-4b69-8cc9-ecaa3857fa09 InstallationDate: Installed on 2013-04-28 (272 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=7e9aaad1-2e08-4726-9451-b5a3d38ccc36 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-18 (99 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev root sambashare sudo dmi.bios.date: 01/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd01/17/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1272765] Re: Xbox 360 wireless controller light continues blinking after sync with receiver
use the update xpad driver from SteamOS: https://launchpad.net/~mdeslaur/+archive/ubuntu/steamos -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1272765 Title: Xbox 360 wireless controller light continues blinking after sync with receiver Status in linux package in Ubuntu: Triaged Bug description: I'm trying to use an Xbox 360 wireless gamepad with Ubuntu 13.10 64-bit (I've confirmed that this bug affects 14.04 as well). For background, the 360 wireless controller uses a receiver (also made by Microsoft) that plugs into a PC via USB. The controller syncs with the receiver by pressing a button on both. The xpad driver in the kernel seems to support most of its functionality just fine, but the light on the controller continues flashing forever after syncing with the receiver. Having a constant blinking light on one's controller is annoying and makes the user experience feel sloppy. As best I can tell, the version of the xpad driver in the mainline kernel hasn't been touched in a few years. Valve, creators of Steam and SteamOS, have done work on the driver recently and have fixed this bug. (Ubuntu PPA for this driver here: https://launchpad.net/~mdeslaur/+archive/steamos ) It would be really nice if 14.04 and all future versions of Ubuntu could use Valve's version of this driver, as it's the version being actively maintained. Without it, gamers trying out Ubuntu will get a low impression of Ubuntu's polish and support for gaming. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpl2694 F pulseaudio /dev/snd/controlC1: jpl2694 F pulseaudio /dev/snd/controlC0: jpl2694 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=d1b7d2f8-4929-4b69-8cc9-ecaa3857fa09 InstallationDate: Installed on 2013-04-28 (272 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=7e9aaad1-2e08-4726-9451-b5a3d38ccc36 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-18 (99 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev root sambashare sudo dmi.bios.date: 01/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd01/17/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
