[Kernel-packages] [Bug 1857271] Re: Focal PRIME Synchronization still not working (450.x)
Not an issue here on my optimus laptop (slightly aged as latest laptop is nvidia only $ uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-48-generic #52~18.04.1-Ubuntu SMP Thu Sep 10 12:50:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 Y $ inxi -CG CPU: Quad core Intel Core i7-4700MQ (-MT-MCP-) cache: 6144 KB clock speeds: max: 3400 MHz 1: 1381 MHz 2: 1736 MHz 3: 1339 MHz 4: 1811 MHz 5: 1336 MHz 6: 1453 MHz 7: 1588 MHz 8: 1503 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 755M] Display Server: x11 (X.Org 1.20.8 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@59.91hz OpenGL: renderer: GeForce GT 755M/PCIe/SSE2 version: 4.6.0 NVIDIA 450.57 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1857271 Title: Focal PRIME Synchronization still not working (450.x) Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: Ubuntu 19.04 (Disco) Linux 5.4.6-050406-generic linux-firmware-1.184 mutter-3.32.2+git20190711-2ubuntu1~19.04.1 nvidia-driver-440: Installed: 440.44-0ubuntu1 Candidate: 440.44-0ubuntu1 Version table: *** 440.44-0ubuntu1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I've noticed screen tearing with the nvidia 440 driver on 5.4.x kernels. Typically, this is resolved by setting the xrandr option 'PRIME Synchronization' to '1', however, doing so with the above combination results in never being enabled. $ xrandr --output eDP-1-1 --set 'PRIME Synchronization' '1' $ xrandr --verbose | grep PRIME PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 Reverting to Linux 5.0.0-37-generic resolve the issue, so I figured I'd raise it here first, however, it seems like a potential kernel regression issue if the only thing I'm changing is indeed the kernel version. Your input would be appreciated. I tried to figure out how to post a bug on the PPA, however, it seems bug creation is disabled on that PPA, so I ended up here. I've been testing newer kernel versions to get fixes for other problems with my hardware. Due to another package dependency, I'm stuck on disco for some pulseaudio bluetooth codec support, so I've been pushing forward the kernel, firmware and nvidia driver versions to get the other driver fixes. I realise this is not ideal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1857271/+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 1859357] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320272/+files/Lsusb-t.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320281/+files/WifiSyslog.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320277/+files/ProcModules.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320268/+files/CurrentDmesg.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320273/+files/Lsusb-v.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320270/+files/Lspci.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] Re: Prime synchronization breaks on kernel 5.4.0-9
Though would like to (re)mention that previously when same symptoms occurred it was fixed via a dkms_nvidia patch *as seen in report posted in comment #4 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320280/+files/UdevDb.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320269/+files/IwConfig.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320276/+files/ProcInterrupts.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320271/+files/Lsusb.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320267/+files/CRDA.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320275/+files/ProcCpuinfoMinimal.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320274/+files/ProcCpuinfo.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320279/+files/RfKill.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320278/+files/PulseList.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: doug 1680 F pulseaudio /dev/snd/controlC1: doug 1680 F pulseaudio /dev/snd/controlC0: doug 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) MachineType: LENOVO 20217 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] Re: Prime synchronization breaks on kernel 5.4.0-9
apport information ** Tags added: apport-collected ** Description changed: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu15 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: doug 1680 F pulseaudio + /dev/snd/controlC1: doug 1680 F pulseaudio + /dev/snd/controlC0: doug 1680 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-01-13 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) + MachineType: LENOVO 20217 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-9-generic N/A + linux-backports-modules-5.4.0-9-generic N/A + linux-firmware 1.184 + Tags: focal + Uname: Linux 5.4.0-9-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/18/2013 + dmi.bios.vendor: LENOVO + dmi.bios.version: 74CN44WW(V3.05) + dmi.board.asset.tag: No Asset Tag + dmi.board.name: VIQY0Y1 + dmi.board.vendor: LENOVO + dmi.board.version: 31900058STD + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo IdeaPad Y510P + dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: + dmi.product.family: IDEAPAD + dmi.product.name: 20217 + dmi.product.sku: LENOVO_BI_IDEAPAD + dmi.product.version: Lenovo IdeaPad Y510P + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1859357/+attachment/5320266/+files/AlsaInfo.txt -- 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/1859357 Title: Prime synchronization breaks on kernel 5.4.0-9 Status in linux package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchroni
[Kernel-packages] [Bug 1859357] Re: Prime Synchronizationbreaks on kernel 5.4.0-9
Oops - titled wrong, breaks on the 5.4.0-9 kernel As far as other bug - if that would suggest this would work on earlier driver, no such luck. Did as fresh install updated, used the 435 driver. Same result, prime sync works on the 5.3.x kernel, fails on the current 5.4.x kernel ** Summary changed: - Prime Synchronizationbreaks on kernel 5.3.0-24 + Prime Synchronizationbreaks on kernel 5.4.0-9 ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Incomplete => 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/1859357 Title: Prime Synchronizationbreaks on kernel 5.4.0-9 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1859357] Re: Prime Synchronizationbreaks on kernel 5.3.0-24
I didn't directly mention, it was the 4.15 kernel https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752739 -- 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/1859357 Title: Prime Synchronizationbreaks on kernel 5.3.0-24 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Test case: Optimus hardware 20.04 updated Install 440 driver Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file. reboot. Seen here - uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y While same machine, ect. while booting to previous 5.3.0-24 kernel uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 [sudo] password for doug: Y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.44-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 12 14:55:34 2020 InstallationDate: Installed on 2019-12-18 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859357/+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 1851416] [NEW] Prime Profiles page could be better
Public bug reported: There are 4 possibly problem points, placement, names, tooltips, help. The 1st 3 are somewhat linked. The new profile, NVIDIA On-Demand is currently placed between the 2 previous & historical ones of NVIDIA.. & Intel.. The placement and name could lead one to believe that it's an app on demand or as needed similar to how optimus works in windows. This is clearly not the case & if picked produces a degraded experience for most users.. It should be the 3rd listed profile and if possible named more towards it's actual use case. There previously were 2 tooltips on hover, currently there still are just 2, the one designed for Intel now exposes only when hovered over NVIDIA On-Demand, hovering over Intel produces nothing NVIDIA On-Demand should get it's own tooltip. The Help button popup shows no info on what NVIDIA On-Demand is about or for, considering the vast majority of users should not use that profile it should be described, ect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 5 12:18:49 2019 InstallationDate: Installed on 2019-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191029.2) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1851416 Title: Prime Profiles page could be better Status in nvidia-settings package in Ubuntu: New Bug description: There are 4 possibly problem points, placement, names, tooltips, help. The 1st 3 are somewhat linked. The new profile, NVIDIA On-Demand is currently placed between the 2 previous & historical ones of NVIDIA.. & Intel.. The placement and name could lead one to believe that it's an app on demand or as needed similar to how optimus works in windows. This is clearly not the case & if picked produces a degraded experience for most users.. It should be the 3rd listed profile and if possible named more towards it's actual use case. There previously were 2 tooltips on hover, currently there still are just 2, the one designed for Intel now exposes only when hovered over NVIDIA On-Demand, hovering over Intel produces nothing NVIDIA On-Demand should get it's own tooltip. The Help button popup shows no info on what NVIDIA On-Demand is about or for, considering the vast majority of users should not use that profile it should be described, ect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 5 12:18:49 2019 InstallationDate: Installed on 2019-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191029.2) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1851416/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Being duped here with a more specific bug, i.e 19.10 optimus hardware No login to ubuntu session possible with gdm, lightdm is ok Maybe a few comments. This bug orig. suggests that one could actually login on optimus hardware with nvidia-drm.modeset=1 thru gdm. That was once the case, it no longer is in 19.10. The only session available is a wayland one because it falls back to Intel. As far as why users set nvidia-drm.modeset=1? I'd suggest the majority do so on optimus machines to be able to use nvidia without tearing. For the most part none have any interest in wayland even though wayland would solve tearing. Why?, because no (or virtually none) optimus machine has ever been able to use wayland & nvidia drivers. Not in the last couple of years, not now. While I don't have a desktop machine I do have a laptop with nvidia GPU only. In that case (19.04) with nvidia-drm.modeset=1 it presents and logs into a wayland session but llvmpipe only. It does work ok in a ubuntu session. Maybe I'll give it a try with 19.10 though on this machine there is no tearing so xorg is fine, currently any positives, if any, of wayland are outweighed by it's negatives. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1822937] Re: NVIDIA settings won't write to /etc/xorg
ii screen-resolution-extra0.17.4 all Extension for the GNOME screen resolution applet -- 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/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: New Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1822937] Re: NVIDIA settings won't write to /etc/xorg
What one would see from terminal (pkexec ls works fine) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in activate_name_owner return self.get_name_owner(bus_name) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner 's', (bus_name,), **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'com.ubuntu.ScreenResolution.Mechanism': no such name During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/screen-resolution-extra/nvidia-polkit.py", line 75, in operation_status = main(options) File "/usr/share/screen-resolution-extra/nvidia-polkit.py", line 42, in main conf = get_xkit_service() File "/usr/share/screen-resolution-extra/nvidia-polkit.py", line 33, in get_xkit_service service_object = dbus.SystemBus().get_object(SERVICE_NAME, OBJECT_PATH) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch daemon, file not found or permissions invalid ERROR: Unable to open X config file '/etc/X11/xorg.conf' for writing. ** Changed in: nvidia-settings (Ubuntu) Status: Incomplete => 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/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: New Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1822482] Re: nouveau fails unless nvidia drivers are 1st installed, then removed. Only lasts for warm restarts, not cold boot
3.log ** Attachment added: "3.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822482/+attachment/5251222/+files/3.log -- 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/1822482 Title: nouveau fails unless nvidia drivers are 1st installed, then removed. Only lasts for warm restarts, not cold boot Status in linux package in Ubuntu: New Bug description: On a nvidia only laptop (NVIDIA GP106M) by default an install uses llvmpipe - $ inxi -G Graphics: Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.4 driver: modesetting,nouveau unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: llvmpipe (LLVM 8.0 256 bits) v: 3.3 Mesa 19.0.1 If nvidia drivers are installed, reboot, nvidia drivers removed, reboot then nouveau (NV136) is used. $ inxi -G Graphics: Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: NV136 v: 4.3 Mesa 19.0.1 This continues thru multiple reboots however if machine is shutdown a cold boot reverts to default behavior, i.e llvmpipe Attaching 2 dmesg logs, 1.log is default, 3.log is after nvidia driver install/remove/warm boots ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-8-generic 5.0.0-8.9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1705 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 31 11:48:02 2019 InstallationDate: Installed on 2019-03-15 (16 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) Lsusb: Bus 002 Device 002: ID 125f:a32a A-DATA Technology Co., Ltd. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b627 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-dc0xxx ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=fd08f3f9-2cd1-4662-b6d7-0519f1a36ecb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: AMI dmi.bios.version: F.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 84DB dmi.board.vendor: HP dmi.board.version: 93.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.08:bd02/21/2019:svnHP:pnOMENbyHPLaptop15-dc0xxx:pvr:rvnHP:rn84DB:rvr93.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dc0xxx dmi.product.sku: 3ME07AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822482/+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 1822482] [NEW] nouveau fails unless nvidia drivers are 1st installed, then removed. Only lasts for warm restarts, not cold boot
Public bug reported: On a nvidia only laptop (NVIDIA GP106M) by default an install uses llvmpipe - $ inxi -G Graphics: Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.4 driver: modesetting,nouveau unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: llvmpipe (LLVM 8.0 256 bits) v: 3.3 Mesa 19.0.1 If nvidia drivers are installed, reboot, nvidia drivers removed, reboot then nouveau (NV136) is used. $ inxi -G Graphics: Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: NV136 v: 4.3 Mesa 19.0.1 This continues thru multiple reboots however if machine is shutdown a cold boot reverts to default behavior, i.e llvmpipe Attaching 2 dmesg logs, 1.log is default, 3.log is after nvidia driver install/remove/warm boots ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-8-generic 5.0.0-8.9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1705 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 31 11:48:02 2019 InstallationDate: Installed on 2019-03-15 (16 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) Lsusb: Bus 002 Device 002: ID 125f:a32a A-DATA Technology Co., Ltd. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b627 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-dc0xxx ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=fd08f3f9-2cd1-4662-b6d7-0519f1a36ecb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: AMI dmi.bios.version: F.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 84DB dmi.board.vendor: HP dmi.board.version: 93.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.08:bd02/21/2019:svnHP:pnOMENbyHPLaptop15-dc0xxx:pvr:rvnHP:rn84DB:rvr93.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dc0xxx dmi.product.sku: 3ME07AV dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "default dmesg" https://bugs.launchpad.net/bugs/1822482/+attachment/5251206/+files/1.log -- 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/1822482 Title: nouveau fails unless nvidia drivers are 1st installed, then removed. Only lasts for warm restarts, not cold boot Status in linux package in Ubuntu: New Bug description: On a nvidia only laptop (NVIDIA GP106M) by default an install uses llvmpipe - $ inxi -G Graphics: Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.4 driver: modesetting,nouveau unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: llvmpipe (LLVM 8.0 256 bits) v: 3.3 Mesa 19.0.1 If nvidia drivers are installed, reboot, nvidia drivers removed, reboot then nouveau (NV136) is used. $ inxi -G Graphics: Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: NV136 v: 4.3 Mesa 19.0.1 This continues thru multiple reboots however if machine is shutdown a cold boot reverts to default behavior, i.e llvmpipe Attaching 2 dmesg logs, 1.log is default, 3.log is after nvidia driver install/remove/warm boots ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-8-generic 5.0.0-8.9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1705 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 31 11:48:02 2019 InstallationDate: Installed on 2019-03-15 (16 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) Lsusb: Bus 002 Device 002: ID 125f:a32a A-DATA Technology Co., Ltd. Bus 002
[Kernel-packages] [Bug 1820537] [NEW] Not used in a wayland session
Public bug reported: Test case Install nvidia-410 driver, enable Nvidia DRM KMS, reboot Log into wayland session What should happen: Get nvidia driver rendering What does happen: If using hybrid hardware then it falls back to Intel device If using recent nvidia gpu hardware only (10xx and newer) on a laptop it falls back to llvmpipe which is basically useless What happens on a Desktop machine don't know, don't have What happens with gpu's that have nouveau support again don't know, don't have. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-410 410.104-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:07:45 2019 InstallationDate: Installed on 2019-03-12 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-410 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-410 in Ubuntu. https://bugs.launchpad.net/bugs/1820537 Title: Not used in a wayland session Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: Test case Install nvidia-410 driver, enable Nvidia DRM KMS, reboot Log into wayland session What should happen: Get nvidia driver rendering What does happen: If using hybrid hardware then it falls back to Intel device If using recent nvidia gpu hardware only (10xx and newer) on a laptop it falls back to llvmpipe which is basically useless What happens on a Desktop machine don't know, don't have What happens with gpu's that have nouveau support again don't know, don't have. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-410 410.104-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:07:45 2019 InstallationDate: Installed on 2019-03-12 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-410 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-410/+bug/1820537/+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 1764794] Re: signing: only install a signed kernel
This update breaks the use of nvidia drivers in both 14.04 & 16.04 See https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1816768 ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial -- 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/1764794 Title: signing: only install a signed kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: We should switch the default kernel install to the signed kernel. This makes it much harder to uninstall the signed kernel in environments which enforce the kernel to be signed. Boot loaders which can understand and validate it want the signed image, those which do not should ignore the appended signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794/+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 1816768] Re: nvidia module fails to build
Yeah, appears this kernel update is in proposed for both 14.04 & 16.04. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794 So if it's intended to be promoted the nvidia driver should be fixed.. ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1816768 Title: nvidia module fails to build Status in linux-meta-lts-xenial package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: With the update to linux-meta-lts-xenial (4.4.0.143.124 nvidia fails to load. Reinstalling the driver (nvidia-384) shows this Building initial module for 4.4.0-143-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-384.0.crash' Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/nvidia-384/384.130/build/make.log for more information. Log attached ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic-lts-xenial 4.4.0.143.124 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 20 09:08:28 2019 InstallationDate: Installed on 2016-03-12 (1075 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-meta-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1816768/+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 1816768] [NEW] nvidia module fails to build
Public bug reported: With the update to linux-meta-lts-xenial (4.4.0.143.124 nvidia fails to load. Reinstalling the driver (nvidia-384) shows this Building initial module for 4.4.0-143-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-384.0.crash' Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/nvidia-384/384.130/build/make.log for more information. Log attached ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic-lts-xenial 4.4.0.143.124 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 20 09:08:28 2019 InstallationDate: Installed on 2016-03-12 (1075 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-meta-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed trusty ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1816768/+attachment/5240240/+files/make.log ** Also affects: nvidia-graphics-drivers-384 (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-384 in Ubuntu. https://bugs.launchpad.net/bugs/1816768 Title: nvidia module fails to build Status in linux-meta-lts-xenial package in Ubuntu: New Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: With the update to linux-meta-lts-xenial (4.4.0.143.124 nvidia fails to load. Reinstalling the driver (nvidia-384) shows this Building initial module for 4.4.0-143-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-384.0.crash' Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/nvidia-384/384.130/build/make.log for more information. Log attached ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic-lts-xenial 4.4.0.143.124 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 20 09:08:28 2019 InstallationDate: Installed on 2016-03-12 (1075 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-meta-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1816768/+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 1791951] Re: nvidia-settings does not work when i install proprietary driver and reboot
*** This bug is a duplicate of bug 1719945 ***
https://bugs.launchpad.net/bugs/1719945
** This bug has been marked a duplicate of bug 1719945
Silently fails in Wayland session
--
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/1791951
Title:
nvidia-settings does not work when i install proprietary driver and
reboot
Status in nvidia-settings package in Ubuntu:
Confirmed
Bug description:
- What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
- What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 3)
1. sudo prime-select nvidia.
2. Reboot and select X11 session.
3. Open nvidia-settings. --> Not ERROR.
In my second test, this step generate an error:
"ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
Steps (Case 4)
1. sudo prime-select intel.
2. Reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
Notes:
- The command: sudo prime-select nvidia[intel] always work
- Secure boot is disabled
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64
(20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1791951/+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 1719945] Re: Silently fails in Wayland session
Currently with hybrid systems a wayland session is presented when nvidia drivers are in use though the user is logged into wayland using the Intel gpu. So the fact that while in wayland the user can't use nvidia-settings > prime profiles to *actually* switch back to the Intel gpu makes this bug more of an issue. ** Tags removed: artful ** Tags added: rls-dd-incoming -- 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/1719945 Title: Silently fails in Wayland session Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia- settings fails silently when started from the shell. When started from a terminal, it prints: ERROR: Unable to load info from any available system and then quits. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 27 11:49:57 2017 InstallationDate: Installed on 2017-09-20 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+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 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu
How can this be marked as various "Fix Released" when the kernel depend was
reverted??
Also note that ubuntu-drivers-common removed the micocode detection based on
these so-called changes.
** Tags added: reverted
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1738259
Title:
need to ensure microcode updates are available to all bare-metal
installs of Ubuntu
Status in linux-meta package in Ubuntu:
Fix Released
Status in linux-meta-hwe package in Ubuntu:
New
Status in linux-meta-hwe-edge package in Ubuntu:
New
Status in linux-meta-lts-xenial package in Ubuntu:
Fix Released
Status in linux-meta source package in Precise:
New
Status in linux-meta source package in Trusty:
Fix Released
Status in linux-meta source package in Xenial:
Fix Released
Status in linux-meta-hwe source package in Xenial:
Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
New
Status in linux-meta source package in Zesty:
New
Status in linux-meta source package in Artful:
Fix Released
Status in linux-meta source package in Bionic:
Fix Released
Bug description:
From time to time, CPU vendors release updates to microcode that can
be loaded into the CPU from the OS. For x86, we have these updates
available in the archive as amd64-microcode and intel-microcode.
Sometimes, these microcode updates have addressed security issues with
the CPU. They almost certainly will again in the future.
We should ensure that all users of Ubuntu on baremetal x86 receive
these security updates, and have them applied to the CPU in early boot
where at all feasible.
Because these are hardware-dependent packages which we don't want to
install except on baremetal (so: not in VMs or containers), the
logical place to pull them into the system is via the kernel, so that
only the kernel baremetal flavors pull them in. This is analogous to
linux-firmware, which is already a dependency of the linux-
image-{lowlatency,generic} metapackages, and whose contents are
applied to the hardware by the kernel similar to microcode.
So, please update the linux-image-{lowlatency,generic} metapackages to
add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
and the corresponding hwe metapackages also.
Please time this change to coincide with the next updates of the
microcode packages in the archive.
I believe we will also need to promote the *-microcode packages to
main from restricted as part of this (again, by analogy with linux-
firmware).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+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 1757180] Re: nvidia-prime can't switch off the discrete GPU
Re: nvidia-setting previously with alternatives lightdm could affect switch on a og out/in, however gdm3 needed a reboot. The message was never changed to reflect this, now that apparently a reboot is required no matter what dm it would be a good time to edit it. Old bug - https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1704781 -- 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/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+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
Re: [Kernel-packages] [Bug 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python
On 10/08/2017 05:11 AM, Yuriy Padlyak wrote: > After python-minimal installation and switching to intel the suggested > relogin doesn't work. I've tried reboot, but now the setting doesn't start > again. This time with a different error: > ERROR: The control display is undefined; please run `nvidia-settings --help` > for usage information. > Not sure that has anything to do with this bug. When switching prime profiles a restart is required (gdm3 only), that's a separate longstanding unattended to bug. https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1704781 Maybe something went south for you when trying to do the switch via a log out? -- 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/1721394 Title: Cannot open nvidia-settings on pc with a hybrid device (or use prime- select), missing python Status in nvidia-prime package in Ubuntu: Triaged Status in nvidia-settings package in Ubuntu: Confirmed Bug description: You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory One would need to go python3 /usr/bin/prime-select intel This is because the python package has been removed from image & isn't installed by either nvidia-settings or nvidia-prime. Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python
Ok, fresh install today's image 1. The manifest say python-minimal is included but it's not installed, $ apt-cache policy python-minimal python-minimal: Installed: (none) Candidate: 2.7.14-2ubuntu1 Version table: 2.7.14-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 2. Also on the manifest but not installed are python2.7 python2.7-minimal 3. Installing nvidia-384 goes fine. If opening nvidia-settings after install but *before* rebooting it actually opens. 4. After rebooting it fails to open as noted in the bug report description. 5. Installing python-minimal or python fixes this or maybe they just need to use python3 -- 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/1721394 Title: Cannot open nvidia-settings on pc with a hybrid device (or use prime- select), missing python Status in nvidia-prime package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Bug description: You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory One would need to go python3 /usr/bin/prime-select intel This is because the python package has been removed from image & isn't installed by either nvidia-settings or nvidia-prime. Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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
Re: [Kernel-packages] [Bug 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python
I wasn't really sure that it really needed the python package, it seems toneed /usr/bin/python which should have been installed as it's provided by the python-minimal package. When nvidia-settings wouldn't start I just installed the python package which brought in python-minimal, ect. When I check the manifest for the current image python-minimal is listed. Maybe I'll try a new install to make sure it is there after installing On Oct 5, 2017 10:01 PM, "Jeremy Bicha" wrote: > Doug, if the package needs python, then it should be marked as a > dependency. > > ** Changed in: nvidia-prime (Ubuntu) >Status: Invalid => New > > ** Changed in: nvidia-settings (Ubuntu) >Status: Invalid => New > > ** Tags added: rls-aa-incoming > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1721394 > > Title: > Cannot open nvidia-settings on pc with a hybrid device (or use prime- > select), missing python > > Status in nvidia-prime package in Ubuntu: > New > Status in nvidia-settings package in Ubuntu: > New > > Bug description: > You would see - > $ nvidia-settings > ** Message: PRIME: Requires offloading > ** Message: PRIME: is it supported? yes > > ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute > child process “/usr/bin/prime-select” (No such file or directory) > Trace/breakpoint trap > > Additionally if trying to run prime-select you'd see - > sudo: unable to execute /usr/bin/prime-select: No such file or directory > > One would need to go >python3 /usr/bin/prime-select intel > > This is because the python package has been removed from image & isn't > installed by either nvidia-settings or nvidia-prime. > > Please adjust this packages to either use python3 or dep to python > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: nvidia-settings 367.35-0ubuntu1 > ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 > Uname: Linux 4.13.0-12-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu2 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Oct 4 17:16:44 2017 > InstallationDate: Installed on 2017-10-04 (0 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: nvidia-settings > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+ > bug/1721394/+subscriptions > -- 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/1721394 Title: Cannot open nvidia-settings on pc with a hybrid device (or use prime- select), missing python Status in nvidia-prime package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Bug description: You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory One would need to go python3 /usr/bin/prime-select intel This is because the python package has been removed from image & isn't installed by either nvidia-settings or nvidia-prime. Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python
going to mark invalid, how this install, (Beta amd64 (20170929) ended up without python-minimal is unknown. Could have been from bad behavior from unattended-upgrades. For historical info it had been removed as seen here when I installed python Commit Log for Wed Oct 4 17:19:48 2017 Installed the following packages: libpython-stdlib (2.7.14-2ubuntu1) python (2.7.14-2ubuntu1) python-minimal (2.7.14-2ubuntu1) python2.7 (2.7.14-2ubuntu2) python2.7-minimal (2.7.14-2ubuntu2) ** Changed in: nvidia-prime (Ubuntu) Status: New => Invalid ** Changed in: nvidia-settings (Ubuntu) Status: New => Invalid -- 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/1721394 Title: Cannot open nvidia-settings on pc with a hybrid device (or use prime- select), missing python Status in nvidia-prime package in Ubuntu: Invalid Status in nvidia-settings package in Ubuntu: Invalid Bug description: You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory One would need to go python3 /usr/bin/prime-select intel This is because the python package has been removed from image & isn't installed by either nvidia-settings or nvidia-prime. Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1719945] Re: Silently fails in Wayland session
While I can certainly confirm, what is the use case? It would seem only useful when in a wayland session to switch from the intel profile to the nvidia one before rebooting to an xorg session. I guess that could save a little time/effort. -- 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/1719945 Title: Silently fails in Wayland session Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia- settings fails silently when started from the shell. When started from a terminal, it prints: ERROR: Unable to load info from any available system and then quits. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 27 11:49:57 2017 InstallationDate: Installed on 2017-09-20 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+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 1719945] Re: Silently fails in Wayland session
** Changed in: nvidia-settings (Ubuntu) Status: New => Confirmed -- 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/1719945 Title: Silently fails in Wayland session Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia- settings fails silently when started from the shell. When started from a terminal, it prints: ERROR: Unable to load info from any available system and then quits. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 27 11:49:57 2017 InstallationDate: Installed on 2017-09-20 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+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 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python
** Summary changed: - Cannot open nvidia-settings on pc with a hybrid device (or use prime-select + Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python -- 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/1721394 Title: Cannot open nvidia-settings on pc with a hybrid device (or use prime- select), missing python Status in nvidia-prime package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Bug description: You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory One would need to go python3 /usr/bin/prime-select intel This is because the python package has been removed from image & isn't installed by either nvidia-settings or nvidia-prime. Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1721394] [NEW] Cannot open nvidia-settings on pc with a hybrid device (or use prime-select
Public bug reported: You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory One would need to go python3 /usr/bin/prime-select intel This is because the python package has been removed from image & isn't installed by either nvidia-settings or nvidia-prime. Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: - You would see - + You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap - Additionally if trying to run prime-select you'd see - + Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory - One would need to go - python3 /usr/bin/prime-select intel + One would need to go + python3 /usr/bin/prime-select intel This is because the python package has been removed from image & is installed by either nvidia-settings or nvidia-prime. - Please adjuct this packages to either use python3 or dep to python + Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Cannot open nvidia-settings on pc with a hybrid device + Cannot open nvidia-settings on pc with a hybrid device (or use prime-select ** Description changed: You would see - $ nvidia-settings ** Message: PRIME: Requires offloading ** Message: PRIME: is it supported? yes ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child process “/usr/bin/prime-select” (No such file or directory) Trace/breakpoint trap Additionally if trying to run prime-select you'd see - sudo: unable to execute /usr/bin/prime-select: No such file or directory One would need to go python3 /usr/bin/prime-select intel - This is because the python package has been removed from image & is + This is because the python package has been removed from image & isn't installed by either nvidia-settings or nvidia-prime. Please adjust this packages to either use python3 or dep to python ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:16:44 2017 InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash S
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
** Tags removed: wily ** Tags added: yakketywily ** Tags removed: yakketywily ** Tags added: wily yakkety -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1580732] Re: wireless keyboard - repeating characters unattended
*** This bug is a duplicate of bug 1579190 *** https://bugs.launchpad.net/bugs/1579190 I would suugest one or more of those affected try the 4.6 or 4.7 kernel as mentioned in post 3 or this bug will go nowhere ** This bug has been marked a duplicate of bug 1579190 Key 5 automatically pressed on some Logitech wireless keyboards -- 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/1580732 Title: wireless keyboard - repeating characters unattended Status in linux package in Ubuntu: Incomplete Bug description: When doing nothing at all, the screen (eg an editor, mail message, terminal etc) will start displaying '5' rapidly across the screen. I am a recent ubuntu 16.04 user - a fresh install "Linux TimPassingham 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux" I was previously on 14.04 and had no such issues. My keyboard is a Logitech wireless MK700/710. There is nothing wrong with it in normal running, nor when using windows (dual-booted). I am not alone, and it is the same key (5) for others seeing this issue. See https://askubuntu.com/questions/761522/ubuntu-16-04 -repeats-keys-without-holding-down-any-key ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crusty 1927 F pulseaudio /dev/snd/controlC1: crusty 1927 F pulseaudio /dev/snd/pcmC2D0c: crusty 1927 F...m pulseaudio /dev/snd/controlC2: crusty 1927 F pulseaudio CurrentDesktop: Unity Date: Wed May 11 19:41:39 2016 HibernationDevice: RESUME=UUID=79194a4a-c084-466c-8b41-b5988820be2e InstallationDate: Installed on 2016-05-08 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=fcd7b99b-d3fb-4a80-b928-e0378d881a8a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B220P007 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID92/ZBOX-IQ01 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB220P007:bd05/21/2014:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-ID92/ZBOX-IQ01 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580732/+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 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards
** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1579190 Title: Key 5 automatically pressed on some Logitech wireless keyboards Status in linux package in Ubuntu: Confirmed Bug description: I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5. It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage. It seems that this is a Linux specific issue as no one is complaining about this issue under Windows, but a couple of people are complaining for different versions of Ubuntu. It is always 5 and WladyXX3740 claims on the Logitech forum that: "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related." Here is where most of the people are complaining: https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639 I discovered that this is related to my Logitech keyboard by running this command: xinput test-xi2 --root Here is the device list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ Logitech M310/M310t id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ DELL Wireless hotkeys id=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] And some extract from the output when this happens: EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 12 (PropertyEvent) property: 308 'Synaptics Off' changed: modified EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.21.22 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux
[Kernel-packages] [Bug 1559576] Re: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
** Also affects: gdm3 (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/1559576 Title: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1559576/+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 1551003] Re: Xenial Files cannot browse network
** Also affects: nautilus (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/1551003 Title: Xenial Files cannot browse network Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Bug description: Xenial Files can't browse wired local network. In a different partition, same pc, 14.04.3 Files can Browse Network, both ubuntu and Windows pc's Xenial Nemo select "Network" can browse the network fine, display photos from Windows pc O.K. Xenial Files will not browse, just asks for server address whatever that is and will not proceed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sun Feb 28 15:35:10 2016 InstallationDate: Installed on 2016-01-31 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=c38a379f-bb91-4c00-be51-7f4824e0aa0e ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551003/+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 1465706] Re: SRU: New upstream releases of nvidia for 14.04.3
nvidia-graphics-drivers-346-updates installs fine with the lts-vivid kernel ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1465706 Title: SRU: New upstream releases of nvidia for 14.04.3 Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-346 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Invalid Status in nvidia-settings package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: In Progress Status in nvidia-graphics-drivers-304-updates source package in Trusty: In Progress Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Committed Status in nvidia-settings source package in Trusty: In Progress Bug description: SRU Request: [Impact] The nvidia packages in Ubuntu 14.04 do not support the backported kernel from 15.04. [Test Case] 1) Enable the trusty-proposed repository, and install the "linux-generic-lts-vivid" 2) Install one of the available nvidia packages or, if the nvidia driver is already installed, dist-upgrade after adding the -proposed repository. 3) Restart and see if the system boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log [Regression Potential] Low, the packages come from either wily or vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1465706/+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 1421793] Re: intel_pstate is always reported to be set to 'performance'
** Also affects: sysvinit Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1421793 Title: intel_pstate is always reported to be set to 'performance' Status in sysvinit: New Status in linux-lts-utopic package in Ubuntu: New Bug description: as in - cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver intel_pstate cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance performance performance performance performance cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 240 2400187 2400093 2394468 2397281 240 2400093 2401125 In 15.04 it is reported at performance at login, then switches to powersave after a min. or so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 13 14:13:57 2015 InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.2) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/sysvinit/+bug/1421793/+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 1421793] Re: intel_pstate is always reported to be set to 'performance'
The ondemand script in 14.04.2 seems wrong, attached If replaced by one in 15.04 then seems to work a bit better, ie. it adds *powersave*) GOVERNOR="powersave" break ** Attachment added: "ondemand" https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1421793/+attachment/4319214/+files/ondemand -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1421793 Title: intel_pstate is always reported to be set to 'performance' Status in linux-lts-utopic package in Ubuntu: New Bug description: as in - cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver intel_pstate cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance performance performance performance performance cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 240 2400187 2400093 2394468 2397281 240 2400093 2401125 In 15.04 it is reported at performance at login, then switches to powersave after a min. or so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 13 14:13:57 2015 InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.2) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1421793/+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 1421793] Re: intel_pstate is always reported to be set to 'performance'
*-cpu description: CPU product: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz vendor: Intel Corp. physical id: 4 bus info: cpu@0 version: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz serial: To Be Filled By O.E.M. slot: U3E1 size: 3072MHz capacity: 3072MHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cpufreq configuration: cores=4 enabledcores=4 threads=8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1421793 Title: intel_pstate is always reported to be set to 'performance' Status in linux-lts-utopic package in Ubuntu: New Bug description: as in - cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver intel_pstate cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance performance performance performance performance cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 240 2400187 2400093 2394468 2397281 240 2400093 2401125 In 15.04 it is reported at performance at login, then switches to powersave after a min. or so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 13 14:13:57 2015 InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.2) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1421793/+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 1421793] Re: intel_pstate is always reported to be set to 'performance'
** Attachment added: "i7z console" https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1421793/+attachment/4318922/+files/Screenshot%20from%202015-02-13%2014%3A17%3A23.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1421793 Title: intel_pstate is always reported to be set to 'performance' Status in linux-lts-utopic package in Ubuntu: New Bug description: as in - cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver intel_pstate cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance performance performance performance performance cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 240 2400187 2400093 2394468 2397281 240 2400093 2401125 In 15.04 it is reported at performance at login, then switches to powersave after a min. or so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 13 14:13:57 2015 InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.2) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1421793/+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 1421793] [NEW] intel_pstate is always reported to be set to 'performance'
Public bug reported: as in - cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver intel_pstate cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance performance performance performance performance cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 240 2400187 2400093 2394468 2397281 240 2400093 2401125 In 15.04 it is reported at performance at login, then switches to powersave after a min. or so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 13 14:13:57 2015 InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.2) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1421793 Title: intel_pstate is always reported to be set to 'performance' Status in linux-lts-utopic package in Ubuntu: New Bug description: as in - cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver intel_pstate cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance performance performance performance performance cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 240 2400187 2400093 2394468 2397281 240 2400093 2401125 In 15.04 it is reported at performance at login, then switches to powersave after a min. or so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 13 14:13:57 2015 InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.2) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1421793/+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 1401960] Re: usb 3 hdd drive takes inordinate time to become available after attaching
** Changed in: linux (Ubuntu) Status: Expired => 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/1401960 Title: usb 3 hdd drive takes inordinate time to become available after attaching Status in linux package in Ubuntu: New Bug description: Test case: Boot up, log in attach a usb 3 hdd drive (type that doesn't have it's own power supply What happens: Takes about 30 -35 sec. before the drive shows in nautilus & unity launcher What's expected: drive should show in a sec. or less ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2152 F pulseaudio /dev/snd/controlC1: doug 2152 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:10:14 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401960/+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
Re: [Kernel-packages] [Bug 1401980] Re: Usb 3 hdd drives cannot be powered off in any manner
On 12/14/2014 12:10 AM, Christopher M. Penalver wrote: > Doug McMahon, did this problem not occur in a release prior to Trusty? > I did not personally have a usb 3 external hdd prior to 14.04 There are quite a number of bug reports concerning the 'auto remounting' of usb hdd drives going back quite some time. One example - https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085 The points here are - Only happens with usb 3 hdd's Only happens with usb 3 when attached to a usb 3 port The option's on these drives aren't consistent - Safely Remove only when attaching after login (- this option fails it's purpose Unmount only when booting up with drive attached or after a log out in with drive attached (- this option works And there is no way to power of the device when attached to a usb 3 port (other than going to suspend), windows & mac's can. -- 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/1401980 Title: Usb 3 hdd drives cannot be powered off in any manner Status in linux package in Ubuntu: Incomplete Bug description: Other than shutting down or pulling the cord out. May not be a kernel bug, didn't know otherwise.. Test case: boot up, log in attach a usb 3 hdd ( one without external power) to a usb 3 port The option to "Safely Remove" will be available in nautilus & unity launcher icon, click on it What happens: Drive is unmounted, momentarily powered off & then re-powered on ( takes less than a sec. What should happen: drive should be powered off & stay off until re-attached If one connects the drive to a usb 2 port then it will power down To further confuse - If one boots up with the device connected or connecting after login then doing log out/in there is no longer a Safely remove option, only mount or unmount At no time does udisksctl power-off -b /path/to actually work, it acts like first scenario, quickly powered off then right back on. Whether useful don't know- Drive(4): ST500LT012-1DG142 Type: GProxyDrive (GProxyVolumeMonitorUDisks2) ids: unix-device: '/dev/sdd' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] is_media_removable=0 has_media=1 is_media_check_automatic=1 can_poll_for_media=0 can_eject=0 can_start=0 can_stop=0 start_stop_type=shutdown sort_key=01hotplug/1418402194745573 Volume(0): backup Type: GProxyVolume (GProxyVolumeMonitorUDisks2) ids: class: 'device' unix-device: '/dev/sdd1' uuid: '6b1c17a9-f65d-4926-96f8-73702c001b43' label: 'backup' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=1 sort_key=gvfs.time_detected_usec.1418402460356605 Mount(0): backup -> file:///media/doug/backup Type: GProxyMount (GProxyVolumeMonitorUDisks2) default_location=file:///media/doug/backup themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 sort_key=gvfs.time_detected_usec.1418402460358648 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2162 F pulseaudio /dev/snd/controlC1: doug 2162 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:42:32 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.versio
Re: [Kernel-packages] [Bug 1401980] Re: Usb 3 hdd drives cannot be powered off in any manner
On 12/13/2014 04:44 PM, Christopher M. Penalver wrote: > Doug McMahon, did you reformat the drive first before using it, or did > you just pull it out of the box and begin using it? > Formatted created a 30gb partition in ext4 to hold some files @ current permissions, the rest of the drive is currently free -- 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/1401980 Title: Usb 3 hdd drives cannot be powered off in any manner Status in linux package in Ubuntu: Incomplete Bug description: Other than shutting down or pulling the cord out. May not be a kernel bug, didn't know otherwise.. Test case: boot up, log in attach a usb 3 hdd ( one without external power) to a usb 3 port The option to "Safely Remove" will be available in nautilus & unity launcher icon, click on it What happens: Drive is unmounted, momentarily powered off & then re-powered on ( takes less than a sec. What should happen: drive should be powered off & stay off until re-attached If one connects the drive to a usb 2 port then it will power down To further confuse - If one boots up with the device connected or connecting after login then doing log out/in there is no longer a Safely remove option, only mount or unmount At no time does udisksctl power-off -b /path/to actually work, it acts like first scenario, quickly powered off then right back on. Whether useful don't know- Drive(4): ST500LT012-1DG142 Type: GProxyDrive (GProxyVolumeMonitorUDisks2) ids: unix-device: '/dev/sdd' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] is_media_removable=0 has_media=1 is_media_check_automatic=1 can_poll_for_media=0 can_eject=0 can_start=0 can_stop=0 start_stop_type=shutdown sort_key=01hotplug/1418402194745573 Volume(0): backup Type: GProxyVolume (GProxyVolumeMonitorUDisks2) ids: class: 'device' unix-device: '/dev/sdd1' uuid: '6b1c17a9-f65d-4926-96f8-73702c001b43' label: 'backup' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=1 sort_key=gvfs.time_detected_usec.1418402460356605 Mount(0): backup -> file:///media/doug/backup Type: GProxyMount (GProxyVolumeMonitorUDisks2) default_location=file:///media/doug/backup themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 sort_key=gvfs.time_detected_usec.1418402460358648 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2162 F pulseaudio /dev/snd/controlC1: doug 2162 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:42:32 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchp
Re: [Kernel-packages] [Bug 1401980] Re: Usb 3 hdd drives cannot be powered off in any manner
On 12/13/2014 03:43 PM, Christopher M. Penalver wrote: > Doug McMahon, what is the manufacturer and model of the USB hard drive > from the sticker (not from the comment)? > Seagate PN-1e7ana-501 (500 GB) on back of drive http://www.seagate.com/external-hard-drives/portable-hard-drives/standard/backup-plus/ I believe the described behaviour would happen with any of the portable usb 3 drives that power from the usb port -- 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/1401980 Title: Usb 3 hdd drives cannot be powered off in any manner Status in linux package in Ubuntu: Incomplete Bug description: Other than shutting down or pulling the cord out. May not be a kernel bug, didn't know otherwise.. Test case: boot up, log in attach a usb 3 hdd ( one without external power) to a usb 3 port The option to "Safely Remove" will be available in nautilus & unity launcher icon, click on it What happens: Drive is unmounted, momentarily powered off & then re-powered on ( takes less than a sec. What should happen: drive should be powered off & stay off until re-attached If one connects the drive to a usb 2 port then it will power down To further confuse - If one boots up with the device connected or connecting after login then doing log out/in there is no longer a Safely remove option, only mount or unmount At no time does udisksctl power-off -b /path/to actually work, it acts like first scenario, quickly powered off then right back on. Whether useful don't know- Drive(4): ST500LT012-1DG142 Type: GProxyDrive (GProxyVolumeMonitorUDisks2) ids: unix-device: '/dev/sdd' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] is_media_removable=0 has_media=1 is_media_check_automatic=1 can_poll_for_media=0 can_eject=0 can_start=0 can_stop=0 start_stop_type=shutdown sort_key=01hotplug/1418402194745573 Volume(0): backup Type: GProxyVolume (GProxyVolumeMonitorUDisks2) ids: class: 'device' unix-device: '/dev/sdd1' uuid: '6b1c17a9-f65d-4926-96f8-73702c001b43' label: 'backup' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=1 sort_key=gvfs.time_detected_usec.1418402460356605 Mount(0): backup -> file:///media/doug/backup Type: GProxyMount (GProxyVolumeMonitorUDisks2) default_location=file:///media/doug/backup themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 sort_key=gvfs.time_detected_usec.1418402460358648 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2162 F pulseaudio /dev/snd/controlC1: doug 2162 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:42:32 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.ver
[Kernel-packages] [Bug 1401960] Re: usb 3 hdd drive takes inordinate time to become available after attaching
/dev/sdd:
ATA device, with non-removable media
Model Number: ST500LT012-1DG142
Serial Number: S3P8W8YR
Firmware Revision: 0001SDM1
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions,
SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x0029)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 268435455
LBA48 user addressable sectors: 976773168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 476940 MBytes
device size with M = 1000*1000: 500107 MBytes (500 GB)
cache/buffer size = unknown
Form Factor: 2.5 inch
Nominal Media Rotation Rate: 5400
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128
Recommended acoustic management value: 208, current value: 0
DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
*SMART feature set
Security Mode feature set
*Power Management feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*NOP cmd
*DOWNLOAD_MICROCODE
*Advanced Power Management feature set
Power-Up In Standby feature set
*SET_FEATURES required to spinup after power up
SET_MAX security extension
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*WRITE_{DMA|MULTIPLE}_FUA_EXT
*64-bit World wide name
*IDLE_IMMEDIATE with UNLOAD
*Write-Read-Verify feature set
*WRITE_UNCORRECTABLE_EXT command
*{READ,WRITE}_DMA_EXT_GPL commands
*Segmented DOWNLOAD_MICROCODE
*Gen1 signaling speed (1.5Gb/s)
*Gen2 signaling speed (3.0Gb/s)
*Gen3 signaling speed (6.0Gb/s)
*Native Command Queueing (NCQ)
*Host-initiated interface power management
*Phy event counters
*Idle-Unload when NCQ is active
*READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
Device-initiated interface power management
*Software settings preservation
*SMART Command Transport (SCT) feature set
*SCT Write Same (AC2)
*SCT Features Control (AC4)
*SCT Data Tables (AC5)
unknown 206[12] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
98min for SECURITY ERASE UNIT. 98min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c50074dfa560
NAA : 5
IEEE OUI: 000c50
Unique ID : 074dfa560
Checksum: correct
--
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/1401960
Title:
usb 3 hdd drive takes inordinate time to become available after
attaching
Status in linux package in Ubuntu:
Incomplete
Bug description:
Test case:
Boot up, log in
attach a usb 3 hdd drive (type that doesn't have it's own power supply
What happens:
Takes about 30 -35 sec. before the drive shows in nautilus & unity launcher
What's expected:
drive should show in a sec. or less
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.15-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
[Kernel-packages] [Bug 1401980] Re: Usb 3 hdd drives cannot be powered off in any manner
/dev/sdd:
ATA device, with non-removable media
Model Number: ST500LT012-1DG142
Serial Number: S3P8W8YR
Firmware Revision: 0001SDM1
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions,
SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x0029)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 268435455
LBA48 user addressable sectors: 976773168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 476940 MBytes
device size with M = 1000*1000: 500107 MBytes (500 GB)
cache/buffer size = unknown
Form Factor: 2.5 inch
Nominal Media Rotation Rate: 5400
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128
Recommended acoustic management value: 208, current value: 0
DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
*SMART feature set
Security Mode feature set
*Power Management feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*NOP cmd
*DOWNLOAD_MICROCODE
*Advanced Power Management feature set
Power-Up In Standby feature set
*SET_FEATURES required to spinup after power up
SET_MAX security extension
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*WRITE_{DMA|MULTIPLE}_FUA_EXT
*64-bit World wide name
*IDLE_IMMEDIATE with UNLOAD
*Write-Read-Verify feature set
*WRITE_UNCORRECTABLE_EXT command
*{READ,WRITE}_DMA_EXT_GPL commands
*Segmented DOWNLOAD_MICROCODE
*Gen1 signaling speed (1.5Gb/s)
*Gen2 signaling speed (3.0Gb/s)
*Gen3 signaling speed (6.0Gb/s)
*Native Command Queueing (NCQ)
*Host-initiated interface power management
*Phy event counters
*Idle-Unload when NCQ is active
*READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
Device-initiated interface power management
*Software settings preservation
*SMART Command Transport (SCT) feature set
*SCT Write Same (AC2)
*SCT Features Control (AC4)
*SCT Data Tables (AC5)
unknown 206[12] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
98min for SECURITY ERASE UNIT. 98min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c50074dfa560
NAA : 5
IEEE OUI: 000c50
Unique ID : 074dfa560
Checksum: correct
--
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/1401980
Title:
Usb 3 hdd drives cannot be powered off in any manner
Status in linux package in Ubuntu:
Incomplete
Bug description:
Other than shutting down or pulling the cord out.
May not be a kernel bug, didn't know otherwise..
Test case:
boot up, log in
attach a usb 3 hdd ( one without external power) to a usb 3 port
The option to "Safely Remove" will be available in nautilus & unity launcher
icon, click on it
What happens:
Drive is unmounted, momentarily powered off & then re-powered on ( takes less
than a sec.
What should happen:
drive should be powered off & stay off until re-attached
If one connects the drive to a usb 2 port then it will power
[Kernel-packages] [Bug 1401980] Re: Usb 3 hdd drives cannot be powered off in any manner
** Description changed: Other than shutting down or pulling the cord out. May not be a kernel bug, didn't know otherwise.. Test case: boot up, log in - attach a usb 3 hdd ( one without externel power + attach a usb 3 hdd ( one without external power) to a usb 3 port The option to "Safely Remove" will be available in nautilus & unity launcher icon, click on it - What happens: - Drive is unmounted, momentarily powered off & then repowered on ( takes less than a sec. + What happens: + Drive is unmounted, momentarily powered off & then re-powered on ( takes less than a sec. What should happen: drive should be powered off & stay off until re-attached If one connects the drive to a usb 2 port then it will power down - To further confuse - - If one boots up with the device connected or after connecting after login then log out/in there is no longer a Safely remove option, only mount or unmount + To further confuse - + If one boots up with the device connected or connecting after login then doing log out/in there is no longer a Safely remove option, only mount or unmount At no time does udisksctl power-off -b /path/to actually work, it acts like first scenario, quickly powered off then right back on. Whether useful don't know- Drive(4): ST500LT012-1DG142 - Type: GProxyDrive (GProxyVolumeMonitorUDisks2) - ids: -unix-device: '/dev/sdd' - themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] - symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] - is_media_removable=0 - has_media=1 - is_media_check_automatic=1 - can_poll_for_media=0 - can_eject=0 - can_start=0 - can_stop=0 - start_stop_type=shutdown - sort_key=01hotplug/1418402194745573 - Volume(0): backup - Type: GProxyVolume (GProxyVolumeMonitorUDisks2) - ids: - class: 'device' - unix-device: '/dev/sdd1' - uuid: '6b1c17a9-f65d-4926-96f8-73702c001b43' - label: 'backup' - themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] - symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] - can_mount=1 - can_eject=0 - should_automount=1 - sort_key=gvfs.time_detected_usec.1418402460356605 - Mount(0): backup -> file:///media/doug/backup - Type: GProxyMount (GProxyVolumeMonitorUDisks2) - default_location=file:///media/doug/backup - themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] - symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] - can_unmount=1 - can_eject=0 - is_shadowed=0 - sort_key=gvfs.time_detected_usec.1418402460358648 + Type: GProxyDrive (GProxyVolumeMonitorUDisks2) + ids: + unix-device: '/dev/sdd' + themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] + symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] + is_media_removable=0 + has_media=1 + is_media_check_automatic=1 + can_poll_for_media=0 + can_eject=0 + can_start=0 + can_stop=0 + start_stop_type=shutdown + sort_key=01hotplug/1418402194745573 + Volume(0): backup + Type: GProxyVolume (GProxyVolumeMonitorUDisks2) + ids: + class: 'device' + unix-device: '/dev/sdd1' + uuid: '6b1c17a9-f65d-4926-96f8-73702c001b43' + label: 'backup' + themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] + symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] + can_mount=1 + can_eject=0 + should_automount=1 + sort_key=gvfs.time_detected_usec.1418402460356605 + Mount(0): backup -> file:///media/doug/backup + Type: GProxyMount (GProxyVolumeMonitorUDisks2) + default_location=file:///media/doug/backup + themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] + symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] + can_unmount=1 + can_eject=0 + is_shadowed=0 + sort_key=gvfs.time_detected_usec.1418402460358648 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: doug 2162 F pulseaudio - /dev/snd/controlC1: doug 2162 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: doug
[Kernel-packages] [Bug 1401980] [NEW] Usb 3 hdd drives cannot be powered off in any manner
Public bug reported: Other than shutting down or pulling the cord out. May not be a kernel bug, didn't know otherwise.. Test case: boot up, log in attach a usb 3 hdd ( one without externel power The option to "Safely Remove" will be available in nautilus & unity launcher icon, click on it What happens: Drive is unmounted, momentarily powered off & then repowered on ( takes less than a sec. What should happen: drive should be powered off & stay off until re-attached If one connects the drive to a usb 2 port then it will power down To further confuse - If one boots up with the device connected or after connecting after login then log out/in there is no longer a Safely remove option, only mount or unmount At no time does udisksctl power-off -b /path/to actually work, it acts like first scenario, quickly powered off then right back on. Whether useful don't know- Drive(4): ST500LT012-1DG142 Type: GProxyDrive (GProxyVolumeMonitorUDisks2) ids: unix-device: '/dev/sdd' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] is_media_removable=0 has_media=1 is_media_check_automatic=1 can_poll_for_media=0 can_eject=0 can_start=0 can_stop=0 start_stop_type=shutdown sort_key=01hotplug/1418402194745573 Volume(0): backup Type: GProxyVolume (GProxyVolumeMonitorUDisks2) ids: class: 'device' unix-device: '/dev/sdd1' uuid: '6b1c17a9-f65d-4926-96f8-73702c001b43' label: 'backup' themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=1 sort_key=gvfs.time_detected_usec.1418402460356605 Mount(0): backup -> file:///media/doug/backup Type: GProxyMount (GProxyVolumeMonitorUDisks2) default_location=file:///media/doug/backup themed icons: [drive-harddisk-usb] [drive-harddisk] [drive] symbolic themed icons: [drive-harddisk-usb-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-usb] [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 sort_key=gvfs.time_detected_usec.1418402460358648 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2162 F pulseaudio /dev/snd/controlC1: doug 2162 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:42:32 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty vivid ** Tags added: trusty -- 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/1401980 Title: Usb 3 hdd drives cannot be powered off in any manner Status in linux package in Ubuntu: Confirmed Bug description: Other than shutting down or pulling the cord out. May not be a kernel bug, didn't know otherwise.. Test case: boot up, log in attach a usb 3 hdd ( one without externel power The option to "Safely Remove" will be available in nautilus & unity launcher icon, click on it What happens: Drive is unmounted, momentarily powered off & then repowered on ( takes less than a sec. What should happen: drive should be powered off & stay off until re-attached If one connects the drive to a usb 2 port
[Kernel-packages] [Bug 1401960] [NEW] usb 3 hdd drive takes inordinate time to become available after attaching
Public bug reported: Test case: Boot up, log in attach a usb 3 hdd drive (type that doesn't have it's own power supply What happens: Takes about 30 -35 sec. before the drive shows in nautilus & unity launcher What's expected: drive should show in a sec. or less ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2152 F pulseaudio /dev/snd/controlC1: doug 2152 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:10:14 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1401960 Title: usb 3 hdd drive takes inordinate time to become available after attaching Status in linux package in Ubuntu: New Bug description: Test case: Boot up, log in attach a usb 3 hdd drive (type that doesn't have it's own power supply What happens: Takes about 30 -35 sec. before the drive shows in nautilus & unity launcher What's expected: drive should show in a sec. or less ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2152 F pulseaudio /dev/snd/controlC1: doug 2152 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:10:14 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401960/+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 1401960] Re: usb 3 hdd drive takes inordinate time to become available after attaching
-- 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/1401960 Title: usb 3 hdd drive takes inordinate time to become available after attaching Status in linux package in Ubuntu: New Bug description: Test case: Boot up, log in attach a usb 3 hdd drive (type that doesn't have it's own power supply What happens: Takes about 30 -35 sec. before the drive shows in nautilus & unity launcher What's expected: drive should show in a sec. or less ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2152 F pulseaudio /dev/snd/controlC1: doug 2152 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:10:14 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401960/+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 1401960] Re: usb 3 hdd drive takes inordinate time to become available after attaching
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401960/+attachment/4279724/+files/syslog -- 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/1401960 Title: usb 3 hdd drive takes inordinate time to become available after attaching Status in linux package in Ubuntu: New Bug description: Test case: Boot up, log in attach a usb 3 hdd drive (type that doesn't have it's own power supply What happens: Takes about 30 -35 sec. before the drive shows in nautilus & unity launcher What's expected: drive should show in a sec. or less ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 2152 F pulseaudio /dev/snd/controlC1: doug 2152 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 12 11:10:14 2014 InstallationDate: Installed on 2014-11-16 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) MachineType: LENOVO 20217 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=91a821ed-7160-439b-8519-939faa93bf90 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.139 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401960/+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 1356357] Re: utopic .iso 20140813 boots to wallpaper no panels
If on intel then you may want to check this report (and I have the new compiz... https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1356683 -- 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/1356357 Title: utopic .iso 20140813 boots to wallpaper no panels Status in “linux” package in Ubuntu: Fix Committed Bug description: zsync'd utopic today, booted and all that appears is wallpaper. No panels, no icons, no applets, nothing. Ctrl-Alt-F1 did ubuntu-bug linux, Copied /tmp/apport* to a partition on the hard drive then did: ubuntu-bug apport* to report this bug. model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-7-generic 3.16.0-7.12 ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0 Uname: Linux 3.16.0-7-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CasperVersion: 1.341 Date: Wed Aug 13 12:48:38 2014 LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140813) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356357/+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 1327735] Re: Sync libmpc 2:0.1~r459-4.1 (universe) from Debian unstable (main)
What you're providing now is broken, the new debian source will fix
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974
https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1310554
** Bug watch added: Debian Bug tracker #665974
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libmpc in Ubuntu.
https://bugs.launchpad.net/bugs/1327735
Title:
Sync libmpc 2:0.1~r459-4.1 (universe) from Debian unstable (main)
Status in “libmpc” package in Ubuntu:
Incomplete
Bug description:
Please sync libmpc 2:0.1~r459-4.1 (universe) from Debian unstable
(main)
Explanation of the Ubuntu delta and why it can be dropped:
* Drop 99_autoreconf.patch, as we are now autoreconfing through CDBS.
* debian/patches/04_link-order.patch: Link against -lm only after the
static libraries that use math functions. Fixes the build failure
from --as-needed, which enforces strict order.
* debian/patches/99_autoreconf.patch: Regenerate by autoconf -i and
removing the cache directory afterwards.
All fixed in debian
Changelog entries since current utopic version 2:0.1~r459-1ubuntu3:
libmpc (2:0.1~r459-4.1) unstable; urgency=low
[ Hideki Yamane ]
* Non-maintainer upload.
- auto detect aclocal/automake/autoconf version (Closes: #713209)
- include autoreconf.mk to add "config/compile" file
* debian/control
- add "Build-Depends: dh-autoreconf" to provide above autoreconf.mk
* debian/patches
- add add_subdir-objects.patch for automake
-- Neil Williams Sat, 22 Mar 2014 14:25:56
+
libmpc (2:0.1~r459-4) unstable; urgency=medium
* Team upload.
* Bump urgency to medium as RC #665974 affects wheezy.
* Avoid re-define mpc_uint8_t, MPC_SAMPLE_FORMAT and mpc_int16_t in
libmpcdec/requant.h, they are defined somewhere else in the code;
patch taken from upstream trunk. (Closes: #665974)
Thanks to Han Boetes for the report and Fabian Greffrath for
traging the bug.
-- Alessio Treglia Thu, 21 Jun 2012 09:37:38
+0200
libmpc (2:0.1~r459-3) unstable; urgency=low
* Team upload.
* Fix buildsystem to avoid FTBFS with --as-needed.
Thanks to Stefan Potyra for the patch. (Closes: #606829)
* Run autotools' stuff before configure to regenerate the buildsystem.
- Drop 99_autoreconf.patch.
- Build-Depends on gnulib, auto{conf,make} libtool.
* Bump Standards.
-- Alessio Treglia Sun, 17 Jun 2012 21:05:37
+0200
libmpc (2:0.1~r459-2) unstable; urgency=low
* Team upload.
* Update maintainer information.
* Add watch file.
* Build for Multiarch.
* Bump Standards.
-- Alessio Treglia Wed, 15 Feb 2012 01:11:57
+0100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1327735/+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 1324306] Re: Fails to update or if removed install: update-rc.d: error: insserv rejected the script header
** Changed in: bluez (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1324306 Title: Fails to update or if removed install: update-rc.d: error: insserv rejected the script header Status in “bluez” package in Ubuntu: Invalid Bug description: On 14.10 - Preparing to unpack .../bluez_4.101-0ubuntu15_amd64.deb ... Unpacking bluez (4.101-0ubuntu15) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up bluez (4.101-0ubuntu15) ... insserv: Service dbus has to be enabled to start service bluetooth insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package bluez (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: bluez E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 28 19:36:10 2014 InstallationDate: Installed on 2014-05-28 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1324306/+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 1324306] Re: Fails to update or if removed install: update-rc.d: error: insserv rejected the script header
** No longer affects: unity-control-center -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1324306 Title: Fails to update or if removed install: update-rc.d: error: insserv rejected the script header Status in “bluez” package in Ubuntu: New Bug description: On 14.10 - Preparing to unpack .../bluez_4.101-0ubuntu15_amd64.deb ... Unpacking bluez (4.101-0ubuntu15) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up bluez (4.101-0ubuntu15) ... insserv: Service dbus has to be enabled to start service bluetooth insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package bluez (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: bluez E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 28 19:36:10 2014 InstallationDate: Installed on 2014-05-28 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1324306/+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 1324306] [NEW] Fails to update or if removed install: update-rc.d: error: insserv rejected the script header
Public bug reported: On 14.10 - Preparing to unpack .../bluez_4.101-0ubuntu15_amd64.deb ... Unpacking bluez (4.101-0ubuntu15) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up bluez (4.101-0ubuntu15) ... insserv: Service dbus has to be enabled to start service bluetooth insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package bluez (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: bluez E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 28 19:36:10 2014 InstallationDate: Installed on 2014-05-28 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-control-center Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Also affects: unity-control-center Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1324306 Title: Fails to update or if removed install: update-rc.d: error: insserv rejected the script header Status in Unity Control Center: New Status in “bluez” package in Ubuntu: New Bug description: On 14.10 - Preparing to unpack .../bluez_4.101-0ubuntu15_amd64.deb ... Unpacking bluez (4.101-0ubuntu15) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up bluez (4.101-0ubuntu15) ... insserv: Service dbus has to be enabled to start service bluetooth insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package bluez (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: bluez E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 28 19:36:10 2014 InstallationDate: Installed on 2014-05-28 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1324306/+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 1310554] Re: Regression: breaks mpc decoding with some players
This bug isn't related to ffmpeg vs libav, the issue is in libmpc vlc from the ppa & gmusicbrowser work because the ppa also has a patched libmpcdec6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmpc in Ubuntu. https://bugs.launchpad.net/bugs/1310554 Title: Regression: breaks mpc decoding with some players Status in “libmpc” package in Ubuntu: Confirmed Bug description: At least 2 players - gmusicbrowser vlc Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1310554/+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 1310554] Re: Regression: breaks mpc decoding with some players
** Description changed: - At least 1 player - + At least 2 players - gmusicbrowser + vlc Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmpc in Ubuntu. https://bugs.launchpad.net/bugs/1310554 Title: Regression: breaks mpc decoding with some players Status in “libmpc” package in Ubuntu: Confirmed Bug description: At least 2 players - gmusicbrowser vlc Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1310554/+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 1310554] Re: Regression: breaks mpc decoding with some players
** Description changed: - At least 2 players - moc + At least 1 player - gmusicbrowser Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmpc in Ubuntu. https://bugs.launchpad.net/bugs/1310554 Title: Regression: breaks mpc decoding with some players Status in “libmpc” package in Ubuntu: New Bug description: At least 1 player - gmusicbrowser Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1310554/+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 1310554] [NEW] Regression: breaks mpc decoding with some players
Public bug reported: At least 2 players moc gmusicbrowser Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libmpc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: At least 2 players moc gmusicbrowser - Fixed in Debian, probably from either 1001_missing_extern_kw.patch + Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: - gcc-4.9-base 4.9-20140406-0ubuntu1 - libc6 2.19-0ubuntu6 - libgcc1 1:4.9-20140406-0ubuntu1 - multiarch-support 2.19-0ubuntu6 + gcc-4.9-base 4.9-20140406-0ubuntu1 + libc6 2.19-0ubuntu6 + libgcc1 1:4.9-20140406-0ubuntu1 + multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmpc in Ubuntu. https://bugs.launchpad.net/bugs/1310554 Title: Regression: breaks mpc decoding with some players Status in “libmpc” package in Ubuntu: New Bug description: At least 2 players moc gmusicbrowser Fixed in Debian, probably from 1001_missing_extern_kw.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665974 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmpcdec6 2:0.1~r459-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 06:39:45 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-15 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414) SourcePackage: libmpc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1310554/+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 1191426] Re: logout is slow, profiling reveals lots of CPU time in nouveau_connector_detect
At least here on previously affected machine this is longer an issue, log outs are back to about 1 sec. or so -- 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/1191426 Title: logout is slow, profiling reveals lots of CPU time in nouveau_connector_detect Status in One Hundred Paper Cuts: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Triaged Status in “xserver-xorg-video-nouveau” package in Ubuntu: Invalid Bug description: I'm running Ubuntu 13.10 (Saucy) on a MacbookPro9,1, which has both an Nvidia GeForce GT 650M and an integrated Intel HD Graphics 4000 controller. I boot with EFI and use the Nouveau driver. On this machine logging out is slow, taking maybe 10 seconds or so. 'top' shows that the X server process uses lots of CPU during logout. I ran sysprof and it attributes much of the CPU time to nouveau_connector_detect, called via the following: system_call_fastpath [48.98%] sys_ioctl [41.90%] do_vfs_ioctl [41.87%] drm_ioctl [41.47%] drm_mode_getconnector [34.14%] drm_helper_probe_single_connector_modes [34.14%] nouveau_connector_detect [28.84%] nouveau_connector_detect_lvds [3.83%] intel_crt_detect [1.48%] The percentages above are of the total CPU time used in the shutdown sequence, so I think several seconds of time is being spent in the path above. That doesn't seem right. --- ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adam 1744 F pulseaudio /dev/snd/controlC0: adam 1744 F pulseaudio CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.30+bdcom, 3.9.0-4-generic, x86_64: installed bcmwl, 6.30.223.30+bdcom, 3.9.0-5-generic, x86_64: installed bcmwl, 6.30.223.30+bdcom, 3.9.0-6-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fb] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fc] HibernationDevice: RESUME=UUID=97a27f76-3baf-42fe-b6fc-5bee91c831ca InstallationDate: Installed on 2013-06-10 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130609) MachineType: Apple Inc. MacBookPro9,1 MarkForUpload: True NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=3ca362e9-34d3-4c77-8a5a-07ecf66b8619 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 RelatedPackageVersions: linux-restricted-modules-3.9.0-6-generic N/A linux-backports-modules-3.9.0-6-generic N/A linux-firmware 1.109 Tags: saucy saucy ubuntu reproducible Uname: Linux 3.9.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B08.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-4B7AC7E43945597E dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B7AC7E43945597E dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E: dmi.product.name: MacBookPro9,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu2 version.xserver-
[Kernel-packages] [Bug 1195811] Re: nouveau: Abnormally high FPS and tearing (no vsync) on natively mir testing demo-clients.
While the 2 commits do eliminate tearing here with nv50 that was brought back when using xmir/u-s-c, considering the current state of bug fixing it would be good not to create yet another bug in compiz For 13.10 not using u-s-c is probably the best choice for users concerned about tearing & who have none with the current X, mesa, compiz & unity Also to note that the commits did a decent job of eliminating tearing in gnomeshell/clutter, 100% gone with xmir/u-s-c, not quite 100% with just the commits (no xmir, u-s-c Though Gs users can eliminate tearing completely with a simple env for clutter If those commits are going to be applied it would be useful to provide a testing ppa to see how they do with other nvidia hardware & if they create any further issues other than noted previously with compiz. -- 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/1195811 Title: nouveau: Abnormally high FPS and tearing (no vsync) on natively mir testing demo-clients. Status in Mir: Triaged Status in “linux” package in Ubuntu: In Progress Bug description: I installed Ubuntu 13.10 (yesterday) in order to test Xmir and Mir natively (examples-clients). Xmirg worked flawlessly. The only "problem" was the duplicate mouse cursor(s). But I noticed an abnormally high FPS in some clients demo when I tested Mir natively per these instructions http://unity.ubuntu.com/mir/using_mir_on_pc.html I recorded the test case using external camera. Apologies for the quality but you will see the values. http://www.youtube.com/watch?v=zil-lRNlaks I attached an apport.log just for more info if are needed. I'm not a technical guy and I filled this report prompted by @duflu in IRC #ubuntu-mir You can read the mini conversation here. http://irclogs.ubuntu.com/2013/06/28/%23ubuntu-mir.html This test had the same results either if X only was running in VT7 (Video) or Xmir. I hope I helped... in something. Regards NikTh To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1195811/+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
