Re: [Bug 1944121] Re: removing packages in installer crashed

removing packages in installer crashed > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944121/+subscriptions > > -- Mvh. -fredrik-normann- Sent from my Gmail Account -- You received this bug notification because you are a memb

[Bug 1944121] [NEW] removing packages in installer crashed

Public bug reported: Installer crashed. Was sent here to report bug. It happend in the final stage of removing packages not needed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux

[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"

@zeorin Thanks for that info. I had to do the following extra. Since I use LUKS encrypted disk and uefi. 1) Open the encrypted disk in File explorer 2) Mount the lvm partition on /mnt mount /dev/ubuntu-vg/root /mnt Mount boot mount /dev/nvme0n1p2 /mnt/boot Mount efi mount /dev/nvme0n1p1

Re: [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"

nchpad.net/bugs/1853369 > > Title: > [19.10] Boot hangs at "loading initial ramdisk" > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions > -- Mvh -fredrik-normann- Sent f

[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"

I encountered this bug when doing a do-release-upgrade. Unable to boot. If I update now, will kernel 5.3.0-24-generic be used? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10]

[Bug 1853369] [NEW] [19.10] Boot hangs at "loading initial ramdisk"

Public bug reported: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to

[Bug 1597466] Re: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file

Saw this today: sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: base-files libmozjs-52-0 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

[27656.334177] usb 1-7: USB disconnect, device number 5 [27712.841243] usb 1-7: new full-speed USB device number 11 using xhci_hcd [27712.990551] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b [27712.990556] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0

[Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

I think this is related to suspend. If I reboot my computer, and pair my headset, I get sound. when I suspend my computer and try to turn on the bluetooth connection I get the error message dmesg. Ubuntu 17.04 did not have this problem, but 17.10 and 18.04 has. -- You received this bug

[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000

17.10 and this shows up in syslog: Oct 23 10:32:43 normann kernel: [16449.935879] ieee80211 phy0: Hardware restart was requested Oct 23 10:33:04 normann kernel: [16470.892551] iwlwifi :03:00.0: regular scan timed out Oct 23 10:33:04 normann kernel: [16470.893902] iwlwifi :03:00.0: