[Kernel-packages] [Bug 2009672] Re: Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates
Occurs with 5.15.0-75-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: My computer can not show in 1920x1080 mode with 50Hz or 60Hz refresh rate. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes, or even in 1920x1080 mode with 30Hz refresh rate. VGA output works without issues. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. Workaround in 20.04 is to use linux-generic kernel, instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates
** Description changed: My computer can not show in 1920x1080 mode with 50Hz or 60Hz refresh rate. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes, or even in 1920x1080 mode with 30Hz refresh rate. VGA output works without issues. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. + + Workaround in 20.04 is to use linux-generic kernel, instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: My computer can not show in 1920x1080 mode with 50Hz or 60Hz refresh rate. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes, or even in 1920x1080 mode with 30Hz refresh rate. VGA output works without issues. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. Workaround in 20.04 is to use linux-generic kernel, instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates
** Description changed: - System can show image in HDMI output during bootup. I don't know which - mode it is using during bootup. Anyway it can not show image in - 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my - system HDMI is just a Displayport connector with an adapter. xrandr - lists the video modes of the connected HDMI monitor, and it does not - show any error message or non-zero exit status when I enable 1920x1080 - mode in the HDMI output; thereafter xrandr shows the mode is currently - used in the HDMI output, but my monitor/TV does not show such a video - mode. It can still work in 1920x1080i and lower resolution modes. VGA - output works fine. + My computer can not show in 1920x1080 mode with 50Hz or 60Hz refresh + rate. I am using Xubuntu 20.04. In my system HDMI is just a Displayport + connector with an adapter. xrandr lists the video modes of the connected + HDMI monitor, and it does not show any error message or non-zero exit + status when I enable 1920x1080 mode in the HDMI output; thereafter + xrandr shows the mode is currently used in the HDMI output, but my + monitor/TV does not show such a video mode. It can still work in + 1920x1080i and lower resolution modes, or even in 1920x1080 mode with + 30Hz refresh rate. VGA output works without issues. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: My computer can not show in 1920x1080 mode with 50Hz or 60Hz refresh rate. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes, or even in 1920x1080 mode with 30Hz refresh rate. VGA output works without issues. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show the native 1920x1080 mode in HDMI output
Bug occurs with 5.15.0-71-generic, too. ** Summary changed: - Regression: Unable to show the native 1920x1080 mode in HDMI output + Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort output with best refresh rates Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. VGA output works fine. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show the native 1920x1080 mode in HDMI output
$ inxi -G Graphics: Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics driver: i915 v: kernel Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1) v: 4.2 Mesa 21.2.6 It shows that 1920x1080~60Hz mode is on, but the monitor tells it can not show the mode, even if it can with older kernel. Why is this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show the native 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. VGA output works fine. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show the native 1920x1080 mode in HDMI output
** Summary changed: - Regression: Unable to show 1920x1080 mode in HDMI output + Regression: Unable to show the native 1920x1080 mode in HDMI output -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show the native 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. VGA output works fine. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show 1920x1080 mode in HDMI output
Possible dubplicate: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012953 ** Summary changed: - Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics + Regression: Unable to show 1920x1080 mode in HDMI output -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. VGA output works fine. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics
** Description changed: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video - mode. It can still work in 1920x1080i and lower resolution modes. + mode. It can still work in 1920x1080i and lower resolution modes. VGA + output works fine. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. VGA output works fine. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2012953] Re: No HDMI with Intel Iris Xe Graphics
This could be a duplicate of the bug I reported: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-5.15/+bug/2009672 Did you try setting a lower resolution? -- 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/2012953 Title: No HDMI with Intel Iris Xe Graphics Status in linux package in Ubuntu: Incomplete Bug description: Hi I have a XMG Focus 17 laptop. i7-12700H with Intel Iris Xe Graphics Nvidia RTX 3060. Dualboot LinuxMint 21.1 (based on Ubuntu 22.04) / Windows 10 Kernel 5.15.0-67-generic HDMI output (2nd screen, TV) works fine with : -Windows -LinuxMint with Nvidia card activated BUT don't work with : LinuxMint with Intel Graphic GPU. I have the same pb on another laptop DELL VOSTRO 5630 (no Nvidia, only Intel GPU), running LinuxMint 21.1 too. So the issue comes from the Intel Iris GPU. My hdmi wires are OK. Here are some command lines ouputs : $ inxi -bG System: Host: vincent-XMG-FOCUS-M22 Kernel: 5.15.0-67-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Laptop System: SchenkerGmbH product: XMG FOCUS (M22) v: N/A serial: Mobo: NB01 model: NP5x_NP6x_NP7xPNP serial: UEFI: INSYDE v: 1.07.09RTR2 date: 12/01/2022 Battery: ID-1: BAT0 charge: 51.3 Wh (100.0%) condition: 51.3/52.5 Wh (97.8%) CPU: Info: 14-core (6-mt/8-st) 12th Gen Intel Core i7-12700H [MST AMCP] speed (MHz): avg: 715 min/max: 400/4600:4700:3500 Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: N/A Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~144Hz OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.2.5 Network: Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi Device-2: Intel Ethernet I219-V driver: e1000e Drives: Local Storage: total: 2.73 TiB used: 1.13 TiB (41.5%) Info: Processes: 386 Uptime: 3h 12m Memory: 15.34 GiB used: 3.21 GiB (20.9%) Shell: Bash inxi: 3.3.13 --- $ grep . /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-DP-3/status:disconnected /sys/class/drm/card0-DP-4/status:disconnected /sys/class/drm/card0-eDP-1/status:connected Thanks a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012953/+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 2009672] Re: Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics
** Summary changed: - Regression: Unable to show 1920x1080 mode in HDMI output + Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. VGA output works fine. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show 1920x1080 mode in HDMI output
Bug occurs with 5.15.0-69-generic, too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] Re: Regression: Unable to show 1920x1080 mode in HDMI output
** Summary changed: - Unable to show 1920x1080 mode in HDMI output + Regression: Unable to show 1920x1080 mode in HDMI output -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2009672] [NEW] Unable to show 1920x1080 mode in HDMI output
Public bug reported: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) ** Affects: linux-signed-hwe-5.15 (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 linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Unable to show 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2000313] Re: System fails to suspend sometimes
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2000313 Title: System fails to suspend sometimes Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Does not enter suspend state successfully sometimes and can not resume. Must do shutdown by button then. Might have something to do with Audio Kontrol 1 -audio adapter of which I have reported a separate bug 1855678. However, I succeed to suspend-resume many times, if I unbind the device before suspending by writing to /sys/bus/usb/drivers/usb/unbind. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Dec 22 13:54:59 2022 InstallationDate: Installed on 2019-12-05 (1112 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (895 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2000313/+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 2000313] Re: System fails to suspend sometimes
** Attachment added: "journalctl extract in case suspend success" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2000313/+attachment/5637198/+files/success -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2000313 Title: System fails to suspend sometimes Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Does not enter suspend state successfully sometimes and can not resume. Must do shutdown by button then. Might have something to do with Audio Kontrol 1 -audio adapter of which I have reported a separate bug 1855678. However, I succeed to suspend-resume many times, if I unbind the device before suspending by writing to /sys/bus/usb/drivers/usb/unbind. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Dec 22 13:54:59 2022 InstallationDate: Installed on 2019-12-05 (1112 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (895 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2000313/+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 2000313] [NEW] System fails to suspend sometimes
Public bug reported: Does not enter suspend state successfully sometimes and can not resume. Must do shutdown by button then. Might have something to do with Audio Kontrol 1 -audio adapter of which I have reported a separate bug 1855678. However, I succeed to suspend-resume many times, if I unbind the device before suspending by writing to /sys/bus/usb/drivers/usb/unbind. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Dec 22 13:54:59 2022 InstallationDate: Installed on 2019-12-05 (1112 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (895 days ago) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "journalctl extract in case suspend fails" https://bugs.launchpad.net/bugs/2000313/+attachment/5637194/+files/fail -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2000313 Title: System fails to suspend sometimes Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Does not enter suspend state successfully sometimes and can not resume. Must do shutdown by button then. Might have something to do with Audio Kontrol 1 -audio adapter of which I have reported a separate bug 1855678. However, I succeed to suspend-resume many times, if I unbind the device before suspending by writing to /sys/bus/usb/drivers/usb/unbind. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Dec 22 13:54:59 2022 InstallationDate: Installed on 2019-12-05 (1112 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (895 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2000313/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Description changed: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. + Workaround: + Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: jarnos 1175 F pulseaudio - /dev/snd/controlC0: jarnos 1175 F pulseaudio - /dev/snd/controlC1: jarnos 1175 F pulseaudio - /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: jarnos 1175 F pulseaudio + /dev/snd/controlC0: jarnos 1175 F pulseaudio + /dev/snd/controlC1: jarnos 1175 F pulseaudio + /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: - lono wireless extensions. - - eno1 no wireless extensions. + lono wireless extensions. + + eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.3.0-24-generic N/A - linux-backports-modules-5.3.0-24-generic N/A - linux-firmware1.183.2 + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.183.2 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. Workaround: Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018
[Kernel-packages] [Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Still present in 5.13.0-27-generic. -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. Workaround: Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1922562] Re: Resume from suspend to RAM fails
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Worked with nvidia-340 driver which is no more updated. - When I resume, nothing works. Macbook keyboard lights are on, but - otherwise the machine seems dead. Power button reboot needed. + When I resume, nothing works. Macbook keyboard lights are on, but I get + no response from the machine. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails Status in linux package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: New Bug description: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but I get no response from the machine. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922562/+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 1917265] Re: Suspending to RAM freezes computer
Well after some kernel update it may be that Nvidia driver does not work anymore so I would have to use nouveau or another card.. -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] Re: Suspending to RAM freezes computer
I switched to nvidia-340 driver (via "Additional Drivers"), rebooted and tested few times that suspend-resume works. -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] Re: Suspending to RAM freezes computer
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+attachment/5471858/+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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] Re: Suspending to RAM freezes computer
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+attachment/5471857/+files/kern.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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] Re: Suspending to RAM freezes computer
I have been using this computer only occasionally. It seems that with 5.4.0-65-generic and later I have had this problem more frequently, but I had this bug problem few times in May 2020, too (or at least I did not resume from suspend), but I had several successful resumes after that (according to journalctl). I wonder, if this could be related to graphics driver? I have been using nouveau instead of nvidia lately. nvidia-340 is no more developed IIRC. -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] Re: Suspending to RAM freezes computer
I tried a couple of times. It does not work no matter which mode I use. -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] Re: Suspending to RAM freezes computer
According to above, exiting suspend has failed only in deep mode, but I wonder why there is one s2idle mode. Maybe later I rub some tests. -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] Re: Suspending to RAM freezes computer
Hi Guilherme, I have mixed result: $ LC_ALL=C sudo journalctl | grep "PM: suspend" | tail -n 17 Sep 22 11:19:52 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend exit Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend entry (s2idle) Sep 22 11:20:36 jarnos-OptiPlex-745 kernel: PM: suspend exit Sep 22 11:21:26 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Sep 22 11:30:00 jarnos-OptiPlex-745 kernel: PM: suspend exit Dec 04 15:53:23 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Dec 04 17:50:48 jarnos-OptiPlex-745 kernel: PM: suspend exit Dec 04 18:40:19 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Dec 04 18:50:02 jarnos-OptiPlex-745 kernel: PM: suspend exit Dec 04 19:35:56 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Dec 05 01:07:52 jarnos-OptiPlex-745 kernel: PM: suspend exit Feb 14 14:52:33 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Feb 20 22:59:47 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Feb 21 14:21:38 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Feb 21 18:43:59 jarnos-OptiPlex-745 kernel: PM: suspend exit Feb 28 23:32:29 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917265] [NEW] Suspending to RAM freezes computer
Public bug reported: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. ** Affects: linux (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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: New Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Oh, do I have to make a different bug report or address this one to another package (which one)? -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Booting mainline kernel did not help. Then I added the kernel parameters for it. ** Attachment added: "journal-5.11.0-051100rc4-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5456252/+files/journal-5.11.0-051100rc4-generic.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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Attachment added: "journalctl -b -1 -k on focal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5453567/+files/journal.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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Tags added: focal -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1880666] Re: Power management: does not suspend
No, I would not waste my time on that. ** Also affects: xfce4-screensaver (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Power management: does not suspend + Suspend does work only after half minute delay. ** Description changed: I am using Xubuntu 20.04. xfce4-session-logout --suspend - exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). - - Reproduceable: sometimes + exits with 0, but suspends only after long delay. This happens only if I have xfce4-screensaver running, even if it is set not to lock screen on suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. ** No longer affects: linux (Ubuntu) -- 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/1880666 Title: Suspend does work only after half minute delay. Status in xfce4-screensaver package in Ubuntu: New Bug description: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but suspends only after long delay. This happens only if I have xfce4-screensaver running, even if it is set not to lock screen on suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1880666/+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 1880666] Re: Power management: does not suspend
I made a couple of tests by Xubuntu Core 20.04 live USB (downloaded from https://unit193.net/xubuntu/core/). First time was by default settings i.e. 'lock screen when system is going to sleep' checked - I think that is not a good default setting for live - and the other time when it was not checked. Both times it did not suspend. The former did blank screen immediately, the other one after delay of several seconds. No keyboard activity did have an effect so I had to use power button. -- 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/1880666 Title: Power management: does not suspend Status in linux package in Ubuntu: Incomplete Bug description: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). Reproduceable: sometimes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880666/+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 1880666] Re: Power management: does not suspend
** Description changed: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). - Reproduceable: at least sometimes; used to work at least sometimes with - this release. + Reproduceable: sometimes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: jarnos 1125 F pulseaudio - /dev/snd/controlC1: jarnos 1125 F pulseaudio - /dev/snd/controlC0: jarnos 1125 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: jarnos 1125 F pulseaudio + /dev/snd/controlC1: jarnos 1125 F pulseaudio + /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: - lono wireless extensions. - - enp3s0no wireless extensions. + lono wireless extensions. + + enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: - linux-restricted-modules-5.4.0-31-generic N/A - linux-backports-modules-5.4.0-31-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-31-generic N/A + linux-backports-modules-5.4.0-31-generic N/A + linux-firmware1.187 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. -- 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/1880666 Title: Power management: does not suspend Status in linux package in Ubuntu: Confirmed Bug description: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). Reproduceable: sometimes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880666/+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 1880666] [NEW] Power management: does not suspend
Public bug reported: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). Reproduceable: at least sometimes; used to work at least sometimes with this release. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. ** Affects: linux (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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1880666 Title: Power management: does not suspend Status in linux package in Ubuntu: New Bug description: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). Reproduceable: at least sometimes; used to work at least sometimes with this release. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880666/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Attachment added: "journalctl -b -1 -k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5311740/+files/journalctl -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1855678] [NEW] Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Public bug reported: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: New Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1814068] Re: Crash/black screen when suspend
How do you know it crashes? -- 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/1814068 Title: Crash/black screen when suspend Status in linux package in Ubuntu: Confirmed Bug description: Suspend does not fully work: The screen goes to black and then crashes. Ctrl+Alt+Del does not work, neither switching to any other tty. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cobolt 2522 F pulseaudio CurrentDesktop: GNOME Date: Thu Jan 31 11:23:51 2019 HibernationDevice: RESUME=/dev/mapper/wisepad--vg-swap_1 MachineType: LENOVO 20HES0FX00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-15 (229 days ago) dmi.bios.date: 07/04/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET77W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET77W(1.52):bd07/04/2018:svnLENOVO:pn20HES0FX00:pvrThinkPadT470:rvnLENOVO:rn20HES0FX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FX00 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814068/+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 1815759] Re: Does not recognize connected HDMI monitor
But hardware acceleration does not work and image flickers in Kodi during playback and in use unlike with nvidia driver. -- 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/1815759 Title: Does not recognize connected HDMI monitor Status in linux package in Ubuntu: Incomplete Bug description: Strandely 'sudo lshw -c video' told nouveau is in use even if xserver- xorg-video-nouveau was not installed. With or without, HDMI does not work unlike with proprietary driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 318243/1281120 files, 2346720/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Feb 13 14:16:02 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-140-generic, x86_64: installed bbswitch, 0.8, 4.4.0-141-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed bbswitch, 0.8, 4.4.0-143-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1179 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Feb 13 14:12:08 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815759/+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 1815759] Re: Does not recognize connected HDMI monitor
I tried in Xubuntu 18.04 with HWE, kernel 4.18.0-16-generic, and I get image on external display via HDMI. xserver-xorg-video-nouveau-hwe-18.04 1:1.0.15-3~18.04.1 -- 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/1815759 Title: Does not recognize connected HDMI monitor Status in linux package in Ubuntu: Incomplete Bug description: Strandely 'sudo lshw -c video' told nouveau is in use even if xserver- xorg-video-nouveau was not installed. With or without, HDMI does not work unlike with proprietary driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 318243/1281120 files, 2346720/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Feb 13 14:16:02 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-140-generic, x86_64: installed bbswitch, 0.8, 4.4.0-141-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed bbswitch, 0.8, 4.4.0-143-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1179 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Feb 13 14:12:08 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815759/+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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Fixed in 340.107-0ubuntu0.16.04.2 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Bug #1819077 ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-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/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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
$ dpkg -l |grep 'linux.*-image.*' ii linux-image-4.4.0-140-generic 4.4.0-140.166 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-141-generic 4.4.0-141.167 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-142-generic 4.4.0-142.168 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-143-generic 4.4.0-143.169 amd64Signed kernel image generic ii linux-image-extra-4.4.0-140-generic 4.4.0-140.166 amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP ii linux-image-extra-4.4.0-141-generic 4.4.0-141.167 amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP ii linux-image-extra-4.4.0-142-generic 4.4.0-142.168 amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP ii linux-image-generic 4.4.0.143.150 amd64Generic Linux kernel image ii linux-signed-image-4.4.0-140-generic4.4.0-140.166 amd64Signed kernel image generic ii linux-signed-image-4.4.0-141-generic4.4.0-141.167 amd64Signed kernel image generic ii linux-signed-image-4.4.0-142-generic4.4.0-142.168 amd64Signed kernel image generic ii linux-signed-image-generic 4.4.0.142.148 amd64Signed Generic Linux kernel image jarnos@jarno-hp8510w:~/.init$ uname -r 4.4.0-143-generic ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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 1764794] Re: signing: only install a signed kernel
Testing this required updating several packages from xenial-proposed In order to install them all I ran this: sudo apt install -t=xenial-proposed linux-signed-generic linux-generic (which is something that is not told in the previous document) In its execution an error occurred; here is an extraction of the part of the output: /etc/kernel/header_postinst.d/dkms: Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.104/build/make.log for more information. Setting up linux-headers-generic (4.4.0.143.150) ... Setting up linux-generic (4.4.0.143.150) ... Processing triggers for linux-image-4.4.0-143-generic (4.4.0-143.169) ... /etc/kernel/postinst.d/dkms: ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-340.0.crash' Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.104/build/make.log for more information. If I would use open source driver nouveu, instead, I could test this, but I would not be able to use HDMI IIRC. Well, I'll try. -- 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 1764794] Re: signing: only install a signed kernel
Is there similar verification needed for 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 262408] Re: SysRq key equivalent needed
** Description changed: MacBook keyboards and other Apple keyboards lack a SysRq key and therefore lack important kernel functionality that is designed to save catastrophic data loss if the computer freezes. An equivalent keystroke should be assigned, for example Fn + Eject, to preserve the functionality of the Magic SysRq key in linux on a Mactel. I believe this is a bug and not a feature request because the current implementation assumes that all keyboards have a SysRq key which is an incorrect assumption and therefore a mistake, or bug. + + Workaround: + https://askubuntu.com/a/896806/21005 -- 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/262408 Title: SysRq key equivalent needed Status in Mactel Support: New Status in linux package in Ubuntu: Confirmed Bug description: MacBook keyboards and other Apple keyboards lack a SysRq key and therefore lack important kernel functionality that is designed to save catastrophic data loss if the computer freezes. An equivalent keystroke should be assigned, for example Fn + Eject, to preserve the functionality of the Magic SysRq key in linux on a Mactel. I believe this is a bug and not a feature request because the current implementation assumes that all keyboards have a SysRq key which is an incorrect assumption and therefore a mistake, or bug. Workaround: https://askubuntu.com/a/896806/21005 To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/262408/+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 1458204] Re: removing kernels should not require a restart afterward
Verified unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
I can verify the update-notifier 3.168.10 Did not test unattended-upgrades Did not change the tag since it is the same for unattended-upgrades unfortunately. -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
In which versions of the packages the fix is released? Which release of Ubuntu? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Fix Released Status in broadcom-sta package in Ubuntu: Fix Released Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+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
** Description changed: - We should switch the default kernle install to the signed kernel. This + 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. -- 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 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 1753050] Re: Does not recognize external monitor
I used "dkms status" to get the required information about the module name (nvidia-340) and version (340.104) After rebuilding and rebooting at least HDMI works with 4.4.0-116-generic -- 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/1753050 Title: Does not recognize external monitor Status in linux package in Ubuntu: Confirmed Bug description: Neither HDMI (digital) nor VGA (analog) output work with the kernel. With 4.4.0-112-generic they work fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1778 F pulseaudio CurrentDesktop: XFCE Date: Sat Mar 3 09:35:16 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e InstallationDate: Installed on 2015-11-21 (832 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753050/+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 1753050] Re: Does not recognize external monitor
$ dkms list outputs nothing -- 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/1753050 Title: Does not recognize external monitor Status in linux package in Ubuntu: Confirmed Bug description: Neither HDMI (digital) nor VGA (analog) output work with the kernel. With 4.4.0-112-generic they work fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1778 F pulseaudio CurrentDesktop: XFCE Date: Sat Mar 3 09:35:16 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e InstallationDate: Installed on 2015-11-21 (832 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753050/+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 1753050] Re: Does not recognize external monitor
As told in the description, with kernel 4.4.0-112-generic the outputs are recognized and work fine. The next kernel I installed was 4.4.0-116-generic with which the bug appears. The bug is not fixed in v4.16-rc4. ** Tags added: kernel-bug-exists-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/1753050 Title: Does not recognize external monitor Status in linux package in Ubuntu: Confirmed Bug description: Neither HDMI (digital) nor VGA (analog) output work with the kernel. With 4.4.0-112-generic they work fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1778 F pulseaudio CurrentDesktop: XFCE Date: Sat Mar 3 09:35:16 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e InstallationDate: Installed on 2015-11-21 (832 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753050/+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 1753050] [NEW] Does not recognize external monitor
Public bug reported: Neither HDMI (digital) nor VGA (analog) output work with the kernel. With 4.4.0-112-generic they work fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1778 F pulseaudio CurrentDesktop: XFCE Date: Sat Mar 3 09:35:16 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e InstallationDate: Installed on 2015-11-21 (832 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1753050 Title: Does not recognize external monitor Status in linux package in Ubuntu: New Bug description: Neither HDMI (digital) nor VGA (analog) output work with the kernel. With 4.4.0-112-generic they work fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1778 F pulseaudio CurrentDesktop: XFCE Date: Sat Mar 3 09:35:16 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e InstallationDate: Installed on 2015-11-21 (832 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753050/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Cool, I was not aware of those variables. -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Brian, Where you have uploaded the code? The code at https://code.launchpad.net/ubuntu/+source/dkms is old. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: In Progress Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Fix Committed Status in initramfs-tools source package in Xenial: New Status in dkms source package in Zesty: Fix Committed Status in initramfs-tools source package in Zesty: New Status in dkms package in Debian: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. [Test Case] On a system with two old kernels and one new kernel available in -updates: 1) install r8168-dkms 2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic' 3) upgrade your kernel e.g. "sudo apt install linux-image-generic' 4) sudo apt autoremove 5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic" With the version of dkms in -proposed, the .old-dkms file will be removed when the kernel is auto removed. [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: BugDistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: allSourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Note that the patch in #15 removes the leftovers related to the kernel version being removed currently. Removing leftovers related to already purged kernels still have to be done manually, for example by linux- purge https://www.bountysource.com/issues/38300038-feature-request-the- command-should-work-like-this together with other extra kernel related stuff. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
According to commant #8 patch against current https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/update-initramfs Removes all leftover initramfs files, even after dkms is uninstalled. ** Attachment added: "patch against update-imitramfs" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+attachment/4926764/+files/2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Oh, I seem to have forgotten to get the possible configurable path to dpkg in the version 2 of the code. That can be added to it, though I don't know how much that is required in Ubuntu. -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1458204] Re: removing kernels should not require a restart afterward
Because the code can be applied in many kernel post-installation scripts, I have attached it in Bug #1501884 and further updates go there. -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
This is another version for the code. It does not use awk. ** Attachment added: "code to add in probably all post-installation scripts except initramfs-tools and dkms to exit them before their job in case removing linux-image-extra (ver. 2)" https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501884/+attachment/4884920/+files/exitifextra -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Still, it might make more sense to run the scripts in /etc/kernel/postrm.d and program the exceptions for linux-image-extra there. For example, check in /etc/kernel/postrm.d/zz-update-grub if we are removing a linux-image-extra package, and only update grub, if not, right? And in /etc/kernel/postrm.d/initramfs-tools create initrd.img instead of removing it, if removing a linux-image-extra package. -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
I think the problems can be worked around by the attached code by adding it to post-installation scripts such as apt-auto-removal, unattended- upgrades, update-notifier, zz-update-grub, but not in initramfs-tools or dkms. ** Attachment added: "code to add in probably all post-installation scripts except initramfs-tools and dkms to exit them before their job in case removing linux-image-extra" https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501884/+attachment/4883533/+files/addition2 -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1458204] Re: removing kernels should not require a restart afterward
** Attachment added: "code to add in probably all post-installation scripts except initramfs-tools and dkms to exit them before their job in case removing linux-image-extra" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4883521/+files/addition2 ** Patch removed: "code to add before touching /var/run/reboot-required in post-installation scripts ; ver. 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4882547/+files/addition -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
** Patch removed: "code to add before touching /var/run/reboot-required in post-installation scripts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4881881/+files/addition -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
The code could be added to /etc/kernel/postinst.d/zz-update-grub, too, to avoid unnecessarily updating grub. -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
An exception for linux-image-extra packages can be added in /etc/kernel/postinst.d/update-notifier and in /etc/kernel/postinst.d /unattended-upgrades Also escape '+' characters, as package name may contain those: https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source ** Attachment added: "code to add before touching /var/run/reboot-required in post-installation scripts ; ver. 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4882547/+files/addition -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
An exception for linux-image-extra packages can be added in /etc/kernel/postinst.d/update-notifier and in /etc/kernel/postinst.d /unattended-upgrades ** Attachment added: "code to add before touching /var/run/reboot-required in post-installation scripts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4881881/+files/addition -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
@Andy, can you give more information about the trigger implementation you referred to? -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
@Andy reboot request notification is triggered by some kernels post- installation scripts only, so it is related. And as for the second issue, I have presented different strategy or two in the description of that bug report. -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Andy, in comment #10 I have mentioned a couple of other side effects of running post-installation scripts when removing a linux-image-extra package. -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
linux-image--generic is present when removing linux-image- extra--generic. initramfs-tools needs to re-create initrd.img, at least if linux-image--generic will not be removed. If that is the only reason, I think it would be better to do the re-creation in a postrm script than run all postinst scripts. /etc/kernel/postrm.d /initramfs-tools could detect it is removing a linux-image-extra package and then do the right thing. -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
As for the apt-auto-removal problem, it is fixed, right? Bug #1440608 Yet to be fixed at least: Bug #1458204 Bug #1678187 -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1458204] Re: removing kernels should not require a restart afterward
Steve Langasek, such a bug has been reported (Bug #1501884) -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
Yes, it is odd. I think the post-installation scripts will be run because the depending linux-image- package might not get removed (and is present at the time anyway), thus initramfs-tools is used to create /boot/initrd.img- without the extra kernel modules provided by linux-image-extra-. I guess that exception could be handled in /etc/kernel/postrm.d/initramfs-tools alternatively. Nowadays also /etc/kernel/postinst.d/unattended-upgrades touches /var/run/reboot-required so, that should be modified, as well (if post- installation script will be run). BTW running the post-installation scripts then may cause other problem, too: Bug #1678187 ** Also affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Also affects: unattended-upgrades 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
When removing a linux-image-extra package, kernel post-installation scripts including /etc/kernel/postinst.d/update-notifier will be run. That is a symbolic link to /usr/share/update-notifier/notify-reboot- required, which can be modified to fix this bug. -- 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/1458204 Title: removing kernels should not require a restart afterward Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/update-notifier/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
** Also affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Also affects: update-notifier 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/1458204 Title: removing kernels should not require a restart afterward Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/update-notifier/+bug/1458204/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Why not adding removing to both? That way update-initramfs would remove the extra ones even if dkms was uninstalled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Or update-initramfs could do more comprehensive deletion in its delete function: rm -f "${initramfs}" "${initramfs}".* instead of rm -f "${initramfs}" "${initramfs}.bak" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Here is the code as a file to retain text formatting. ** Attachment added: "Shell code for removing the backup initrd file for given kernel" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1515513/+attachment/4852757/+files/remove_initrd_backup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
The Bourne shell script code to remove the backups could be added in kernel_prerm.d_dkms (or currently non-existing kernel_postrm.d_dkms) in dkms package source, but if the package was removed, there would be no code to remove the backups in conjunction with kernel removing. Thus, the code could be added to kernel/postrm.d/initramfs-tools (or currently non-existing kernel/prerm.d/initramfs-tools) in initramfs-tools package source, too: # This is applied from make_initrd function in dkms command, which # creates the possible initrd backup file. remove_initrd_backup() { for initrd in "initrd-$1.img" "initramfs-$1.img" "initrd.img-$1" "initrd-$1"; do rm -fv /boot/"${initrd}".old-dkms \ /boot/efi/efi/redhat/"${initrd}".old-dkms done } remove_initrd_backup "$1" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1659750] Re: Wifi does not work
By 4.10-rc6 Network Manager tells "Wi-Fi is disabled" even if I check "Enable Wi-Fi". ** Tags added: bug-exists-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/1659750 Title: Wifi does not work Status in linux package in Ubuntu: Confirmed Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+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 1659750] Re: Wifi does not work
By 4.4.0-22 network manager tells "Wi-Fi is disabled" whereas in 4.4.0-51 and later it tells "device not ready". I do not remember, if this happened after update, but Wi-Fi used to work by the previous kernels before. -- 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/1659750 Title: Wifi does not work Status in linux package in Ubuntu: Incomplete Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+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 1608236] Re: Regression: S-video output does not work
S-video works by 4.8 based Yakkety kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1659750] Re: Wifi does not work
I also tried to boot from live USB, both 14.04.1 and 16.04.1 and same thing. I could not switch wireless on by "Fn + F5" in Linux https://support.lenovo.com/fi/en/documents/migr-63140 -- 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/1659750 Title: Wifi does not work Status in linux package in Ubuntu: Confirmed Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+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 1659750] [NEW] Wifi does not work
Public bug reported: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wifi 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/1659750 Title: Wifi does not work Status in linux package in Ubuntu: New Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+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 1608236] Re: Regression: S-video output does not work
Why incomplete? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1608236] Re: Regression: S-video output does not work
It works. But colors are gone. Also with 4.4.0-22-generic. Maybe my hardware is breaking. I also tried to install linux-generic- hwe-16.04-edge to get newer kernel, but apt failed to fetch the .debs. -- 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1608236] Re: Regression: S-video output does not work
The kernel does not resolve the bug. -- 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1608236] Re: Regression: S-video output does not work
I get the same kernel (4.4.0.51.54) via , xenial-updates, xenial- security and xenial-proposed now. The bug is not fixed. -- 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1620648] Re: [Regression] Pairing bluetooth 0a12:0001 with Bose SoundLink around-ear II headphones fails
As for #11, it is due to Bug #1274613 -- 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/1620648 Title: [Regression] Pairing bluetooth 0a12:0001 with Bose SoundLink around- ear II headphones fails Status in blueman package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I see the device in blueman-manager, but pairing fails. I could pair the dongle with another device. And I could pair the Bose device with another bluetooth device in Xubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jarnos 3069 F...m pulseaudio /dev/snd/pcmC0D0p: jarnos 3069 F...m pulseaudio /dev/snd/controlC0: jarnos 3069 F pulseaudio CurrentDesktop: XFCE Date: Tue Sep 6 17:01:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (131 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1620648/+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 1608236] Re: Regression: S-video output does not work
Yes, it has landed there. Will it land to Xenial soon? -- 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1620648] Re: [Regression] Pairing bluetooth 0a12:0001 with Bose SoundLink around-ear II headphones fails
I finally was able to make sound work in Xenial. I did pactl unload-module module-bluetooth-discover and pactl load-module module-bluetooth-discover on terminal. Removed and re-added the BOSE device in bluetooth manager. I also had to tweak bluetooth settings in pavucontrol. -- 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/1620648 Title: [Regression] Pairing bluetooth 0a12:0001 with Bose SoundLink around- ear II headphones fails Status in blueman package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I see the device in blueman-manager, but pairing fails. I could pair the dongle with another device. And I could pair the Bose device with another bluetooth device in Xubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jarnos 3069 F...m pulseaudio /dev/snd/pcmC0D0p: jarnos 3069 F...m pulseaudio /dev/snd/controlC0: jarnos 3069 F pulseaudio CurrentDesktop: XFCE Date: Tue Sep 6 17:01:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (131 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1620648/+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 1608236] Re: Regression: S-video output does not work
I am looking forward to seeing the bug fixed in kernel updates for 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1620648] Re: [Regression] Pairing bluetooth 0a12:0001 with Bose SoundLink around-ear II headphones fails
In the Trusty machine it helped that I ran pactl load-module module-bluetooth-discover -- 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/1620648 Title: [Regression] Pairing bluetooth 0a12:0001 with Bose SoundLink around- ear II headphones fails Status in blueman package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I see the device in blueman-manager, but pairing fails. I could pair the dongle with another device. And I could pair the Bose device with another bluetooth device in Xubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jarnos 3069 F...m pulseaudio /dev/snd/pcmC0D0p: jarnos 3069 F...m pulseaudio /dev/snd/controlC0: jarnos 3069 F pulseaudio CurrentDesktop: XFCE Date: Tue Sep 6 17:01:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (131 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1620648/+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 1608236] Re: Regression: S-video output does not work
4.9-rc2 does not have the bug. -- 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: Confirmed Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1608236] Re: Regression: S-video output does not work
It does not have the bug. -- 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: Confirmed Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1608236] Re: Regression: S-video output does not work
That has the bug. -- 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: Confirmed Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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