[Kernel-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
how does this get assigned to someone so it might get 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/1652101
Title:
Can't create nested AppArmor namespaces
Status in AppArmor:
Confirmed
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
policy namespace and load a profile belonging to that AppArmor
namespace. Once that's done, the user can confine a process with that
namespaced AppArmor profile and enter into a user namespace. That
process can then load additional AppArmor profiles inside of the
AppArmor and user namespace. Here's an example:
We need to set up the namespace, n1, and load the profile, p1.
$ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root,
capability,"
$ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
$ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1
Now we enter into confinement using the AppArmor namespace and profile and
then enter into an unprivileged user namespace
$ aa-exec -n n1 -p p1 -- unshare -Ur
We can now load profiles as the privileged user inside of the unprivileged
user namespace
# echo "profile test {}" | apparmor_parser -qr
The reason for this bug report is that we cannot create a nested
AppArmor policy namespace inside of the unprivileged user namespace
# mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
mkdir: cannot create directory
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission
denied
If that worked, we could adjust LXD to read
/sys/kernel/security/apparmor/.ns_name to get the current AppArmor
namespace, then create a new namespace under the current namespace,
and leverage the nested namespace for its nested containers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1652101/+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 1652101] Re: Can't create nested AppArmor namespaces
>From what I understand, LXD is moving toward SNAP LXD as a default, so
not being able to run SNAP in an LXD container configured for "nesting":
re -
lxc config set security.nesting true
Is basically going to prevent LXD from being used for Nested Containers.
--
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/1652101
Title:
Can't create nested AppArmor namespaces
Status in AppArmor:
Confirmed
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
policy namespace and load a profile belonging to that AppArmor
namespace. Once that's done, the user can confine a process with that
namespaced AppArmor profile and enter into a user namespace. That
process can then load additional AppArmor profiles inside of the
AppArmor and user namespace. Here's an example:
We need to set up the namespace, n1, and load the profile, p1.
$ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root,
capability,"
$ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
$ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1
Now we enter into confinement using the AppArmor namespace and profile and
then enter into an unprivileged user namespace
$ aa-exec -n n1 -p p1 -- unshare -Ur
We can now load profiles as the privileged user inside of the unprivileged
user namespace
# echo "profile test {}" | apparmor_parser -qr
The reason for this bug report is that we cannot create a nested
AppArmor policy namespace inside of the unprivileged user namespace
# mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
mkdir: cannot create directory
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission
denied
If that worked, we could adjust LXD to read
/sys/kernel/security/apparmor/.ns_name to get the current AppArmor
namespace, then create a new namespace under the current namespace,
and leverage the nested namespace for its nested containers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1652101/+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 1745758] [NEW] package linux-headers-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: I just did: sudo apt update sudo apt upgrade -y sudo apt dist-upgrade -y and this bug/error popped up. Note: I have had this happen on a 2nd Ubuntu 17.10 system as well. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: audio-recorder:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1380 F pulseaudio bmullan2305 F pulseaudio /dev/snd/controlC0: gdm1380 F pulseaudio bmullan2305 F pulseaudio Date: Sat Jan 27 11:49:20 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=e9819db4-72fd-4104-8562-e853ec676f78 InstallationDate: Installed on 2017-12-28 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=UUID=9f7b0e7e-c876-4dff-8f51-dbfe92641817 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package artful -- 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/1745758 Title: package linux-headers-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: I just did: sudo apt update sudo apt upgrade -y sudo apt dist-upgrade -y and this bug/error popped up. Note: I have had this happen on a 2nd Ubuntu 17.10 system as well. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: audio-recorder:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1380 F pulseaudio bmullan2305 F pulseaudio /dev/snd/controlC0: gdm1380 F pulseaudio bmullan2305 F pulseaudio Date: Sat Jan 27 11:49:20 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=e9819db4-72fd-4104-8562-e853ec676f78 InstallationDate: Installed on 2017-12-28 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=UUID=9f7b0e7e-c876-4dff-8f51-dbfe92641817 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, pytho
[Kernel-packages] [Bug 1745758] Re: package linux-headers-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Ok I opened a terminal and sudo apt-get install -f and got... $ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 6 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up linux-headers-4.13.0-32-generic (4.13.0-32.35) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.13.0-32-generic /boot/vmlinuz-4.13.0-32-generic Error! Could not locate dkms.conf file. File: does not exist. run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-4.13.0-32-generic.postinst line 110. dpkg: error processing package linux-headers-4.13.0-32-generic (--configure): subprocess installed post-installation script returned error exit status 2 Setting up linux-image-4.13.0-32-generic (4.13.0-32.35) ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-4.13.0-32-generic vmlinuz(/boot/vmlinuz-4.13.0-32-generic ) points to /boot/vmlinuz-4.13.0-32-generic (/boot/vmlinuz-4.13.0-32-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-32-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-32-generic /boot/vmlinuz-4.13.0-32-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-32-generic /boot/vmlinuz-4.13.0-32-generic Error! Could not locate dkms.conf file. File: does not exist. run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.13.0-32-generic.postinst line 1052. dpkg: error processing package linux-image-4.13.0-32-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-extra-4.13.0-32-generic: linux-image-extra-4.13.0-32-generic depends on linux-image-4.13.0-32-generic; however: Package linux-image-4.13.0-32-generic is not configured yet. dpkg: error processing package linux-image-extra-4.13.0-32-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.13.0-32-generic; however: Package linux-image-4.13.0-32-generic is not configured yet. linux-image-generic depends on linux-image-extra-4.13.0-32-generic; however: Package linux-image-extra-4.13.0-32-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-4.13.0-32-generic; however: Package linux-headers-4.13.0-32-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 4.13.0.32.34); however: Package linux-image-generic is not configured yet. linux-generic depends on linux-headers-generic (= 4.13.0.32.34); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-4.13.0-32-generic linux-image-4.13.0-32-generic linux-image-extra-4.13.0-32-generic linux-image-generic linux-headers-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) bmullan@pc:~$ continuing with the rest of the suggested commands: sudo apt-get clean sudo apt-get update and both of those have normal output. However, trying to install any app after those (such as vlc) I get the same errors: $ sudo apt-get install vlc Reading package lists... Done Building dependency tree Reading state information... Done vlc is already the newest version (2.2.6-6). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 6 not fully installed or removed. After th
[Kernel-packages] [Bug 1745758] Re: package linux-headers-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
NOTE: just fyi but a google search earlier before I filed the bug showed others getting this also -- 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/1745758 Title: package linux-headers-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: I just did: sudo apt update sudo apt upgrade -y sudo apt dist-upgrade -y and this bug/error popped up. Note: I have had this happen on a 2nd Ubuntu 17.10 system as well. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: audio-recorder:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1380 F pulseaudio bmullan2305 F pulseaudio /dev/snd/controlC0: gdm1380 F pulseaudio bmullan2305 F pulseaudio Date: Sat Jan 27 11:49:20 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=e9819db4-72fd-4104-8562-e853ec676f78 InstallationDate: Installed on 2017-12-28 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=UUID=9f7b0e7e-c876-4dff-8f51-dbfe92641817 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745758/+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 1736827] Re: Toshiba BIOS wrecked
*** This bug is a duplicate of bug 1734147 *** https://bugs.launchpad.net/bugs/1734147 Appears this lenovo bios problem affects more than just ubuntu... https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 -- 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/1736827 Title: Toshiba BIOS wrecked Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: I installed UBUNTU 17.10 - Dual Boot Windows 10, with GRUB2 as Bootloader on my expensive Toshiba Laptop - s50t-b (model #). Now Bios is basically useless, no change boot order, no load defaults, no system clock. what do I do? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736827/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Appears that this lenovo bios problem affects more than just Ubuntu... https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (20/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+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 1971573] Re: After upgrade from 20.04 to 22.04 & reboor hangs
I wish I had the log files etc but I was trying to get my system back up. The explanation I gave is pretty clear the top 2 entries in the grub boot menu had an odd name including "kvm" in it. Since those 2 weren't there before I have to assume the Ubuntu "upgrade" process > do-release-upgrade -d I deleted those from /boot updated grub rebooted System booted up normally. This "was" a 20.04 upgraded by > do-release-upgrade -d Upgrade succeeded and told me to reboot. After POST system just hung on "something" Which led to the previous info I had done a search and found others asking about the same 22.04 "upgrade" "hang" on askubuntu etc. Brian -- 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/1971573 Title: After upgrade from 20.04 to 22.04 & reboor hangs Status in linux package in Ubuntu: Incomplete Bug description: I had a 20.04 system I "upgraded" to 22.04. > do-release-upgrade -d The upgrade went well except after reboot the system never came back up. Searching the web I found quite a few others having the same/similar problem. Troubleshooting I booted a LiveCD Ubuntu 22.04 and looked at /boot on the just upgraded system and found something really strange! There were the expected vmlinuz and initrd files but there were also 2 entries for some kind of KVM entries ?? Removing the KVM entries and rebooting the system it rebooted successfully into 22.04. I'd never seen "KVM anything" in grub boot menu before so thought I'd report it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971573/+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
