[Kernel-packages] [Bug 1826461] Re: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.
** Changed in: modem-manager-gui (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Incomplete Status in modem-manager-gui package in Ubuntu: Incomplete Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+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 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series
Please update nvidia-settings in Bionic as well, so that users can adjust settings of the new features in the 430 / 435 drivers. e.g. G-SYNC ** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1844126 Title: Update NVIDIA the 430 series and introduce the 435 series Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: New Status in nvidia-graphics-drivers-430 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-435 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: New Bug description: Update NVIDIA the 430 series and introduce the 435 series from 19.10. [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] 430.50: * New upstream release (LP: #1844126): - Fixed display color range handling on pre-Turing GPUs, such that when limited color range is selected through the display controls page in nvidia-settings, output pixel values will be correctly clamped to Consumer Technology Association (CTA) range. 435.21: * New upstream release: - Fixed a bug that caused the X server to crash when using HardDPMS with an NVIDIA-driven GPU Screen. - Fixed a bug which caused the kernel to panic when exiting a single X server when multiple X servers were active and in an SLI configuration. - Fixed a regression introduced in the 430.* series of releases that caused a segmentation fault in libnvcuvid.so while using Video Codec SDK APIs on certain graphics boards. - Added initial experimental support for runtime D3 (RTD3) power management on Turing notebook GPUs. - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3) power management information. - Improved nvidia-bug-report.sh to collect ACPI tables when the acpidump tool is available. - Added Vulkan and OpenGL+GLX support for PRIME render offload. Please see the PRIME Render Offload chapter in the README for system requirements and configuration details. - Added support for changing Digital Vibrance in the display controls section of nvidia-settings on Turing hardware. - Fixed the cuvidParseVideoData API in the NVCUVID driver to correctly propagate errors returned by the PFNVIDSEQUENCECALLBACK callback function to the application. - Fixed a bug that caused the NVIDIA X driver to behave incorrectly or crash when a client queried Xinerama information on X servers with a non-NVIDIA X screen as screen 0. - Fixed the "Image Settings" options in the "OpenGL Settings" page of nvidia-settings for Quadro GPUs. Previously, OpenGL rendering on Quadro would behave as if the "High Quality" option were selected regardless of the selection. Now, the setting will default to "High Quality" for Quadro but selecting a lower option will affect rendering accordingly. (Other GPUs are unchanged: the default remains "Quality", but other options can be selected if desired.) - Fixed a bug that could cause Vulkan applications to generate spurious warning messages about a missing NV-GLX extension. - Fixed a bug that prevented nvidia-drm from marking preferred modes properly when reporting display information via the DRM- KMS API. - Fixed the NvEncodeAPI driver to correctly reject the encoding of sequences with resolutions smaller than what the NVENC supports. - Fixed display color range handling on pre-Turing GPUs, such that when limited color range is selected through the display controls page in nvidia-settings, output pixel values will be correctly clamped to Consumer Technology Association (CTA)
[Kernel-packages] [Bug 1736617] Re: Port nvidia-settings to gtk3
PR: https://github.com/tseliot/nvidia-settings/pull/4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1736617 Title: Port nvidia-settings to gtk3 Status in nvidia-settings package in Ubuntu: New Bug description: gtk3 was declared stable in September 2016 with the gtk 3.22 release. nvidia-settings should switch to gtk3. nvidia-settings is one of the last dozen packages to keep gtk2 in main. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gtk2-demotion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1736617/+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 1690669] Re: Please build libxnvctrl0/-dev for s390x
PR: https://github.com/tseliot/nvidia-settings/pull/2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1690669 Title: Please build libxnvctrl0/-dev for s390x Status in nvidia-settings package in Ubuntu: New Bug description: The Debian version of this package is built for all architectures: https://buildd.debian.org/status/package.php?p=nvidia-settings Please do the same for Ubuntu also. In particular, qtwebengine-opensource-src needs libxnvctrl-dev (which depends on libxnvctrl0) to build on s390x. qtwebengine in turned is needed for the KDE PIM components (and probably other parts of the KDE platfrom). https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.7.1 +dfsg-6build1/+build/12459543 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1690669/+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 1630063] Re: specific USB devices disconnect and don't reconnect
With the 4.8.0-30.32 kernel I have been able to print a page, but attempting to scan results in my mouse dying. -- 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/1630063 Title: specific USB devices disconnect and don't reconnect Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 2 USB ports randomly disconnect and don't reconnect (it's always the same two), and in dmesg all I get is " [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up [ 1276.916553] usb 3-1: USB disconnect, device number 2 [ 1277.017302] usb 3-2: USB disconnect, device number 3 " This only started happening when Yakkety went to the 4.8 branch, with 4.7 branch this doesn't occur, hence the bug report since it's unlikely that a hardware failure will only stick to one OS and one branch of the kernel for that OS. (these USB ports don't randomly die on Windows or BSD, I've tested that in the past couple of days) kernel version: 4.8.0.17.27 Ubuntu version Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: c_smith2213 F pulseaudio /dev/snd/controlC0: c_smith2213 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b InstallationDate: Installed on 2016-10-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630063/+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 1630063] Re: specific USB devices disconnect and don't reconnect
Testing again now with the 4.8.0-30.32 kernel, I have been able to scan a page and listen to several minutes of YouTube audio over USB headphones. -- 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/1630063 Title: specific USB devices disconnect and don't reconnect Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 2 USB ports randomly disconnect and don't reconnect (it's always the same two), and in dmesg all I get is " [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up [ 1276.916553] usb 3-1: USB disconnect, device number 2 [ 1277.017302] usb 3-2: USB disconnect, device number 3 " This only started happening when Yakkety went to the 4.8 branch, with 4.7 branch this doesn't occur, hence the bug report since it's unlikely that a hardware failure will only stick to one OS and one branch of the kernel for that OS. (these USB ports don't randomly die on Windows or BSD, I've tested that in the past couple of days) kernel version: 4.8.0.17.27 Ubuntu version Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: c_smith2213 F pulseaudio /dev/snd/controlC0: c_smith2213 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b InstallationDate: Installed on 2016-10-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630063/+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 1327753] Re: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev
** Changed in: hwloc-contrib (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1327753 Title: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev Status in hwloc-contrib package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Bug description: Hwloc-contrib 1.9-1 currently fails to build because it depends on libxnvctrl-dev which is not available. Package libxnvctrl-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: nvidia-settings E: Package 'libxnvctrl-dev' has no installation candidate apt-get failed. For more details, see https://launchpadlibrarian.net/173944551/buildlog_ubuntu-utopic-i386.hwloc-contrib_1.9-1_MANUALDEPWAIT.txt.gz In Debian, libxnvctrl-dev is part of the nvidia-settings package (http://packages.qa.debian.org/n/nvidia-settings.html). However, this is not synced since Ubuntu has its own nvidia-settings package (https://launchpad.net/ubuntu/+source/nvidia-settings), though that does not offer the binary package which hwloc-contrib needs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwloc-contrib/+bug/1327753/+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 1327753] Re: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev
I had a go at merging the changes from 343.22-1 in Debian experimental. The result is available in my PPA: https://launchpad.net/~ginggs/+archive/ubuntu/arm-testing and the debdiff is attached. The armhf build runs fine on an NVIDIA Jetson TK1 board. Moving forward, I think it would be easier to maintain if we started with the Debian packaging (I think it can be used with only minor changes to debian/control) and then merged in the Ubuntu patches. Upstream have released version 346.47 and I can look at updating the Debian package to that version. Is there still time to get this into Vivid? ** Patch added: "nvidia-settings_346.35-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwloc-contrib/+bug/1327753/+attachment/4337004/+files/nvidia-settings_346.35-0ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1327753 Title: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev Status in hwloc-contrib package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Bug description: Hwloc-contrib 1.9-1 currently fails to build because it depends on libxnvctrl-dev which is not available. Package libxnvctrl-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: nvidia-settings E: Package 'libxnvctrl-dev' has no installation candidate apt-get failed. For more details, see https://launchpadlibrarian.net/173944551/buildlog_ubuntu-utopic-i386.hwloc-contrib_1.9-1_MANUALDEPWAIT.txt.gz In Debian, libxnvctrl-dev is part of the nvidia-settings package (http://packages.qa.debian.org/n/nvidia-settings.html). However, this is not synced since Ubuntu has its own nvidia-settings package (https://launchpad.net/ubuntu/+source/nvidia-settings), though that does not offer the binary package which hwloc-contrib needs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwloc-contrib/+bug/1327753/+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 1429974] Re: Outdated/wrong copyright/license data
I'll add a new debdiff to LP: #1327753 and merge in debian/copyright from the Debian packaging. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1429974 Title: Outdated/wrong copyright/license data Status in nvidia-settings package in Ubuntu: Confirmed Bug description: The nvidia-settings package has a significant problem with the copyright file. It is either significantly out of date or plain wrong, neglecting a variety of files that have different licenses from the main binary. This is most significant in the portion of the package that provides libXNVCtrl, which is licensed under the Expat license (and therefore compatible with LGPL projects). The current license data implies that it is GPL-only, which would present a problem for LGPL projects. For reference, the upstream Debian package has this covered: http://metadata.ftp-master.debian.org/changelogs//main/n/nvidia-settings/nvidia-settings_340.46-2_copyright Ideally the libXNVCtrl library would be split into a separate package (like it is on Debian), but at the very least the copyright/license data should be corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1429974/+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 1327753] Re: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev
I'll attach an updated debdiff soon including a merge of debian/copyright from the Debian packaging. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1327753 Title: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev Status in hwloc-contrib package in Ubuntu: Confirmed Status in nvidia-settings package in Ubuntu: Confirmed Bug description: Hwloc-contrib 1.9-1 currently fails to build because it depends on libxnvctrl-dev which is not available. Package libxnvctrl-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: nvidia-settings E: Package 'libxnvctrl-dev' has no installation candidate apt-get failed. For more details, see https://launchpadlibrarian.net/173944551/buildlog_ubuntu-utopic-i386.hwloc-contrib_1.9-1_MANUALDEPWAIT.txt.gz In Debian, libxnvctrl-dev is part of the nvidia-settings package (http://packages.qa.debian.org/n/nvidia-settings.html). However, this is not synced since Ubuntu has its own nvidia-settings package (https://launchpad.net/ubuntu/+source/nvidia-settings), though that does not offer the binary package which hwloc-contrib needs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwloc-contrib/+bug/1327753/+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 1327753] Re: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev
Updated debdiff attached with the following changes: Merge debian/copyright from 343.22-1 in Debian experimental, add Ubuntu contributors, update copyright years. Remove debian/dirs which was renamed to debian/nvidia-settings.dirs in the previous debdiff. Remove extra empty and commented out lines from debian/patches/series and debian/rules. ** Patch added: "nvidia-settings_346.35-0ubuntu2-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwloc-contrib/+bug/1327753/+attachment/4340888/+files/nvidia-settings_346.35-0ubuntu2-v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1327753 Title: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev Status in hwloc-contrib package in Ubuntu: Confirmed Status in nvidia-settings package in Ubuntu: Confirmed Bug description: Hwloc-contrib 1.9-1 currently fails to build because it depends on libxnvctrl-dev which is not available. Package libxnvctrl-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: nvidia-settings E: Package 'libxnvctrl-dev' has no installation candidate apt-get failed. For more details, see https://launchpadlibrarian.net/173944551/buildlog_ubuntu-utopic-i386.hwloc-contrib_1.9-1_MANUALDEPWAIT.txt.gz In Debian, libxnvctrl-dev is part of the nvidia-settings package (http://packages.qa.debian.org/n/nvidia-settings.html). However, this is not synced since Ubuntu has its own nvidia-settings package (https://launchpad.net/ubuntu/+source/nvidia-settings), though that does not offer the binary package which hwloc-contrib needs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwloc-contrib/+bug/1327753/+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 1634737] Re: ohci-pci: frame counter not updating; disabled
*** This bug is a duplicate of bug 1630063 *** https://bugs.launchpad.net/bugs/1630063 ** This bug has been marked a duplicate of bug 1630063 specific USB devices disconnect and don't reconnect -- 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/1634737 Title: ohci-pci: frame counter not updating; disabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: I've been running Ubuntu 16.04 inside a VirtualBox (version 5.1.6 r110634 (Qt5.5.1)) running on Windows 10 Home (version 1607 os build 14393.321) host without any incident until I upgraded to Ubuntu 16.10. I have a USB to Serial converter (pl2303) connected to a development board that is handled by the Ubuntu Linux Kernel. After upgrading to Ubuntu 16.10 the ohci-hcd driver reported that the "frame counter not updated; disabled" followed by "HC died; cleaning up" which would kill my terminal application (kermit) that was connected to the pl2303 device. When the issue was first noticed, I rebooted the Linux virtual machine and booted the previous kernel (4.4.0-43-generic) and was able to use the pl2303 to communicate to my development board just fine. I switched back to the 4.8.0-22-generic kernel and the ohci-hcd driver reported the same problem. I looked at the differences between the ohci-hcd.c and pl2303.[ch] drivers between 4.9-rc1 and the 4.4.0 linux kernels and the pl2303.[ch] files didn't have any changes, and only a couple of changes were made to ohci-hcd.c but nothing that would indicate an issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Tue Oct 18 22:30:12 2016 HibernationDevice: RESUME=/dev/mapper/cartman--vg-swap_1 InstallationDate: Installed on 2014-08-02 (808 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/hostname--vg-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-15 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2014-08-02 (810 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: yakkety Uname: Linux 4.9.0-040900rc1-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to yakkety on 2016-10-15 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo users vboxsf _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1635012] Re: Usb wireless mouse gets disconnected randomly in Ubuntu 16.10
*** This bug is a duplicate of bug 1630063 *** https://bugs.launchpad.net/bugs/1630063 ** This bug has been marked a duplicate of bug 1630063 specific USB devices disconnect and don't reconnect -- 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/1635012 Title: Usb wireless mouse gets disconnected randomly in Ubuntu 16.10 Status in linux package in Ubuntu: Confirmed Bug description: This happens frequently just after making a clean install of Ubuntu 16.10, I never had this issue with Ubuntu 16.04 LTS with the same device. The only error message in dmesg is this: [ 713.796447] usb 5-2: USB disconnect, device number 2 [ 727.415529] usb 5-2: new full-speed USB device number 3 using ohci-pci [ 727.602758] usb 5-2: New USB device found, idVendor=0458, idProduct=0185 [ 727.602765] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 727.602769] usb 5-2: Product: Wireless Mouse [ 727.602773] usb 5-2: Manufacturer: MOSART Semi. [ 727.612028] hid-generic 0003:0458:0185.0003: hiddev0,hidraw0: USB HID v1.10 Device [MOSART Semi. Wireless Mouse] on usb-:00:13.0-2/input0 [ 727.617768] input: MOSART Semi. Wireless Mouse as /devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/0003:0458:0185.0004/input/input14 [ 727.676316] hid-generic 0003:0458:0185.0004: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. Wireless Mouse] on usb-:00:13.0-2/input1 [ 6113.408175] ohci-pci :00:13.0: frame counter not updating; disabled [ 6113.408190] ohci-pci :00:13.0: HC died; cleaning up [ 6113.408364] usb 5-2: USB disconnect, device number 3 My laptop is a HP Pavilion dv7-4061nr DistroRelease: Ubuntu 16.10 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 18:26:36 2016 InstallationDate: Installed on 2016-10-18 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kike 2148 F pulseaudio /dev/snd/controlC1: kike 2148 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=5bbfb5db-57eb-4bd5-a584-98aa50218bed InstallationDate: Installed on 2016-10-18 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Package: linux (not installed) ProcEnviron: LANGUAGE=es_AR:es TERM=xterm-256color PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=9a0d0769-6d64-49b8-901a-a8185747d073 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/25/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1442 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr048D10242B202:rvnHewlett-Packard:rn1442:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 048D10242B202 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-10-18 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: linux (not installed) Tags: yakkety Uname: Linux 4.9.0-040900rc1-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin pl
[Kernel-packages] [Bug 1630063] Re: specific USB devices disconnect and don't reconnect
Looks like it was accepted here: https://github.com/torvalds/linux/commit/ed6d6f8f42d7302f6f9b6245f34927ec20d26c12 We still need this to go into the yakkety 4.8 kernel. -- 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/1630063 Title: specific USB devices disconnect and don't reconnect Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 2 USB ports randomly disconnect and don't reconnect (it's always the same two), and in dmesg all I get is " [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up [ 1276.916553] usb 3-1: USB disconnect, device number 2 [ 1277.017302] usb 3-2: USB disconnect, device number 3 " This only started happening when Yakkety went to the 4.8 branch, with 4.7 branch this doesn't occur, hence the bug report since it's unlikely that a hardware failure will only stick to one OS and one branch of the kernel for that OS. (these USB ports don't randomly die on Windows or BSD, I've tested that in the past couple of days) kernel version: 4.8.0.17.27 Ubuntu version Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: c_smith2213 F pulseaudio /dev/snd/controlC0: c_smith2213 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b InstallationDate: Installed on 2016-10-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630063/+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 763457] Re: please provide opencl-icd virtual package
@arvindsraj: what is that you want backported to 12.04? pyopencl in 12.04 does not depend on opencl-icd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-common in Ubuntu. https://bugs.launchpad.net/bugs/763457 Title: please provide opencl-icd virtual package Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “nvidia-common” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “fglrx-installer” source package in Quantal: Won't Fix Status in “nvidia-common” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers-304” source package in Quantal: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Quantal: Confirmed Status in “nvidia-graphics-drivers-319” source package in Quantal: Confirmed Status in “nvidia-graphics-drivers-319-updates” source package in Quantal: Confirmed Status in “pyopencl” source package in Quantal: Fix Released Status in “pyopencl” package in Debian: Fix Released Bug description: The package python-pyopencl depends on nvidia-current, which makes it impossible to correctly use on AMD / ATI systems. In debbugs #628702 debian started using a virtual package opencl-icd instead of depending directly on particular graphics driver / opencl implementation. We should follow the same. TODO * syn pyopencl * nvidia-graphics-drivers or nvidia-common (not sure) to provide opencl-icd * fglrx-installer to provide opencl-icd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/763457/+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 763457] Re: please provide opencl-icd virtual package
Yes, I see the problem. To fix this for AMD, we would first need to get fglrx-installer fixed in Saucy, then back port that for Precise. For Intel I think we would need to backport the beignet package, and it would be good if ocl-icd could be backported as well. Ask someone in #ubuntu-bugs on IRC if they can create the Precise tasks for these packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-common in Ubuntu. https://bugs.launchpad.net/bugs/763457 Title: please provide opencl-icd virtual package Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “nvidia-common” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “fglrx-installer” source package in Quantal: Won't Fix Status in “nvidia-common” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers-304” source package in Quantal: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Quantal: Confirmed Status in “nvidia-graphics-drivers-319” source package in Quantal: Confirmed Status in “nvidia-graphics-drivers-319-updates” source package in Quantal: Confirmed Status in “pyopencl” source package in Quantal: Fix Released Status in “pyopencl” package in Debian: Fix Released Bug description: The package python-pyopencl depends on nvidia-current, which makes it impossible to correctly use on AMD / ATI systems. In debbugs #628702 debian started using a virtual package opencl-icd instead of depending directly on particular graphics driver / opencl implementation. We should follow the same. TODO * syn pyopencl * nvidia-graphics-drivers or nvidia-common (not sure) to provide opencl-icd * fglrx-installer to provide opencl-icd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/763457/+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 763457] Re: please provide opencl-icd virtual package
** Also affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319-updates (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-319 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-common in Ubuntu. https://bugs.launchpad.net/bugs/763457 Title: please provide opencl-icd virtual package Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “nvidia-common” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “fglrx-installer” source package in Quantal: Won't Fix Status in “nvidia-common” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Status in “nvidia-graphics-drivers-304” source package in Quantal: New Status in “nvidia-graphics-drivers-304-updates” source package in Quantal: New Status in “nvidia-graphics-drivers-319” source package in Quantal: New Status in “nvidia-graphics-drivers-319-updates” source package in Quantal: New Status in “pyopencl” source package in Quantal: Fix Released Status in “pyopencl” package in Debian: Fix Released Bug description: The package python-pyopencl depends on nvidia-current, which makes it impossible to correctly use on AMD / ATI systems. In debbugs #628702 debian started using a virtual package opencl-icd instead of depending directly on particular graphics driver / opencl implementation. We should follow the same. TODO * syn pyopencl * nvidia-graphics-drivers or nvidia-common (not sure) to provide opencl-icd * fglrx-installer to provide opencl-icd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/763457/+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 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
Someone needs to test the version in precise-proposed and then tag this bug 'verification-done' or 'verification-failed' as appropriate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings Status in “nvidia-settings” package in Ubuntu: Invalid Status in “nvidia-settings-experimental-304” package in Ubuntu: Fix Committed Status in “nvidia-settings-experimental-310” package in Ubuntu: Fix Committed Status in “nvidia-settings-updates” package in Ubuntu: Invalid Status in “nvidia-settings” source package in Precise: New Status in “nvidia-settings-experimental-304” source package in Precise: New Status in “nvidia-settings-experimental-310” source package in Precise: New Status in “nvidia-settings-updates” source package in Precise: New Bug description: package nvidia-settings was installed. Seemed to conflict somehow. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 (not installed) ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 AptOrdering: nvidia-settings-experimental-310: Install nvidia-settings-experimental-310: Configure Architecture: amd64 Date: Thu Nov 8 17:00:14 2012 DpkgTerminalLog: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 DuplicateSignature: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 ErrorMessage: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: nvidia-settings-experimental-310 Title: package nvidia-settings-experimental-310 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 UpgradeStatus: Upgraded to precise on 2012-05-16 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+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 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
Tagging verification-failed so these packages can be removed. ** Tags added: verification-failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings Status in “nvidia-settings” package in Ubuntu: Invalid Status in “nvidia-settings-experimental-304” package in Ubuntu: Invalid Status in “nvidia-settings-experimental-310” package in Ubuntu: Invalid Status in “nvidia-settings-updates” package in Ubuntu: Invalid Status in “nvidia-settings” source package in Precise: Invalid Status in “nvidia-settings-experimental-304” source package in Precise: Invalid Status in “nvidia-settings-experimental-310” source package in Precise: Invalid Status in “nvidia-settings-updates” source package in Precise: Invalid Bug description: package nvidia-settings was installed. Seemed to conflict somehow. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 (not installed) ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 AptOrdering: nvidia-settings-experimental-310: Install nvidia-settings-experimental-310: Configure Architecture: amd64 Date: Thu Nov 8 17:00:14 2012 DpkgTerminalLog: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 DuplicateSignature: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 ErrorMessage: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: nvidia-settings-experimental-310 Title: package nvidia-settings-experimental-310 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 UpgradeStatus: Upgraded to precise on 2012-05-16 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+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 2037642] Re: [FFe] Raspberry Pi 5 support
FFe for linux-firmware-raspi in LP: #2037634 FFe for gpiozero in LP: #2037637 ** No longer affects: linux-firmware-raspi (Ubuntu) ** Changed in: libcamera (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux-meta-raspi (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Triaged ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged ** Changed in: pipewire (Ubuntu) Status: Confirmed => Triaged ** Changed in: rpi-eeprom (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
** Tags removed: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in kdump-tools source package in Xenial:
New
Status in makedumpfile source package in Xenial:
Won't Fix
Status in kdump-tools source package in Bionic:
New
Status in makedumpfile source package in Bionic:
Confirmed
Status in kdump-tools source package in Eoan:
New
Status in makedumpfile source package in Eoan:
Won't Fix
Status in kdump-tools source package in Focal:
New
Status in makedumpfile source package in Focal:
Confirmed
Status in kdump-tools source package in Groovy:
New
Status in makedumpfile source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
"patch" flag removed from the attachment
"patch" tag removed
~ubuntu-sponsors unsubscribed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in kdump-tools source package in Xenial:
New
Status in makedumpfile source package in Xenial:
Won't Fix
Status in kdump-tools source package in Bionic:
New
Status in makedumpfile source package in Bionic:
Confirmed
Status in kdump-tools source package in Eoan:
New
Status in makedumpfile source package in Eoan:
Won't Fix
Status in kdump-tools source package in Focal:
New
Status in makedumpfile source package in Focal:
Confirmed
Status in kdump-tools source package in Groovy:
New
Status in makedumpfile source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 2072750] Re: hwloc 2.11.0-2 stuck in proposed as it requires libnvidia-compute-550 (>= 550.90.07)
** Also affects: hwloc-contrib (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550 (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-550 in Ubuntu. https://bugs.launchpad.net/bugs/2072750 Title: hwloc 2.11.0-2 stuck in proposed as it requires libnvidia-compute-550 (>= 550.90.07) Status in hwloc package in Ubuntu: New Status in hwloc-contrib package in Ubuntu: New Status in nvidia-graphics-drivers-550 package in Ubuntu: New Bug description: hwloc (2.10.0-1build1 to 2.11.0-2) Migration status for hwloc (2.10.0-1build1 to 2.11.0-2): Will attempt migration (Any information below is purely informational) Additional info: 7 days old It depends on "hwloc-contrib" packages to migrate and dose-distcheck reports that in turn this requires "libnvidia-compute-550 (>= 550.90.07)" which cannot migrate due to other reasons (related to the kernel). missing: pkg: package: libhwloc-contrib-plugins version: 2.11.0-1 architecture: arm64 unsat-dependency: libnvidia-compute-550 (>= 550.90.07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwloc/+bug/2072750/+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 1990964] Re: FTBFS on kinetic
** Changed in: strace (Ubuntu) Assignee: Adrien Nader (adrien-n) => Graham Inggs (ginggs) ** Changed in: strace (Ubuntu) Status: Triaged => In Progress -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: In Progress Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1990964] Re: FTBFS on kinetic
Sponsored with minor changes, as discussed with Adrien: kinetic -> lunar dropped debian/changelog.in delta ** Changed in: strace (Ubuntu) Status: In Progress => Fix Committed ** Also affects: strace (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: Fix Committed Status in linux source package in Kinetic: New Status in strace source package in Kinetic: New Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1215411] Re: libcpupower.so is not installed from linux-tools
** Also affects: opa-ff (Ubuntu) Importance: Undecided Status: New -- 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/1215411 Title: libcpupower.so is not installed from linux-tools Status in cpufreqd package in Ubuntu: Confirmed Status in gkrellm2-cpufreq package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in opa-ff package in Ubuntu: New Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1215411/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: ubuntu-drivers-common (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => Invalid ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Status: New => Confirmed ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Milestone: None => lunar-updates ** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Milestone: ubuntu-23.04 => ubuntu-23.10-beta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Confirmed Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2034510] Re: spl fails to unregister sysctl entries
** Changed in: zfs-linux (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2034510 Title: spl fails to unregister sysctl entries Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Mantic: Fix Committed Bug description: [Impact] On unload the spl module is not properly cleaning up the registered sysctl entries with kernel 6.5 in Mantic: 06:58 ubuntu@mantic$ sudo modprobe spl modprobe: ERROR: could not insert 'spl': Protocol driver not attached 06:58 ubuntu@mantic$ sudo dmesg | grep duplicate [ 152.587197] sysctl duplicate entry: /kernel/spl/kmem/slab_kvmem_total [Test case] Uninstall zfsutils-linux and try to `modprobe -r zfs; modprobe -r spl`, then `modprobe zfs` again and you should see the error (with a failure to load spl again). At this point it is possible to load spl again only after a reboot. [Fix] Properly cleanup all the registered sysctl entries when the spl module is unloaded. [Regression potential] We may experience regressions in systems that are using zfs with the 6.5 kernel. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: zfs-dkms 2.2.0~rc3-0ubuntu3 ProcVersionSignature: User Name 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230823 CloudSubPlatform: config-disk (/dev/vdb) Date: Wed Sep 6 07:06:33 2023 PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2034510/+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 1990964] Re: FTBFS on kinetic
Now that the kernel is fixed, we can see a different error:
gcc -DHAVE_CONFIG_H -I./linux/x86_64 -I../../src/linux/x86_64
-I./linux/generic -I../../src/linux/generic -I. -I../../src -DIN_STRACE=1
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-missing-field-initializers
-Wno-unused-parameter -Wdate-time -Wformat-security -Wimplicit-fallthrough=5
-Winit-self -Wlogical-op -Wmissing-prototypes -Wnested-externs
-Wold-style-definition -Wtrampolines -Wundef -Wwrite-strings -Werror -g -O2
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
-Wall -g -MT libstrace_a-ioctl.o -MD -MP -MF .deps/libstrace_a-ioctl.Tpo -c -o
libstrace_a-ioctl.o `test -f 'ioctl.c' || echo '../../src/'`ioctl.c
In file included from ../../src/list.h:90,
from ../../src/defs.h:40,
from ../../src/io_uring.c:9:
../../src/io_uring.c: In function ‘print_io_uring_register_rsrc’:
../../src/io_uring.c:394:29: error: ‘struct io_uring_rsrc_register’ has no
member named ‘resv’; did you mean ‘resv2’?
394 | CHECK_TYPE_SIZE(arg.resv, sizeof(uint32_t));
| ^~~~
../../src/macros.h:141:30: note: in definition of macro ‘CHECK_TYPE_SIZE’
141 | static_assert(sizeof(type_) == (sz_), \
| ^
../../src/macros.h:141:23: error: expression in static assertion is not an
integer
141 | static_assert(sizeof(type_) == (sz_), \
| ^~
../../src/io_uring.c:394:9: note: in expansion of macro ‘CHECK_TYPE_SIZE’
394 | CHECK_TYPE_SIZE(arg.resv, sizeof(uint32_t));
| ^~~
../../src/io_uring.c:408:17: error: ‘struct io_uring_rsrc_register’ has no
member named ‘resv’; did you mean ‘resv2’?
408 | if (arg.resv) {
| ^~~~
| resv2
https://launchpadlibrarian.net/628843686/buildlog_ubuntu-kinetic-amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz
--
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/1990964
Title:
FTBFS on kinetic
Status in linux package in Ubuntu:
Fix Released
Status in strace package in Ubuntu:
Triaged
Bug description:
As can be seen in [1], strace FTBFS in kinetic: this is caused by the
kernel headers (linux-libc-dev) which do not define F_GETLK64 and
other on 64b builds because the kernel contains a bogus commit
(306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
fcntl.h"). This commit actually did the opposite of what it was
supposed to do, namely defining those macros even on 64b builds. There
is an attempt here to fix this which was not merged yet:
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/
[1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1988966] [NEW] kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency
Public bug reported: kiwi-dracut-oem-dump has a dependency on kexec-tools which is not built for riscv64. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254 contains a patch from openSUSE https://build.opensuse.org/package/view_file/openSUSE:Factory:RISCV/kexec- tools/riscv.patch ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Affects: kiwi (Ubuntu) Importance: Undecided Status: New ** Affects: kexec-tools (Debian) Importance: Unknown Status: Unknown ** Tags: update-excuse ** Also affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse ** Bug watch added: Debian Bug tracker #1019254 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254 ** Also affects: kexec-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1988966 Title: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency Status in kexec-tools package in Ubuntu: New Status in kiwi package in Ubuntu: New Status in kexec-tools package in Debian: Unknown Bug description: kiwi-dracut-oem-dump has a dependency on kexec-tools which is not built for riscv64. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254 contains a patch from openSUSE https://build.opensuse.org/package/view_file/openSUSE:Factory:RISCV/kexec- tools/riscv.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1988966/+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 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support
** Summary changed: - PolarFire Icicle Kit: enable PCIe support + [FFe] PolarFire Icicle Kit: enable PCIe support -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1989566 Title: [FFe] PolarFire Icicle Kit: enable PCIe support Status in linux-riscv package in Ubuntu: New Bug description: The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it is not usable. Please, add the following patches: # https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/ riscv: dts: microchip: add pci dma ranges for the icicle # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: move the mpfs' pci node to # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: update pci address # https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: re-jig fabric peripheral # https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/ riscv: dts: microchip: add fabric address translation # https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/ PCI: microchip: add fabric address translation properties All patches are strictly restricted to the PolarFire Icicle Kit and have no impact on any other RISC-V boards that we support. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+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 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support
This is fine from Release Team's perspective, so FFe granted, but still needs Kernel Team to incorporate the changes. ** Changed in: linux-riscv (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1989566 Title: [FFe] PolarFire Icicle Kit: enable PCIe support Status in linux-riscv package in Ubuntu: Triaged Bug description: The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it is not usable. Please, add the following patches: # https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/ riscv: dts: microchip: add pci dma ranges for the icicle # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: move the mpfs' pci node to # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: update pci address # https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: re-jig fabric peripheral # https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/ riscv: dts: microchip: add fabric address translation # https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/ PCI: microchip: add fabric address translation properties All patches are strictly restricted to the PolarFire Icicle Kit and have no impact on any other RISC-V boards that we support. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+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 2101893] Re: [FFe] Update zfs-linux to upstream 2.3.0
** Summary changed: - Update zfs-linux to upstream 2.3.0 + [FFe] Update zfs-linux to upstream 2.3.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2101893 Title: [FFe] Update zfs-linux to upstream 2.3.0 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Plucky: New Bug description: Would like to update to the 2.3.0 upstream version for the Plucky release due to the following new features: * RAIDZ Expansion: Add new devices to an existing RAIDZ pool, increasing storage capacity without downtime. * Fast Dedup: A major performance upgrade to the original OpenZFS deduplication functionality. * Direct IO: Allows bypassing the ARC for reads/writes, improving performance in scenarios like NVMe devices where caching may hinder efficiency. * JSON: Optional JSON output for the most used commands. * Long names: Support for file and directory names up to 1023 characters. * Bug Fixes: A series of critical bug fixes addressing issues reported in previous versions. * Numerous performance improvements throughout the code base. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2101893/+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 2101893] Re: [FFe] Update zfs-linux to upstream 2.3.0
Hi John, a quick question, at: https://github.com/openzfs/zfs/releases/tag/zfs-2.3.1 I see: Linux: compatible with 4.18 - 6.13 kernels What is the plan for supporting the 6.14 kernel, expected in plucky? Is upgrading to zfs-linux 2.3.0 a pre-requisite for that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2101893 Title: [FFe] Update zfs-linux to upstream 2.3.0 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Plucky: New Bug description: Would like to update to the 2.3.0 upstream version for the Plucky release due to the following new features: * RAIDZ Expansion: Add new devices to an existing RAIDZ pool, increasing storage capacity without downtime. * Fast Dedup: A major performance upgrade to the original OpenZFS deduplication functionality. * Direct IO: Allows bypassing the ARC for reads/writes, improving performance in scenarios like NVMe devices where caching may hinder efficiency. * JSON: Optional JSON output for the most used commands. * Long names: Support for file and directory names up to 1023 characters. * Bug Fixes: A series of critical bug fixes addressing issues reported in previous versions. * Numerous performance improvements throughout the code base. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2101893/+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 2101893] Re: [FFe] Update zfs-linux to upstream 2.3.0
Thanks. There is always a risk that adding new features brings new bugs, but let's get this in early, so it can get some testing during the beta. FFe approved, please go ahead. ** Changed in: zfs-linux (Ubuntu Plucky) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2101893 Title: [FFe] Update zfs-linux to upstream 2.3.0 Status in zfs-linux package in Ubuntu: Triaged Status in zfs-linux source package in Plucky: Triaged Bug description: Would like to update to the 2.3.0 upstream version for the Plucky release due to the following new features: * RAIDZ Expansion: Add new devices to an existing RAIDZ pool, increasing storage capacity without downtime. * Fast Dedup: A major performance upgrade to the original OpenZFS deduplication functionality. * Direct IO: Allows bypassing the ARC for reads/writes, improving performance in scenarios like NVMe devices where caching may hinder efficiency. * JSON: Optional JSON output for the most used commands. * Long names: Support for file and directory names up to 1023 characters. * Bug Fixes: A series of critical bug fixes addressing issues reported in previous versions. * Numerous performance improvements throughout the code base. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2101893/+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 2101893] Re: [FFe] Update zfs-linux to upstream 2.3.1
To be clear, going directly to 2.3.1 under this FFe would be fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2101893 Title: [FFe] Update zfs-linux to upstream 2.3.1 Status in zfs-linux package in Ubuntu: Triaged Status in zfs-linux source package in Plucky: Triaged Bug description: Would like to update to the 2.3.0 upstream version for the Plucky release due to the following new features: * RAIDZ Expansion: Add new devices to an existing RAIDZ pool, increasing storage capacity without downtime. * Fast Dedup: A major performance upgrade to the original OpenZFS deduplication functionality. * Direct IO: Allows bypassing the ARC for reads/writes, improving performance in scenarios like NVMe devices where caching may hinder efficiency. * JSON: Optional JSON output for the most used commands. * Long names: Support for file and directory names up to 1023 characters. * Bug Fixes: A series of critical bug fixes addressing issues reported in previous versions. * Numerous performance improvements throughout the code base. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2101893/+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 2028925] Re: FTBFS: too many arguments to function ‘zpool_search_import’
The FTBFS of grubzfs-testsuite is preventing zfs-linux from migrating.
I've added zfs-linux as an affecetd package so that it appears on the excuses
report.
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2028925
Title:
FTBFS: too many arguments to function ‘zpool_search_import’
Status in grubzfs-testsuite package in Ubuntu:
New
Status in zfs-linux package in Ubuntu:
New
Bug description:
Building this package on mantic, I get:
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
go test -c -o grubzfs-tests
# github.com/bicomsystems/go-libzfs
In file included from /usr/include/libzfs/libzfs.h:37,
from zfs.c:5:
zfs.c: In function ‘read_user_property’:
zfs.c:208:38: warning: passing argument 3 of ‘nvlist_lookup_string’ from
incompatible pointer type [-Wincompatible-pointer-types]
208 | ZPROP_VALUE, &strval) == 0);
| ^~~
| |
| char **
/usr/include/libspl/assert.h:71:20: note: in definition of macro ‘verify’
71 | (void) ((!(cond)) &&
\
|^~~~
In file included from /usr/include/libzfs/libnvpair.h:29,
from /usr/include/libzfs/libzfs.h:39:
/usr/include/libzfs/sys/nvpair.h:236:5: note: expected ‘const char **’ but
argument is of type ‘char **’
236 | const char **);
| ^
zfs.c:210:39: warning: passing argument 3 of ‘nvlist_lookup_string’ from
incompatible pointer type [-Wincompatible-pointer-types]
210 | ZPROP_SOURCE, &sourceval) == 0);
| ^~
| |
| char **
/usr/include/libspl/assert.h:71:20: note: in definition of macro ‘verify’
71 | (void) ((!(cond)) &&
\
|^~~~
/usr/include/libzfs/sys/nvpair.h:236:5: note: expected ‘const char **’ but
argument is of type ‘char **’
236 | const char **);
| ^
# github.com/bicomsystems/go-libzfs
zpool.c: In function ‘get_vdev_type’:
zpool.c:374:61: warning: passing argument 3 of ‘nvlist_lookup_string’ from
incompatible pointer type [-Wincompatible-pointer-types]
374 | int r = nvlist_lookup_string(nv, ZPOOL_CONFIG_TYPE, &value);
| ^~
| |
| char **
In file included from /usr/include/libzfs/libnvpair.h:29,
from /usr/include/libzfs/libzfs.h:39,
from zpool.c:5:
/usr/include/libzfs/sys/nvpair.h:236:5: note: expected ‘const char **’ but
argument is of type ‘char **’
236 | const char **);
| ^
zpool.c: In function ‘get_vdev_path’:
zpool.c:448:72: warning: passing argument 3 of ‘nvlist_lookup_string’ from
incompatible pointer type [-Wincompatible-pointer-types]
448 | if ( 0 != nvlist_lookup_string(nv,
ZPOOL_CONFIG_PATH, &path) ) {
|
^
|
|
|
char **
/usr/include/libzfs/sys/nvpair.h:236:5: note: expected ‘const char **’ but
argument is of type ‘char **’
236 | const char **);
| ^
zpool.c: In function ‘get_zpool_name’:
zpool.c:477:67: warning: passing argument 3 of ‘nvlist_lookup_string’ from
incompatible pointer type [-Wincompatible-pointer-types]
477 | if (0 != nvlist_lookup_string(nv, ZPOOL_CONFIG_POOL_NAME,
&name)) {
|
^
| |
|
char **
/usr/include/libzfs/sys/nvpair.h:236:5: note: expected ‘const char **’ but
argument is of type ‘char **’
236 | const char **);
| ^
zpool.c: In function ‘get_zpool_comment’:
zpool.c:485:65: warning: passing argument 3 of ‘nvlist_lookup_string’ from
incompatible pointer type [-Wincompatible-pointer-types]
485 | if (0 != nvlist_lookup_string(nv, ZPOOL_CONFIG_COMMENT,
&comment)) {
|
